DB query tables omit per-task and aggregate tracked time

オープン
  • 何か問題がありますか？
#1,470 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
45/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
領域
frontend

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
言語のデータがありません
スター
29
フォーク
2
30日以内にマージされた PR はありません

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

logseq/db-test のほかの issue

logseq/db-test の issue をすべて見る

似ている issue

Web Dev の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。