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

Make mobile issue sheets read-first with on-demand planning #215

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

Problem

Opening an assigned issue currently places label, due-date, and milestone editors before the description and conversation, and immediately requests label and milestone catalogs even when the user only wants to read or reply. On a phone this delays context behind several viewport-heights of controls.

Slice

Reorder the assigned-issue sheet around reading and conversation. Put title/status/metadata, description, and conversation first; place title/body editing, labels, due date, and milestone inside one touch-safe Plan & edit disclosure. Lazy-load label and milestone catalogs only on first expansion, without refetching on repeated expansion. Preserve existing drafts and actions.

Acceptance

  • Opening an issue does not request label or milestone catalogs.
  • Description and conversation appear before the collapsed Plan & edit disclosure.
  • First expansion requests labels and milestones once; subsequent expansion does not refetch.
  • Planning-load failure leaves reading and commenting usable and exposes an in-disclosure retry.
  • Disclosure and controls are keyboard-operable, at least 44px tall, and the sheet has no horizontal overflow at 320px.
  • Existing label, due-date, milestone, content-edit, route, and draft behavior remains green.

Non-duplication evidence

Historical issues add the individual editing capabilities (#173, #189, #191, #203), conversations (#209), and routes (#205/#207), but no issue or recent commit covers read-first hierarchy or lazy planning metadata.

Implementation must use strict RED-GREEN-REFACTOR and include behavioral tests.

## Problem Opening an assigned issue currently places label, due-date, and milestone editors before the description and conversation, and immediately requests label and milestone catalogs even when the user only wants to read or reply. On a phone this delays context behind several viewport-heights of controls. ## Slice Reorder the assigned-issue sheet around reading and conversation. Put title/status/metadata, description, and conversation first; place title/body editing, labels, due date, and milestone inside one touch-safe **Plan & edit** disclosure. Lazy-load label and milestone catalogs only on first expansion, without refetching on repeated expansion. Preserve existing drafts and actions. ## Acceptance - Opening an issue does not request label or milestone catalogs. - Description and conversation appear before the collapsed Plan & edit disclosure. - First expansion requests labels and milestones once; subsequent expansion does not refetch. - Planning-load failure leaves reading and commenting usable and exposes an in-disclosure retry. - Disclosure and controls are keyboard-operable, at least 44px tall, and the sheet has no horizontal overflow at 320px. - Existing label, due-date, milestone, content-edit, route, and draft behavior remains green. ## Non-duplication evidence Historical issues add the individual editing capabilities (#173, #189, #191, #203), conversations (#209), and routes (#205/#207), but no issue or recent commit covers read-first hierarchy or lazy planning metadata. Implementation must use strict RED-GREEN-REFACTOR and include behavioral tests.
timmy was assigned by rockachopa 2026-08-07 17:38:02 +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#215
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?