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

Complete delegated mobile filing with a shareable issue receipt #866

New Issue
Closed
opened 2026-08-15 02:51:18 +00:00 by timmy · 0 comments
timmy commented 2026-08-15 02:51:18 +00:00
Owner
Copy Link

Problem

Mobile issue creation now supports assigning a teammate or no owner, but confirmed delivery only attempts to open the result through My Work. Those issues are intentionally absent from the current operator’s My Work, leaving only transient status text; background receipts also route to an authorization-ineligible My Work detail.

Product slice

After any confirmed filing that is not opened as current-user work, present an accessible mobile completion receipt with the confirmed repository, issue number, title, ownership outcome, canonical Gitea link, Share/Copy, File another, and Done. Background delivery notifications for created issues must open the validated canonical issue URL.

Acceptance

  • Confirmed delegated and unassigned creations display a keyboard-safe 320/390px receipt with 44px actions and no horizontal overflow.
  • Open in Gitea uses the exact validated URL returned by the API.
  • Share uses Web Share and falls back to copying that same URL; cancellation does not dismiss the receipt.
  • File another returns to a clean capture flow; Done restores focus.
  • Offline admission remains truthful (no number/link until confirmation).
  • Background delivery notifications open canonical confirmed issue URLs, never an ineligible My Work route.
  • Self-assigned Create & start behavior remains unchanged.

Evidence

frontend/dashboard.js only opens confirmed issues found in lastMyWork; frontend/background-issue-sync.js currently builds a My Work route for all created issues. No matching title/behavior exists among 436 historical issues or recent commits.

## Problem Mobile issue creation now supports assigning a teammate or no owner, but confirmed delivery only attempts to open the result through My Work. Those issues are intentionally absent from the current operator’s My Work, leaving only transient status text; background receipts also route to an authorization-ineligible My Work detail. ## Product slice After any confirmed filing that is not opened as current-user work, present an accessible mobile completion receipt with the confirmed repository, issue number, title, ownership outcome, canonical Gitea link, Share/Copy, File another, and Done. Background delivery notifications for created issues must open the validated canonical issue URL. ## Acceptance - Confirmed delegated and unassigned creations display a keyboard-safe 320/390px receipt with 44px actions and no horizontal overflow. - Open in Gitea uses the exact validated URL returned by the API. - Share uses Web Share and falls back to copying that same URL; cancellation does not dismiss the receipt. - File another returns to a clean capture flow; Done restores focus. - Offline admission remains truthful (no number/link until confirmation). - Background delivery notifications open canonical confirmed issue URLs, never an ineligible My Work route. - Self-assigned Create & start behavior remains unchanged. ## Evidence `frontend/dashboard.js` only opens confirmed issues found in `lastMyWork`; `frontend/background-issue-sync.js` currently builds a My Work route for all created issues. No matching title/behavior exists among 436 historical issues or recent commits.
timmy self-assigned this 2026-08-15 02:51:32 +00:00
timmy closed this issue 2026-08-15 03:10:28 +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#866
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?