DB query tables omit per-task and aggregate tracked time

Aperta
  • Qualcosa non va?
#1,470 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Nessun dato sulla lingua
Stelle
29
Fork
2
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di logseq/db-test

Tutte le issue di logseq/db-test

Issue simili

Altre issue su Web Dev

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.