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

Release mobile issue assignments from My Work #183

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

User problem

A mobile user can claim or create work in the dashboard, but cannot relinquish a mistaken or stale assignment without leaving the app for Gitea. This makes the Find Work → claim → My Work loop one-way.

Vertical slice

Add a confirmed Release assignment action to the assigned-issue sheet. It removes only the authenticated user, preserves peer assignees, updates My Work after confirmation, and invalidates Find Work so a newly unassigned issue can reappear.

Acceptance criteria

  • Assigned issue sheet exposes a 44px mobile-safe release action with confirmation.
  • Repeated taps produce one request; cancellation produces none.
  • Backend verifies an open non-PR issue is assigned to the current user, removes only that user, and confirms the returned assignees.
  • Successful release removes the issue from local My Work; failures retain it and allow retry.
  • Sole-assignee release invalidates available-work cache; co-assignee release does not advertise it as available.
  • Endpoint is no-store, bounded, returns truthful 404/503 responses, and full tests pass.
## User problem A mobile user can claim or create work in the dashboard, but cannot relinquish a mistaken or stale assignment without leaving the app for Gitea. This makes the Find Work → claim → My Work loop one-way. ## Vertical slice Add a confirmed **Release assignment** action to the assigned-issue sheet. It removes only the authenticated user, preserves peer assignees, updates My Work after confirmation, and invalidates Find Work so a newly unassigned issue can reappear. ## Acceptance criteria - Assigned issue sheet exposes a 44px mobile-safe release action with confirmation. - Repeated taps produce one request; cancellation produces none. - Backend verifies an open non-PR issue is assigned to the current user, removes only that user, and confirms the returned assignees. - Successful release removes the issue from local My Work; failures retain it and allow retry. - Sole-assignee release invalidates available-work cache; co-assignee release does not advertise it as available. - Endpoint is no-store, bounded, returns truthful 404/503 responses, and full tests pass.
timmy self-assigned this 2026-08-07 09:18:48 +00:00
timmy closed this issue 2026-08-07 09:25:07 +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#183
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?