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

Keep delegated filings visible in a mobile Filed queue #870

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

Problem

After a mobile operator files an issue for a teammate or leaves it unassigned, the issue disappears from My Work after the transient receipt. The authenticated Gitea created=true stream is not loaded, despite representing durable cross-device follow-up work.

Vertical slice

  • Load a bounded open authored-issue stream from Gitea with a distinct created_by_me reason.
  • Merge authored issues into My Work without duplicating self-assigned issues.
  • Add a Filed queue/count for durable delegated and unassigned follow-up.
  • Add a primary receipt action that opens the confirmed issue in Filed.
  • Preserve existing read-first issue detail behavior and paginated refresh semantics.

Acceptance

  • work_page("filed") requests state=open&created=true&type=issues with bounded pagination and upstream totals.
  • Authored issues are normalized with created_by_me; an authored issue also assigned to the operator appears once with both reasons.
  • Filed filtering/counts include authored issues and exclude unrelated work.
  • The receipt's View in Filed action closes the receipt and routes the exact repository/number into the in-app Filed queue.
  • Mobile actions remain at least 44px and the focused flow has no horizontal overflow.
  • Focused tests and full suite pass.

Evidence: current src/gitea_proxy.py only defines assigned issue/pull and review streams; current receipt only offers external open/share/related/another/done. All 438 historical issue titles and recent commits were checked; no prior Filed/authored follow-up queue exists.

## Problem After a mobile operator files an issue for a teammate or leaves it unassigned, the issue disappears from My Work after the transient receipt. The authenticated Gitea `created=true` stream is not loaded, despite representing durable cross-device follow-up work. ## Vertical slice - Load a bounded open authored-issue stream from Gitea with a distinct `created_by_me` reason. - Merge authored issues into My Work without duplicating self-assigned issues. - Add a Filed queue/count for durable delegated and unassigned follow-up. - Add a primary receipt action that opens the confirmed issue in Filed. - Preserve existing read-first issue detail behavior and paginated refresh semantics. ## Acceptance - `work_page("filed")` requests `state=open&created=true&type=issues` with bounded pagination and upstream totals. - Authored issues are normalized with `created_by_me`; an authored issue also assigned to the operator appears once with both reasons. - Filed filtering/counts include authored issues and exclude unrelated work. - The receipt's View in Filed action closes the receipt and routes the exact repository/number into the in-app Filed queue. - Mobile actions remain at least 44px and the focused flow has no horizontal overflow. - Focused tests and full suite pass. Evidence: current `src/gitea_proxy.py` only defines assigned issue/pull and review streams; current receipt only offers external open/share/related/another/done. All 438 historical issue titles and recent commits were checked; no prior Filed/authored follow-up queue exists.
timmy closed this issue 2026-08-15 05:05:11 +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
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#870
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?