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

Take ownership from an unread issue update #321

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

Problem

On mobile, an operator reading an actionable unread issue update must leave the conversation, find the issue again, claim it elsewhere, then return to plan it. This breaks notification triage and risks losing context.

Slice

  • Show Take ownership in the unread-update sheet only for an open, unassigned issue.
  • Claim through the existing bounded claim endpoint.
  • Reconcile the confirmed issue into My Work while preserving the unread update, then offer Add to Today.
  • Preserve drafts and truthful state on conflict or retryable failure.

Acceptance

  • Claimability is derived from normalized issue detail; PRs, closed, and assigned issues are not claimable.
  • One claim tap sends one request and disables duplicates.
  • Success yields one My Work issue carrying its unread-update badge and enables Add to Today.
  • A 409 removes stale claimability without marking the update read.
  • Retryable failure keeps the conversation, draft, and action recoverable.
  • Controls remain phone-safe at 390x844 and 320x568.
  • Focused behavioral tests and the full suite pass.
## Problem On mobile, an operator reading an actionable unread issue update must leave the conversation, find the issue again, claim it elsewhere, then return to plan it. This breaks notification triage and risks losing context. ## Slice - Show **Take ownership** in the unread-update sheet only for an open, unassigned issue. - Claim through the existing bounded claim endpoint. - Reconcile the confirmed issue into My Work while preserving the unread update, then offer **Add to Today**. - Preserve drafts and truthful state on conflict or retryable failure. ## Acceptance - Claimability is derived from normalized issue detail; PRs, closed, and assigned issues are not claimable. - One claim tap sends one request and disables duplicates. - Success yields one My Work issue carrying its unread-update badge and enables Add to Today. - A 409 removes stale claimability without marking the update read. - Retryable failure keeps the conversation, draft, and action recoverable. - Controls remain phone-safe at 390x844 and 320x568. - Focused behavioral tests and the full suite pass.
timmy self-assigned this 2026-08-08 17:10:07 +00:00
timmy closed this issue 2026-08-08 17:20:48 +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#321
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?