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

Complete assigned issues from mobile My Work #157

New Issue
Closed
opened 2026-08-07 02:26:23 +00:00 by timmy · 0 comments
timmy commented 2026-08-07 02:26:23 +00:00
Owner
Copy Link

User problem

Assigned issues in mobile My Work are external links, while reviews and unread updates can be completed in-dashboard. Phone users must context-switch to Gitea just to read context, comment, or close ordinary assigned work.

Vertical slice

Add an accessible issue action sheet for assigned issues with normalized detail/recent discussion, draft-safe single-flight comments, confirmed closure, and a permanent Open in Gitea fallback. Remove an issue from My Work only after Gitea confirms closure.

Acceptance tests

  • Tapping an issue card opens a full-width safe-area-aware sheet with title, body, labels, assignees, recent comments, retry, and Open in Gitea.
  • Failed detail loads remain retryable without leaking upstream errors.
  • Comment drafts survive close/reopen and failed submission; duplicate taps cause one POST; success clears the draft.
  • Close requires confirmation, is single-flight, removes the card/count only after success, and keeps it on failure.
  • API routes validate input, use no-store, enforce bounded deadlines, and sanitize failures.
  • Mobile controls are at least 44px and focus returns to the originating card.

Non-duplication evidence

No open issue or PR covers issue action sheets. Historical issues #115-#155 cover My Work, review flows, and notification flows, but none implements general assigned-issue detail/comment/close. Current main renders ordinary issue cards as external links.

## User problem Assigned issues in mobile My Work are external links, while reviews and unread updates can be completed in-dashboard. Phone users must context-switch to Gitea just to read context, comment, or close ordinary assigned work. ## Vertical slice Add an accessible issue action sheet for assigned issues with normalized detail/recent discussion, draft-safe single-flight comments, confirmed closure, and a permanent Open in Gitea fallback. Remove an issue from My Work only after Gitea confirms closure. ## Acceptance tests - Tapping an issue card opens a full-width safe-area-aware sheet with title, body, labels, assignees, recent comments, retry, and Open in Gitea. - Failed detail loads remain retryable without leaking upstream errors. - Comment drafts survive close/reopen and failed submission; duplicate taps cause one POST; success clears the draft. - Close requires confirmation, is single-flight, removes the card/count only after success, and keeps it on failure. - API routes validate input, use no-store, enforce bounded deadlines, and sanitize failures. - Mobile controls are at least 44px and focus returns to the originating card. ## Non-duplication evidence No open issue or PR covers issue action sheets. Historical issues #115-#155 cover My Work, review flows, and notification flows, but none implements general assigned-issue detail/comment/close. Current main renders ordinary issue cards as external links.
timmy self-assigned this 2026-08-07 02:26:23 +00:00
timmy closed this issue 2026-08-07 02:41:58 +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#157
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?