{{ message }}
feat(ui): show metadata for recently viewed tasks and task groups#8755
Open
nitishagar wants to merge 2 commits into
Open
feat(ui): show metadata for recently viewed tasks and task groups#8755nitishagar wants to merge 2 commits into
nitishagar wants to merge 2 commits into
Conversation
…s/groups - renderSecondary returns null (not the ID) when no metadata is stored, avoiding duplicate ID display for legacy records - renderStatusSummary labels a resolved group FAILED when failures exist, rather than always using COMPLETED
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
The
/tasksand/tasks/groupspages previously listed the last 5 recently-viewed items as bare IDs with no context. This PR stores richer metadata at view time and displays up to 20 entries ordered by recency.Before
After
Design decisions
viewedAtsecondary index on both Dexie tables makesorderBy('viewedAt').reverse().limit(20)efficient.viewedAtand are excluded by the index query — they age out naturally as the user browses and new rich records fill in. Mentioned in tests.Possible follow-up (out of scope)
A comment on the issue suggested a "my recent tasks" filtered by owner. That would require storing
task.metadata.ownerand filtering; noted here for future work.Changes
ui/src/utils/db.js:db.version(2)addsviewedAtsecondary indexui/src/views/Tasks/ViewTask/index.jsx:updateTaskIdHistorystores name, source, taskQueueId, created, deadline, state, viewedAtui/src/views/Tasks/TaskGroup/index.jsx:updateTaskGroupIdHistorystores decision-task metadata + statusCount + viewedAtui/src/views/Tasks/NoTask/index.jsx: queries by viewedAt, renders rich listui/src/views/Tasks/NoTaskGroup/index.jsx: queries by viewedAt, renders rich list with status countsFixes #8711