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

Reply and continue from mobile Search #805

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

User problem

Mobile Search now supports scoped discovery, conversation reading, and sequential navigation, but a phone operator cannot reply without leaving the dashboard for Gitea and losing the fast triage flow. The sticky Search preview actions stop at planning/share/handoff.

Evidence

  • frontend/index.html Search preview contains conversation and navigation controls but no reply composer.
  • frontend/search-preview.js loads current conversations and advances results, but exposes no reply operation or per-result draft.
  • src/main.py only accepts comments for issues already assigned to the current operator, while Search intentionally includes accessible assigned, unassigned, closed, and pull-request results.
  • Historical title review found no Search reply/comment feature; #803 only reads conversations, #801 only advances results, while #503/#429 implement reply-and-continue in different Today/Updates flows.

Acceptance

  • An authorized operator can write and post a reply to an issue or pull request from Search preview without opening Gitea.
  • Send uses a stable idempotency key, retains the draft on failure, clears it only after server confirmation, and appends the confirmed comment exactly once.
  • Send & next advances only after confirmed delivery while preserving the Search session and per-result navigation.
  • Drafts are isolated per repository/item and survive Previous/Next navigation.
  • Direct mutation validates the requested accessible issue/pull before posting and fails closed for a mismatched or unavailable target.
  • At 390px the composer and controls remain reachable above the mobile keyboard.
  • Focused behavioral tests and the full suite pass.
## User problem Mobile Search now supports scoped discovery, conversation reading, and sequential navigation, but a phone operator cannot reply without leaving the dashboard for Gitea and losing the fast triage flow. The sticky Search preview actions stop at planning/share/handoff. ## Evidence - `frontend/index.html` Search preview contains conversation and navigation controls but no reply composer. - `frontend/search-preview.js` loads current conversations and advances results, but exposes no reply operation or per-result draft. - `src/main.py` only accepts comments for issues already assigned to the current operator, while Search intentionally includes accessible assigned, unassigned, closed, and pull-request results. - Historical title review found no Search reply/comment feature; #803 only reads conversations, #801 only advances results, while #503/#429 implement reply-and-continue in different Today/Updates flows. ## Acceptance - An authorized operator can write and post a reply to an issue or pull request from Search preview without opening Gitea. - Send uses a stable idempotency key, retains the draft on failure, clears it only after server confirmation, and appends the confirmed comment exactly once. - Send & next advances only after confirmed delivery while preserving the Search session and per-result navigation. - Drafts are isolated per repository/item and survive Previous/Next navigation. - Direct mutation validates the requested accessible issue/pull before posting and fails closed for a mismatched or unavailable target. - At 390px the composer and controls remain reachable above the mobile keyboard. - Focused behavioral tests and the full suite pass.
timmy self-assigned this 2026-08-14 06:21:13 +00:00
timmy closed this issue 2026-08-14 06:44:31 +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#805
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?