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

Reply to delegated issues from mobile Filed #876

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

User problem

An issue author can revisit a delegated issue in the mobile Filed queue, but the current read-only detail hides older conversation pages and the reply composer. That breaks the capture → delegate → clarify loop and forces a context switch to Gitea.

Vertical slice

Allow the authenticated issue author to load the complete conversation and post an idempotent follow-up from Filed, while every ownership/planning mutation remains unavailable.

Acceptance criteria

  • access=filed conversation reads and comment writes authorize with is_authored_issue; requests for another author's issue return 404.
  • Filed conversation pagination works and preserves already loaded messages on retry.
  • Filed follow-up uses the existing durable draft and idempotency key behavior; a confirmed post clears the draft and appends exactly once.
  • The Filed sheet exposes only conversation/reply capabilities; edit, ownership, labels, milestones, blockers, defer, release, handoff, and close controls remain absent.
  • Mobile composer remains keyboard-safe and touch targets remain at least 44px.
  • Focused behavioral tests and the complete suite pass.
## User problem An issue author can revisit a delegated issue in the mobile Filed queue, but the current read-only detail hides older conversation pages and the reply composer. That breaks the capture → delegate → clarify loop and forces a context switch to Gitea. ## Vertical slice Allow the authenticated issue author to load the complete conversation and post an idempotent follow-up from Filed, while every ownership/planning mutation remains unavailable. ## Acceptance criteria - `access=filed` conversation reads and comment writes authorize with `is_authored_issue`; requests for another author's issue return 404. - Filed conversation pagination works and preserves already loaded messages on retry. - Filed follow-up uses the existing durable draft and idempotency key behavior; a confirmed post clears the draft and appends exactly once. - The Filed sheet exposes only conversation/reply capabilities; edit, ownership, labels, milestones, blockers, defer, release, handoff, and close controls remain absent. - Mobile composer remains keyboard-safe and touch targets remain at least 44px. - Focused behavioral tests and the complete suite pass.
timmy self-assigned this 2026-08-15 06:51:21 +00:00
timmy closed this issue 2026-08-15 07:02:52 +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#876
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?