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

Open delegated Filed issues in read-only detail #872

New Issue
Closed
opened 2026-08-15 05:27:52 +00:00 by timmy · 0 comments
timmy commented 2026-08-15 05:27:52 +00:00
Owner
Copy Link

Problem

The Filed queue now retains issues authored by the operator, including delegated and unassigned issues, but those cards serialize as assigned issue routes. Both route resolution and issue detail require the current operator to be an assignee, so the primary Filed flow ends in a 404 instead of a readable filing.

User flow

  • A delegated or unassigned authored issue opens from Filed and from the filing receipt.
  • The issue sheet shows title, body, ownership, labels, milestone, due date, conversation, and canonical Gitea link.
  • The sheet is explicitly read-only when the operator is not assigned: no comments, editing, planning, handoff, release, close, defer, or blocker mutations.
  • A crafted Filed route for an issue authored by someone else returns 404.
  • A self-assigned authored issue keeps the normal assigned route and controls.

Acceptance tests

  1. #/my-work/filed/<owner>/<repo>/<number> round-trips and resolves only an open issue authored by the authenticated Gitea user.
  2. Filed detail authorization is constant-request and author-verified; unrelated authored identity returns 404.
  3. Delegated Filed cards and cold routes load read-only details and preserve browser Back to Filed.
  4. Self-assigned filings retain normal assigned capabilities.
  5. Focused route/API/UI tests and the full suite pass.

Evidence / non-duplication

frontend/work-route.js supports only issue/pull/review detail kinds; src/gitea_proxy.py::resolve_work_route and src/main.py::assigned_issue_detail require assignment. Historical #870 and PR #871 added Filed discovery/filtering only; all issue titles and recent commits contain no authored read-only detail implementation.

## Problem The Filed queue now retains issues authored by the operator, including delegated and unassigned issues, but those cards serialize as assigned issue routes. Both route resolution and issue detail require the current operator to be an assignee, so the primary Filed flow ends in a 404 instead of a readable filing. ## User flow - A delegated or unassigned authored issue opens from Filed and from the filing receipt. - The issue sheet shows title, body, ownership, labels, milestone, due date, conversation, and canonical Gitea link. - The sheet is explicitly read-only when the operator is not assigned: no comments, editing, planning, handoff, release, close, defer, or blocker mutations. - A crafted Filed route for an issue authored by someone else returns 404. - A self-assigned authored issue keeps the normal assigned route and controls. ## Acceptance tests 1. `#/my-work/filed/<owner>/<repo>/<number>` round-trips and resolves only an open issue authored by the authenticated Gitea user. 2. Filed detail authorization is constant-request and author-verified; unrelated authored identity returns 404. 3. Delegated Filed cards and cold routes load read-only details and preserve browser Back to Filed. 4. Self-assigned filings retain normal assigned capabilities. 5. Focused route/API/UI tests and the full suite pass. ## Evidence / non-duplication `frontend/work-route.js` supports only issue/pull/review detail kinds; `src/gitea_proxy.py::resolve_work_route` and `src/main.py::assigned_issue_detail` require assignment. Historical #870 and PR #871 added Filed discovery/filtering only; all issue titles and recent commits contain no authored read-only detail implementation.
timmy self-assigned this 2026-08-15 05:27:52 +00:00
timmy closed this issue 2026-08-15 05:48:40 +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#872
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?