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

Capture shared mobile content as a planned issue #223

New Issue
Closed
opened 2026-08-07 19:49:07 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-07 19:49:07 +00:00
Member
Copy Link

User problem

Mobile users who encounter work in a browser, chat, or monitoring app must open Stackchain and manually reconstruct the source as an issue, despite the dashboard already having a draft-safe planned issue capture flow.

Vertical slice

Make Stackchain an installable PWA and Android Web Share Target. Normalize a shared title/text/URL into the existing New issue draft, preserve an existing draft instead of overwriting it, stage shared content until repositories load, and never cache authenticated API traffic in the service worker.

Acceptance tests

  • Sharing title/text/URL opens New issue with bounded normalized content and the source URL exactly once.
  • An existing issue draft is never silently overwritten; shared content remains recoverable until explicitly selected.
  • Reload preserves accepted shared content through the existing draft store.
  • Manifest and root-scoped service worker are served with correct content types/scope; API and mutation requests are never cached.
  • Mobile conflict actions are at least 44px and status is announced accessibly.
  • Existing create, plan, idempotency, and post-create flows remain green.

Non-duplication evidence

No historical issue title/body or recent commit adds a web app manifest, service worker, inbound Web Share Target, or OS-to-dashboard capture. Existing #159/#177/#211/#221 cover only in-dashboard capture, retry safety, draft recovery, and planning.

## User problem Mobile users who encounter work in a browser, chat, or monitoring app must open Stackchain and manually reconstruct the source as an issue, despite the dashboard already having a draft-safe planned issue capture flow. ## Vertical slice Make Stackchain an installable PWA and Android Web Share Target. Normalize a shared title/text/URL into the existing New issue draft, preserve an existing draft instead of overwriting it, stage shared content until repositories load, and never cache authenticated API traffic in the service worker. ## Acceptance tests - Sharing title/text/URL opens New issue with bounded normalized content and the source URL exactly once. - An existing issue draft is never silently overwritten; shared content remains recoverable until explicitly selected. - Reload preserves accepted shared content through the existing draft store. - Manifest and root-scoped service worker are served with correct content types/scope; API and mutation requests are never cached. - Mobile conflict actions are at least 44px and status is announced accessibly. - Existing create, plan, idempotency, and post-create flows remain green. ## Non-duplication evidence No historical issue title/body or recent commit adds a web app manifest, service worker, inbound Web Share Target, or OS-to-dashboard capture. Existing #159/#177/#211/#221 cover only in-dashboard capture, retry safety, draft recovery, and planning.
timmy was assigned by rockachopa 2026-08-07 19:49:07 +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#223
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?