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

Select repository issue templates while filing on mobile #845

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

Product gap

The mobile filing flow captures evidence and planning metadata but still starts every issue from an unstructured title and note. Gitea exposes repository issue templates, yet the dashboard does not load or apply them.

Vertical slice

After repository selection, offer Blank issue plus available repository templates. Applying a template preserves captured title/note/evidence, appends a bounded repository scaffold, maps only valid template labels, survives review/drafts/offline delivery through the resulting issue payload, and degrades to blank filing when templates are unavailable.

Acceptance criteria

  • Access-checked, timeout-bounded API normalizes null/malformed/oversized template responses.
  • Mobile Issue type control appears only when templates exist; blank filing remains the default.
  • Applying/switching templates preserves authored title/note and evidence without duplicating content.
  • Valid configured labels are selected; unknown labels are ignored.
  • Final review displays the selected issue type and exact body submitted.
  • Repository changes suppress stale template responses and clear template-derived state safely.
  • Behavioral tests cover API normalization, client application, review, failure fallback, and mobile markup.

Non-duplication evidence

All 426 historical issue titles, open PRs, recent commits, and releases through v0.1.0-rc.1037 were checked. No issue or commit implements repository template-aware mobile filing.

## Product gap The mobile filing flow captures evidence and planning metadata but still starts every issue from an unstructured title and note. Gitea exposes repository issue templates, yet the dashboard does not load or apply them. ## Vertical slice After repository selection, offer Blank issue plus available repository templates. Applying a template preserves captured title/note/evidence, appends a bounded repository scaffold, maps only valid template labels, survives review/drafts/offline delivery through the resulting issue payload, and degrades to blank filing when templates are unavailable. ## Acceptance criteria - Access-checked, timeout-bounded API normalizes null/malformed/oversized template responses. - Mobile Issue type control appears only when templates exist; blank filing remains the default. - Applying/switching templates preserves authored title/note and evidence without duplicating content. - Valid configured labels are selected; unknown labels are ignored. - Final review displays the selected issue type and exact body submitted. - Repository changes suppress stale template responses and clear template-derived state safely. - Behavioral tests cover API normalization, client application, review, failure fallback, and mobile markup. ## Non-duplication evidence All 426 historical issue titles, open PRs, recent commits, and releases through v0.1.0-rc.1037 were checked. No issue or commit implements repository template-aware mobile filing.
timmy self-assigned this 2026-08-14 18:49:38 +00:00
timmy closed this issue 2026-08-14 19:18:03 +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#845
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?