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

Apply mobile Search release plans atomically #817

New Issue
Closed
opened 2026-08-14 09:52:58 +00:00 by timmy · 0 comments
timmy commented 2026-08-14 09:52:58 +00:00
Owner
Copy Link

Problem

Mobile Search release planning currently applies milestone and optional due date with separate requests. A second-request failure leaves a partially planned issue, and each selected issue repeats authorization reads and mutations.

Scope

Add one authenticated release-plan operation that validates an operator-owned open issue and an open milestone, then applies milestone plus optional due date in one confirmed upstream mutation. Update the mobile Search batch flow to use it and preserve retry journal behavior.

Acceptance criteria

  • One upstream issue PATCH applies milestone and optional due date together.
  • Missing deadline preserves the existing due date.
  • Closed/PR/not-operator-owned issues and unknown/closed milestones cause no mutation.
  • A failed or unconfirmed mutation remains retryable and is never reported complete.
  • Mobile Search sends one release-plan request per selected issue, not separate milestone and due-date requests.
  • Focused and full test suites pass.
## Problem Mobile Search release planning currently applies milestone and optional due date with separate requests. A second-request failure leaves a partially planned issue, and each selected issue repeats authorization reads and mutations. ## Scope Add one authenticated release-plan operation that validates an operator-owned open issue and an open milestone, then applies milestone plus optional due date in one confirmed upstream mutation. Update the mobile Search batch flow to use it and preserve retry journal behavior. ## Acceptance criteria - One upstream issue PATCH applies milestone and optional due date together. - Missing deadline preserves the existing due date. - Closed/PR/not-operator-owned issues and unknown/closed milestones cause no mutation. - A failed or unconfirmed mutation remains retryable and is never reported complete. - Mobile Search sends one release-plan request per selected issue, not separate milestone and due-date requests. - Focused and full test suites pass.
timmy self-assigned this 2026-08-14 09:52:58 +00:00
timmy closed this issue 2026-08-14 10:00:04 +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#817
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?