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

File mobile issues without assigning an owner #855

New Issue
Closed
opened 2026-08-14 22:50:37 +00:00 by timmy · 0 comments
timmy commented 2026-08-14 22:50:37 +00:00
Owner
Copy Link

Problem

Mobile issue filing currently forces assignment to the signed-in operator or a teammate. Operators cannot capture backlog work without polluting My Work and Today ownership signals.

Vertical slice

Add an explicit No owner choice throughout mobile issue filing. Preserve it across drafts, duplicate review, offline outbox delivery, and final review; create a genuinely unassigned Gitea issue; keep Create & start unavailable for unowned work. Existing clients that omit the new intent retain self-assignment.

Acceptance tests

  • Owner choices include Me, No owner, and eligible teammates.
  • Final review and draft/outbox restore preserve and display No owner.
  • Online and offline delivery create an issue with no assignees.
  • Create & start is unavailable for No owner and does not create an issue.
  • Contradictory unassigned plus named-assignee payloads are rejected.
  • Existing omitted ownership intent still assigns the signed-in operator.

Evidence / non-duplication

Current UI and API default missing teammate selection to the operator. Historical issue #843 added Me-or-teammate selection; #175 added downstream discovery/claiming of unassigned issues. Neither supports creating unassigned issues. Audit of all 431 historical titles and recent main commits found no duplicate behavior.

## Problem Mobile issue filing currently forces assignment to the signed-in operator or a teammate. Operators cannot capture backlog work without polluting My Work and Today ownership signals. ## Vertical slice Add an explicit **No owner** choice throughout mobile issue filing. Preserve it across drafts, duplicate review, offline outbox delivery, and final review; create a genuinely unassigned Gitea issue; keep Create & start unavailable for unowned work. Existing clients that omit the new intent retain self-assignment. ## Acceptance tests - Owner choices include Me, No owner, and eligible teammates. - Final review and draft/outbox restore preserve and display No owner. - Online and offline delivery create an issue with no assignees. - Create & start is unavailable for No owner and does not create an issue. - Contradictory unassigned plus named-assignee payloads are rejected. - Existing omitted ownership intent still assigns the signed-in operator. ## Evidence / non-duplication Current UI and API default missing teammate selection to the operator. Historical issue #843 added Me-or-teammate selection; #175 added downstream discovery/claiming of unassigned issues. Neither supports creating unassigned issues. Audit of all 431 historical titles and recent main commits found no duplicate behavior.
timmy self-assigned this 2026-08-14 22:50:37 +00:00
timmy closed this issue 2026-08-14 23:08:41 +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#855
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?