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

Revise an open delegated issue from mobile Filed #887

New Issue
Closed
opened 2026-08-15 10:50:07 +00:00 by timmy · 0 comments
timmy commented 2026-08-15 10:50:07 +00:00
Owner
Copy Link

Problem

An issue author can track, read, reply to, review, and withdraw a delegated filing in mobile Filed, but cannot correct its canonical title or description. The existing editor and optimistic concurrency flow only authorize current assignees, forcing authors out to Gitea for typos or clarified acceptance criteria.

Evidence

  • frontend/issue-sheet.js loads delegated filings through access=filed as read-only.
  • frontend/dashboard.css hides #issue-planning, including the existing title/body editor, for that state.
  • src/main.py and src/gitea_proxy.py restrict content updates to assigned issues, while Filed detail/comments already reauthorize authorship.
  • Historical issue/PR review found adjacent assigned editing (#189), pre-filing review (#833), replies (#876), and withdrawal (#884), but no author-scoped canonical revision after delegation.

Scope

Add a Revise filing flow for open authored delegated issues. Reuse the current title/body editor, preserve optimistic concurrency and drafts, authorize authorship at mutation time, refresh Filed detail in place, and never change assignees. Closed, non-authored, and pull-request targets must not mutate upstream.

Acceptance

  • An open delegated issue authored by the operator can edit title/body through access=filed.
  • Closed, non-authored, and pull-request targets return 404 before upstream mutation.
  • Stale expected_updated_at returns 409 and preserves entered content.
  • A successful save refreshes visible Filed content and leaves assignment unchanged.
  • The 320px/390px rendered editor has no horizontal overflow, reachable 44px Save/Cancel controls, and browser Back closes editing before detail.
  • Focused and full suites pass.
## Problem An issue author can track, read, reply to, review, and withdraw a delegated filing in mobile **Filed**, but cannot correct its canonical title or description. The existing editor and optimistic concurrency flow only authorize current assignees, forcing authors out to Gitea for typos or clarified acceptance criteria. ## Evidence - `frontend/issue-sheet.js` loads delegated filings through `access=filed` as read-only. - `frontend/dashboard.css` hides `#issue-planning`, including the existing title/body editor, for that state. - `src/main.py` and `src/gitea_proxy.py` restrict content updates to assigned issues, while Filed detail/comments already reauthorize authorship. - Historical issue/PR review found adjacent assigned editing (#189), pre-filing review (#833), replies (#876), and withdrawal (#884), but no author-scoped canonical revision after delegation. ## Scope Add a **Revise filing** flow for open authored delegated issues. Reuse the current title/body editor, preserve optimistic concurrency and drafts, authorize authorship at mutation time, refresh Filed detail in place, and never change assignees. Closed, non-authored, and pull-request targets must not mutate upstream. ## Acceptance - An open delegated issue authored by the operator can edit title/body through `access=filed`. - Closed, non-authored, and pull-request targets return `404` before upstream mutation. - Stale `expected_updated_at` returns `409` and preserves entered content. - A successful save refreshes visible Filed content and leaves assignment unchanged. - The 320px/390px rendered editor has no horizontal overflow, reachable 44px Save/Cancel controls, and browser Back closes editing before detail. - Focused and full suites pass.
timmy self-assigned this 2026-08-15 10:50:07 +00:00
timmy closed this issue 2026-08-15 11:04:13 +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#887
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?