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

Reply to unread updates from mobile My Work #153

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

User problem

Mobile My Work can read and acknowledge an unread issue or pull-request update, but replying still requires leaving the dashboard and rebuilding context in Gitea.

Vertical slice

Add a reply composer to the existing unread-update sheet. Resolve the notification subject server-side, post the reply to the matching Gitea issue/PR conversation, preserve drafts across close/reload and failures, and retain Mark read & next as an explicit separate action.

Acceptance criteria

  • Only issue/pull notification subjects on the configured Gitea origin can receive replies.
  • Empty/oversized replies are rejected before upstream I/O; upstream errors are sanitized and retryable.
  • A failed reply never marks the notification read and preserves the draft.
  • A successful reply clears only that thread draft and confirms success.
  • Double submit is single-flight; responses are no-store.
  • Existing notification triage continues to pass.
  • Mobile composer/actions remain usable at 320x568 and 390x844 with 44px targets and safe-area spacing.

Non-duplication evidence

Issues #133, #135, #141, #147, and #151 cover discovery, acknowledgement, bulk triage, pagination, and reading updates. No historical issue, PR, recent commit, source route, or open ticket implements posting a reply from the update sheet.

## User problem Mobile My Work can read and acknowledge an unread issue or pull-request update, but replying still requires leaving the dashboard and rebuilding context in Gitea. ## Vertical slice Add a reply composer to the existing unread-update sheet. Resolve the notification subject server-side, post the reply to the matching Gitea issue/PR conversation, preserve drafts across close/reload and failures, and retain Mark read & next as an explicit separate action. ## Acceptance criteria - Only issue/pull notification subjects on the configured Gitea origin can receive replies. - Empty/oversized replies are rejected before upstream I/O; upstream errors are sanitized and retryable. - A failed reply never marks the notification read and preserves the draft. - A successful reply clears only that thread draft and confirms success. - Double submit is single-flight; responses are no-store. - Existing notification triage continues to pass. - Mobile composer/actions remain usable at 320x568 and 390x844 with 44px targets and safe-area spacing. ## Non-duplication evidence Issues #133, #135, #141, #147, and #151 cover discovery, acknowledgement, bulk triage, pagination, and reading updates. No historical issue, PR, recent commit, source route, or open ticket implements posting a reply from the update sheet.
timmy self-assigned this 2026-08-07 00:52:54 +00:00
timmy closed this issue 2026-08-07 01:02:57 +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#153
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?