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

Review completed delegated issues from mobile Filed #878

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

Problem

Delegated issues disappear from the mobile Filed queue as soon as they close, precisely when the filer needs to review the result. The work search currently hard-codes state=open, while the recently shipped Filed detail/reply flow only handles open authored issues.

Vertical slice

  • Include a bounded newest-first set of closed issues authored by the signed-in operator in Filed.
  • Mark completed outcomes distinctly and prioritize them for review.
  • Let the filer acknowledge a completed outcome locally and advance to the next Filed item; acknowledgement survives refresh and a later upstream update makes the outcome visible again.
  • Preserve the existing read-only Filed detail and follow-up reply flow.
  • Keep the mobile decision surface safe-area aware and accessible at 320px/390px.

Acceptance

  • A newly closed delegated issue remains visible as Completed · review outcome in Filed and contributes to its count.
  • Open Filed behavior is unchanged.
  • Acknowledging removes only that outcome, persists across refresh, is idempotent, and opens the next Filed item when present.
  • A closed issue updated after acknowledgement becomes reviewable again.
  • Completed Filed detail remains read-only except conversation/reply and acknowledgement.
  • Focus/status behavior and narrow mobile layout are covered by behavioral tests.

Evidence / non-duplication

Current main ends with #866/#868/#870/#872/#874/#876, which build filing receipt, Filed discovery/detail/launch/replies but never retain closed outcomes. Generic Search reopen (#547) does not provide a delegated-outcome review queue. All 442 historical issue titles and recent commits were checked; no issue covers completed Filed outcome review.

## Problem Delegated issues disappear from the mobile Filed queue as soon as they close, precisely when the filer needs to review the result. The work search currently hard-codes `state=open`, while the recently shipped Filed detail/reply flow only handles open authored issues. ## Vertical slice - Include a bounded newest-first set of closed issues authored by the signed-in operator in Filed. - Mark completed outcomes distinctly and prioritize them for review. - Let the filer acknowledge a completed outcome locally and advance to the next Filed item; acknowledgement survives refresh and a later upstream update makes the outcome visible again. - Preserve the existing read-only Filed detail and follow-up reply flow. - Keep the mobile decision surface safe-area aware and accessible at 320px/390px. ## Acceptance - A newly closed delegated issue remains visible as `Completed · review outcome` in Filed and contributes to its count. - Open Filed behavior is unchanged. - Acknowledging removes only that outcome, persists across refresh, is idempotent, and opens the next Filed item when present. - A closed issue updated after acknowledgement becomes reviewable again. - Completed Filed detail remains read-only except conversation/reply and acknowledgement. - Focus/status behavior and narrow mobile layout are covered by behavioral tests. ## Evidence / non-duplication Current main ends with #866/#868/#870/#872/#874/#876, which build filing receipt, Filed discovery/detail/launch/replies but never retain closed outcomes. Generic Search reopen (#547) does not provide a delegated-outcome review queue. All 442 historical issue titles and recent commits were checked; no issue covers completed Filed outcome review.
timmy self-assigned this 2026-08-15 07:20:12 +00:00
timmy closed this issue 2026-08-15 07:44:22 +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#878
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?