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

Choose blockers while filing a mobile issue #841

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

Evidence

The mobile New issue flow persists labels, milestone, due date, and evidence, but cannot capture known dependencies. Existing authenticated blocker APIs already support desired-state relationships after creation. Historical blocker work manages existing issues only; issue history contains no capture-time blocker selection or checkpointed blocker delivery.

User flow

From New issue, choose accessible open issues as blockers, review them with the complete filing payload, and create the issue once. Deliver relationships through retry-safe checkpoints. A blocked issue must not auto-start.

Acceptance

  • Search and select blockers during filing, with bounded accessible mobile controls.
  • Preserve blocker identities through Back to edit, Drafts, offline admission, and reload.
  • Final review displays blocker repository, number, and title.
  • Create the issue exactly once; retry only incomplete blocker relationships after partial failure.
  • Create and start does not start a blocked issue and offers truthful blocker and My Work navigation.
  • Behavioral tests cover online, offline, partial failure, and 320px rendering.
  • Full suite and Gitea Actions pass.

Implementation files include frontend/create-issue-sheet.js, issue-filing-review.js, unfiled-captures.js, issue-outbox.js, background-issue-sync.js, index.html, dashboard.css, dashboard.js, and focused tests.

## Evidence The mobile New issue flow persists labels, milestone, due date, and evidence, but cannot capture known dependencies. Existing authenticated blocker APIs already support desired-state relationships after creation. Historical blocker work manages existing issues only; issue history contains no capture-time blocker selection or checkpointed blocker delivery. ## User flow From New issue, choose accessible open issues as blockers, review them with the complete filing payload, and create the issue once. Deliver relationships through retry-safe checkpoints. A blocked issue must not auto-start. ## Acceptance - Search and select blockers during filing, with bounded accessible mobile controls. - Preserve blocker identities through Back to edit, Drafts, offline admission, and reload. - Final review displays blocker repository, number, and title. - Create the issue exactly once; retry only incomplete blocker relationships after partial failure. - Create and start does not start a blocked issue and offers truthful blocker and My Work navigation. - Behavioral tests cover online, offline, partial failure, and 320px rendering. - Full suite and Gitea Actions pass. Implementation files include frontend/create-issue-sheet.js, issue-filing-review.js, unfiled-captures.js, issue-outbox.js, background-issue-sync.js, index.html, dashboard.css, dashboard.js, and focused tests.
timmy closed this issue 2026-08-14 17:36:43 +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
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#841
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?