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

File a related issue from the confirmed filing receipt #868

New Issue
Closed
opened 2026-08-15 03:59:26 +00:00 by timmy · 0 comments
timmy commented 2026-08-15 03:59:26 +00:00
Owner
Copy Link

Product gap

After a delegated or unassigned issue is confirmed, File another starts from a blank capture. Operators decomposing one discovery into related work must reselect the same repository, issue type, owner, labels, milestone, and due date.

Current evidence: frontend/issue-filing-receipt.js only dispatches blank onFileAnother; frontend/dashboard.js wires it to #new-issue; the successful capture is cleared before the receipt appears. No historical issue title or recent commit implements safe related-plan reuse.

Acceptance criteria

  • Add File related issue to the confirmed receipt.
  • Preserve only repository, selected issue type/template, owner intent, labels, milestone, and due date.
  • Start with a blank focused title and pristine template scaffold (when selected).
  • Reset completed body content, evidence, blockers, Today estimate/completion intent, duplicate acknowledgement, and operation identity.
  • Keep ordinary File another, Open, Share, Done, Escape, offline queueing, and mobile 44px/safe-area behavior intact.
  • A related submission receives a fresh idempotency identity and creates a distinct issue exactly once.

Verification

Strict TDD behavioral tests, full suite, and rendered 390x844 mobile flow.

## Product gap After a delegated or unassigned issue is confirmed, **File another** starts from a blank capture. Operators decomposing one discovery into related work must reselect the same repository, issue type, owner, labels, milestone, and due date. Current evidence: `frontend/issue-filing-receipt.js` only dispatches blank `onFileAnother`; `frontend/dashboard.js` wires it to `#new-issue`; the successful capture is cleared before the receipt appears. No historical issue title or recent commit implements safe related-plan reuse. ## Acceptance criteria - Add **File related issue** to the confirmed receipt. - Preserve only repository, selected issue type/template, owner intent, labels, milestone, and due date. - Start with a blank focused title and pristine template scaffold (when selected). - Reset completed body content, evidence, blockers, Today estimate/completion intent, duplicate acknowledgement, and operation identity. - Keep ordinary **File another**, Open, Share, Done, Escape, offline queueing, and mobile 44px/safe-area behavior intact. - A related submission receives a fresh idempotency identity and creates a distinct issue exactly once. ## Verification Strict TDD behavioral tests, full suite, and rendered 390x844 mobile flow.
timmy self-assigned this 2026-08-15 03:59:26 +00:00
timmy closed this issue 2026-08-15 04:16:17 +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#868
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?