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

Plan selected mobile Search issues into a release milestone #815

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

User problem

On a phone, release leads can find and select related open issues across mobile Search, but must open every issue separately to claim it, assign a milestone, and set a due date. Search currently only supports batch Today and Later actions.

Vertical slice

Add a Plan release action for selected Search issues from one repository. Before mutation, show a mobile review with an open milestone and optional due date. Revalidate/claim only unassigned issues, then apply the selected milestone and deadline through existing assigned-issue APIs. Preserve Search selection on failure and make interrupted work resumable.

Acceptance criteria

  • Plan release is enabled only for selected open issues from one repository; mixed-repository selection is rejected before network mutation.
  • Review fetches and renders server-confirmed open milestones, optional YYYY-MM-DD due date, affected issues, and touch-safe cancel/confirm controls.
  • Confirmation claims only claimable issues, then applies milestone and optional due date; it does not modify Today or Later.
  • Durable account-bound journal resumes only unfinished operations and reports exact success/failure counts.
  • Success keeps the Search query/scope/session and announces the planned count and milestone.
  • Behavioral controller tests cover single-repository validation, no-mutation review, mutation ordering, partial failure/resume, and mobile DOM/CSS contracts.
  • Full test suite and Gitea Actions pass.

Non-duplication evidence

Historical issue/PR title audit (811 records) and recent commit history found individual milestone planning (#203/#204), Search-to-Today (#809-#812), and Search-to-Later (#813/#814), but no batch Search-to-milestone/release workflow. There are no open issues or PRs for this behavior.

## User problem On a phone, release leads can find and select related open issues across mobile Search, but must open every issue separately to claim it, assign a milestone, and set a due date. Search currently only supports batch Today and Later actions. ## Vertical slice Add a **Plan release** action for selected Search issues from one repository. Before mutation, show a mobile review with an open milestone and optional due date. Revalidate/claim only unassigned issues, then apply the selected milestone and deadline through existing assigned-issue APIs. Preserve Search selection on failure and make interrupted work resumable. ## Acceptance criteria - Plan release is enabled only for selected open issues from one repository; mixed-repository selection is rejected before network mutation. - Review fetches and renders server-confirmed open milestones, optional YYYY-MM-DD due date, affected issues, and touch-safe cancel/confirm controls. - Confirmation claims only claimable issues, then applies milestone and optional due date; it does not modify Today or Later. - Durable account-bound journal resumes only unfinished operations and reports exact success/failure counts. - Success keeps the Search query/scope/session and announces the planned count and milestone. - Behavioral controller tests cover single-repository validation, no-mutation review, mutation ordering, partial failure/resume, and mobile DOM/CSS contracts. - Full test suite and Gitea Actions pass. ## Non-duplication evidence Historical issue/PR title audit (811 records) and recent commit history found individual milestone planning (#203/#204), Search-to-Today (#809-#812), and Search-to-Later (#813/#814), but no batch Search-to-milestone/release workflow. There are no open issues or PRs for this behavior.
timmy self-assigned this 2026-08-14 09:21:00 +00:00
timmy closed this issue 2026-08-14 09:34:29 +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#815
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?