Choose the initial owner while filing a mobile issue #843

Closed
opened 2026-08-14 17:52:32 +00:00 by timmy · 0 comments
Owner

User problem

Mobile issue capture always assigns the new issue to the signed-in operator. Delegating requires filing first, reopening the issue, loading handoff candidates, and transferring afterward. This adds friction and briefly puts work in the wrong queue.

Evidence

  • src/main.py derives the authenticated login for every create request.
  • src/gitea_proxy.py creates and confirms self-assignment.
  • Existing issue handoff candidates already provide a bounded repository-eligible owner list, but only after creation.
  • All 425 historical issue titles and recent commits were checked; none implements initial owner selection during filing. Nearest prior work is #159 (self-assign on creation) and #281 (handoff after creation).

Acceptance criteria

  • Owner defaults to Me without an additional upstream request.
  • A user can lazily choose an eligible teammate after selecting a repository.
  • The chosen owner survives draft review and offline delivery.
  • Final filing review names the selected owner.
  • Teammate-owned issues cannot use Create & start.
  • The server validates the selected owner and confirms that exact assignment; invalid/stale owners create no issue.
  • Repository changes discard stale owner candidates/selections.
  • Focused behavioral tests and the full suite pass.
## User problem Mobile issue capture always assigns the new issue to the signed-in operator. Delegating requires filing first, reopening the issue, loading handoff candidates, and transferring afterward. This adds friction and briefly puts work in the wrong queue. ## Evidence - `src/main.py` derives the authenticated login for every create request. - `src/gitea_proxy.py` creates and confirms self-assignment. - Existing issue handoff candidates already provide a bounded repository-eligible owner list, but only after creation. - All 425 historical issue titles and recent commits were checked; none implements initial owner selection during filing. Nearest prior work is #159 (self-assign on creation) and #281 (handoff after creation). ## Acceptance criteria - Owner defaults to Me without an additional upstream request. - A user can lazily choose an eligible teammate after selecting a repository. - The chosen owner survives draft review and offline delivery. - Final filing review names the selected owner. - Teammate-owned issues cannot use Create & start. - The server validates the selected owner and confirms that exact assignment; invalid/stale owners create no issue. - Repository changes discard stale owner candidates/selections. - Focused behavioral tests and the full suite pass.
timmy self-assigned this 2026-08-14 17:52:32 +00:00
timmy closed this issue 2026-08-14 18:32:29 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
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#843
No description provided.