DB query tables omit per-task and aggregate tracked time

Abierto
  • ¿Algo no está bien?
#1,470 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Área
frontend

Línea de trabajo

The issue names no implementation files or tests; it identifies DB Query Table and List views, the query heading, and existing status-history duration calculation as starting points. Read the query display and aggregation implementation, then trace how task duration is calculated. Done means each result can show Time Spent, the heading totals the complete matching result set, and values update as described; focused worker and UI tests are expected.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Related issue

This follows up on #465, which reported that DB query results did not expose time-tracking data for individual task rows. That issue was closed as stale, but the limitation is still present in the current DB version.

What happened?

In a DB graph, a query that returns tasks with recorded time behaves differently depending on the selected view:

  • List View shows the tracked duration on each rendered task.
  • Table View has no Time Spent column and does not show the duration for individual task rows.
  • The Live Query (N) heading does not show the aggregate tracked time for the complete result set.

This is also a regression relative to Logseq OG/file graphs. OG query tables expose the aggregate tracked time, even though #465 documents that their individual rows do not expose each task's duration. The DB version currently provides neither value in Table View, so users lose the invoice total they could obtain in OG.

Here, "Table View" means the table view of a Query block inside a DB graph, not the global graph visualization.

OG Table (narrow and scrolled to the left to show upper left hand corner with aggregate)
Image
DB Table (no aggregate data shown)
Image
Reproduction
  1. In a DB graph, create several tasks under a shared tag or parent reference.
  2. Move each task through Doing long enough to record time, then complete the tasks.
  3. Create a query that returns those tasks.
  4. Switch the query to Table View.
  5. Open the column visibility menu and inspect the query heading.

Observed:

  • No per-row Time Spent column is available.
  • No aggregate duration is shown beside Live Query (N) or elsewhere in the query view.
  • Switching to List View shows the individual task duration, confirming that the underlying time data is available.
Expected behavior
  • Query Table View provides a Time Spent column for each task result.
  • The query heading shows the aggregate tracked time for all results represented by Live Query (N).
  • The aggregate uses the complete matching result set, not only the currently rendered/virtualized rows.
  • The aggregate remains available when switching between Table and List views.
  • Values refresh when query membership, view filters, or relevant task status history changes.

Sorting or filtering by the calculated duration is not required to address this issue.

Why this matters

A common workflow is to query completed tasks for an invoice period and use their aggregate tracked time to prepare an invoice. Without an aggregate, the DB version cannot replace the equivalent OG workflow. This is a migration blocker for users who rely on Logseq for task-based time tracking and invoicing.

Environment

Reproduced in the current local DB development build on macOS (Logseq Desktop 2.0.2).

PR willingness
  • I am willing to submit a focused PR adding the per-task query column and aggregate query time.

I have already investigated the current implementation and would keep the change scoped to query display/aggregation, reuse the existing status-history duration calculation, and include focused worker and UI tests.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
29
Forks
2
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de logseq/db-test

Todos los issues de logseq/db-test

Issues similares

Más issues de Web Dev

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.