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

Plan new mobile issues at capture time #221

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

User outcome

Mobile users can select an open milestone and optional due date while creating a self-assigned issue, so captured work enters the correct release lane without a second edit flow.

Evidence

Current capture accepts repository, title, description, and labels only; milestone/due-date controls exist only after creation. Historical #159/#163 cover creation/labels, while #191/#203 cover post-creation scheduling/planning. No issue or recent commit combines planning with capture.

Acceptance criteria

  • New issue sheet loads open milestones for the selected repository and exposes optional milestone/due-date controls on mobile.
  • Draft recovery and operation identity include both planning fields.
  • Creation validates milestone ownership/state and date format before one upstream create request.
  • Omitted planning fields preserve existing behavior; option-load failure does not block basic capture.
  • Behavioral tests cover payloads, validation, idempotency, draft recovery, and mobile rendering.
## User outcome Mobile users can select an open milestone and optional due date while creating a self-assigned issue, so captured work enters the correct release lane without a second edit flow. ## Evidence Current capture accepts repository, title, description, and labels only; milestone/due-date controls exist only after creation. Historical #159/#163 cover creation/labels, while #191/#203 cover post-creation scheduling/planning. No issue or recent commit combines planning with capture. ## Acceptance criteria - New issue sheet loads open milestones for the selected repository and exposes optional milestone/due-date controls on mobile. - Draft recovery and operation identity include both planning fields. - Creation validates milestone ownership/state and date format before one upstream create request. - Omitted planning fields preserve existing behavior; option-load failure does not block basic capture. - Behavioral tests cover payloads, validation, idempotency, draft recovery, and mobile rendering.
timmy self-assigned this 2026-08-07 19:09:33 +00:00
timmy closed this issue 2026-08-07 19:19:39 +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#221
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?