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

Warn about duplicate issues during mobile capture #371

New Issue
Closed
opened 2026-08-09 04:29:51 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-09 04:29:51 +00:00
Member
Copy Link

User problem

Mobile issue capture durably queues work immediately, but does not check whether the selected repository already has an open issue with a similar title. This fragments discussion and duplicates delivery effort.

Vertical slice

Add advisory, duplicate-aware capture to the New issue sheet. After a repository and meaningful title are entered, search for open issues in that repository. Show up to three candidates. If candidates exist, the first create attempt must pause before outbox admission; the operator can review the matches or explicitly create anyway. Changing the repository or title invalidates that acknowledgement. Offline/search failures remain non-blocking and preserve existing durable capture.

Acceptance criteria

  • Only open issue results from the selected repository are candidates; pull requests, closed items, and cross-repository results are excluded.
  • Stale search responses cannot replace results for a newer repository/title.
  • An unacknowledged match prevents outbox enqueue; explicit Create anyway allows exactly one existing idempotent admission.
  • Editing repository/title requires acknowledgement again.
  • Offline, timeout, or search failure displays advisory status but never disables capture.
  • Candidate controls are keyboard accessible, announced via aria-live, at least 44px tall, and do not overflow a 390px viewport.
  • Behavioral tests cover filtering, stale responses, guard/override reset, and failure fallback.

Evidence / non-duplication

Current origin/main at 1bf759d submits directly in frontend/dashboard.js:2577-2613; frontend/create-issue-sheet.js has no duplicate lookup. Existing search/preview issues #195/#197/#199 and capture issues #159/#177/#221/#301 do not connect search to the create decision. All 188 historical issue titles and recent commits were checked; none ships this behavior.

## User problem Mobile issue capture durably queues work immediately, but does not check whether the selected repository already has an open issue with a similar title. This fragments discussion and duplicates delivery effort. ## Vertical slice Add advisory, duplicate-aware capture to the New issue sheet. After a repository and meaningful title are entered, search for open issues in that repository. Show up to three candidates. If candidates exist, the first create attempt must pause before outbox admission; the operator can review the matches or explicitly create anyway. Changing the repository or title invalidates that acknowledgement. Offline/search failures remain non-blocking and preserve existing durable capture. ## Acceptance criteria - Only open issue results from the selected repository are candidates; pull requests, closed items, and cross-repository results are excluded. - Stale search responses cannot replace results for a newer repository/title. - An unacknowledged match prevents outbox enqueue; explicit Create anyway allows exactly one existing idempotent admission. - Editing repository/title requires acknowledgement again. - Offline, timeout, or search failure displays advisory status but never disables capture. - Candidate controls are keyboard accessible, announced via aria-live, at least 44px tall, and do not overflow a 390px viewport. - Behavioral tests cover filtering, stale responses, guard/override reset, and failure fallback. ## Evidence / non-duplication Current `origin/main` at `1bf759d` submits directly in `frontend/dashboard.js:2577-2613`; `frontend/create-issue-sheet.js` has no duplicate lookup. Existing search/preview issues #195/#197/#199 and capture issues #159/#177/#221/#301 do not connect search to the create decision. All 188 historical issue titles and recent commits were checked; none ships this behavior.
timmy was assigned by rockachopa 2026-08-09 04:29:51 +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#371
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?