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

Create follow-up work from an unread update #663

New Issue
Closed
opened 2026-08-12 16:23:38 +00:00 by timmy · 0 comments
timmy commented 2026-08-12 16:23:38 +00:00
Owner
Copy Link

Problem

Mobile unread updates provide reply, ownership, acknowledgement, defer, and mark-read actions, but cannot turn discussion context into a new trackable issue. Updates on pull requests, assigned issues, and closed threads therefore require a lossy manual copy/paste flow.

Slice

Add a phone-safe Create follow-up action to update detail. It opens existing issue capture with the source repository, a derived editable title, and canonical source/context in the body. Preserve any existing capture draft behind an explicit resume/use conflict, keep the source update unread, and return to the same update on cancel. Reuse existing Drafts, duplicate detection, create, and create-and-start paths.

Acceptance

  • Supported issue/PR updates expose a 44px-minimum Create follow-up action.
  • Follow-up capture derives safe repository/title/body fields with canonical source URL and latest context.
  • Existing capture drafts are never silently overwritten.
  • Cancelling returns to the source update, which remains unread.
  • Existing save-to-Drafts, create, create-and-start, duplicate, and capacity behavior remains intact.
  • Behavioral tests cover normalization, conflict/acceptance, and dashboard wiring.

Evidence / non-duplication

Audited origin/main 97eb928, all 334 issue titles, 325 PRs, 666 commits, and six open issues. No issue, PR, or commit implements update-to-follow-up capture; nearby work covers update replies/ownership and share capture only.

## Problem Mobile unread updates provide reply, ownership, acknowledgement, defer, and mark-read actions, but cannot turn discussion context into a new trackable issue. Updates on pull requests, assigned issues, and closed threads therefore require a lossy manual copy/paste flow. ## Slice Add a phone-safe **Create follow-up** action to update detail. It opens existing issue capture with the source repository, a derived editable title, and canonical source/context in the body. Preserve any existing capture draft behind an explicit resume/use conflict, keep the source update unread, and return to the same update on cancel. Reuse existing Drafts, duplicate detection, create, and create-and-start paths. ## Acceptance - Supported issue/PR updates expose a 44px-minimum Create follow-up action. - Follow-up capture derives safe repository/title/body fields with canonical source URL and latest context. - Existing capture drafts are never silently overwritten. - Cancelling returns to the source update, which remains unread. - Existing save-to-Drafts, create, create-and-start, duplicate, and capacity behavior remains intact. - Behavioral tests cover normalization, conflict/acceptance, and dashboard wiring. ## Evidence / non-duplication Audited origin/main `97eb928`, all 334 issue titles, 325 PRs, 666 commits, and six open issues. No issue, PR, or commit implements update-to-follow-up capture; nearby work covers update replies/ownership and share capture only.
timmy self-assigned this 2026-08-12 16:23:38 +00:00
timmy closed this issue 2026-08-12 16:35:35 +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#663
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?