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

Select priority labels while creating mobile issues #163

New Issue
Closed
opened 2026-08-07 03:49:22 +00:00 by timmy · 0 comments
timmy commented 2026-08-07 03:49:22 +00:00
Owner
Copy Link

User value

Complete capture and triage in one phone-native flow: repository labels load after repository selection, selected labels survive interruption, and a newly self-assigned issue appears at the right priority in My Work.

Acceptance criteria

  • Load and display labels for the selected repository with priority labels first.
  • Persist selected label IDs with the issue draft and clear them only after confirmed creation.
  • Validate selected labels belong to the target repository before creating the issue.
  • Create and self-assign the issue with selected labels; return confirmed labels.
  • Preserve no-label creation behavior and keep controls usable at 320px with 44px touch targets.
  • Add behavioral frontend/API/proxy tests and pass the full suite.

Evidence

Issue capture currently sends only title/body (frontend/create-issue-sheet.js, src/main.py, src/gitea_proxy.py), while frontend/my-work.js already prioritizes P0/critical labels. Historical issue/PR titles and recent commits contain no label-selection or capture-time triage feature.

## User value Complete capture and triage in one phone-native flow: repository labels load after repository selection, selected labels survive interruption, and a newly self-assigned issue appears at the right priority in My Work. ## Acceptance criteria - Load and display labels for the selected repository with priority labels first. - Persist selected label IDs with the issue draft and clear them only after confirmed creation. - Validate selected labels belong to the target repository before creating the issue. - Create and self-assign the issue with selected labels; return confirmed labels. - Preserve no-label creation behavior and keep controls usable at 320px with 44px touch targets. - Add behavioral frontend/API/proxy tests and pass the full suite. ## Evidence Issue capture currently sends only title/body (`frontend/create-issue-sheet.js`, `src/main.py`, `src/gitea_proxy.py`), while `frontend/my-work.js` already prioritizes P0/critical labels. Historical issue/PR titles and recent commits contain no label-selection or capture-time triage feature.
timmy self-assigned this 2026-08-07 03:49:22 +00:00
timmy closed this issue 2026-08-07 03:56:57 +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#163
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?