stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Keep acknowledged outcomes in mobile Filed history #882

New Issue
Closed
opened 2026-08-15 08:51:08 +00:00 by timmy · 0 comments
timmy commented 2026-08-15 08:51:08 +00:00
Owner
Copy Link

User problem

Acknowledge & next currently removes a completed delegated filing from Filed entirely. Operators lose the natural record of work they initiated and must reconstruct it through global Search or Gitea, even though the synchronized acknowledgement receipt retains the issue identity and reviewed revision.

Scope

Add Needs review and Reviewed views to mobile Filed. Acknowledgement moves a completed outcome into Reviewed; reviewed cards reopen the existing read-only Filed detail and conversation. A newer upstream updated_at revision returns the outcome to Needs review. Keep the Filed badge actionable-only.

Acceptance criteria

  • At 320px and 390px widths, Filed exposes touch-sized Needs review and Reviewed controls without horizontal overflow.
  • Acknowledging a completed outcome moves it to Reviewed and advances to the next actionable item.
  • Reviewed cards reopen existing Filed detail; Back returns to Reviewed.
  • Same-revision refresh remains Reviewed; a newer revision returns to Needs review.
  • Reviewed has a truthful empty state and does not inflate the actionable Filed badge.
  • Behavioral tests cover partitioning, acknowledgement movement, revision reactivation, routing, and mobile markup.

Non-duplication evidence

All 444 historical issue titles/bodies and recent commits through 403190e were checked. #878 added completed-outcome review and intentionally suppresses acknowledged revisions; #880 synchronized those receipts. Neither provides browsable post-acknowledgement history. No historical issue matches “Filed history” or “Reviewed history”.

## User problem `Acknowledge & next` currently removes a completed delegated filing from Filed entirely. Operators lose the natural record of work they initiated and must reconstruct it through global Search or Gitea, even though the synchronized acknowledgement receipt retains the issue identity and reviewed revision. ## Scope Add **Needs review** and **Reviewed** views to mobile Filed. Acknowledgement moves a completed outcome into Reviewed; reviewed cards reopen the existing read-only Filed detail and conversation. A newer upstream `updated_at` revision returns the outcome to Needs review. Keep the Filed badge actionable-only. ## Acceptance criteria - At 320px and 390px widths, Filed exposes touch-sized Needs review and Reviewed controls without horizontal overflow. - Acknowledging a completed outcome moves it to Reviewed and advances to the next actionable item. - Reviewed cards reopen existing Filed detail; Back returns to Reviewed. - Same-revision refresh remains Reviewed; a newer revision returns to Needs review. - Reviewed has a truthful empty state and does not inflate the actionable Filed badge. - Behavioral tests cover partitioning, acknowledgement movement, revision reactivation, routing, and mobile markup. ## Non-duplication evidence All 444 historical issue titles/bodies and recent commits through `403190e` were checked. #878 added completed-outcome review and intentionally suppresses acknowledged revisions; #880 synchronized those receipts. Neither provides browsable post-acknowledgement history. No historical issue matches “Filed history” or “Reviewed history”.
timmy self-assigned this 2026-08-15 08:51:08 +00:00
timmy closed this issue 2026-08-15 09:13:44 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#882
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?