Preserve selections when batch closing issues fails

User intention

Close two release tasks together.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both
BeforeThe defect at the parent commit
0:00.00 / 0:00.00Frame 0 · Inspect the selected release issues in the issues list.

Attempt to close the two selected release issues and inspect the resulting list and selection state.

AfterThe same script once the merged fix is applied
0:00.00 / 0:00.00Frame 0 · Inspect the selected release issues in the issues list.

Attempt the batch close and inspect the dependency message and retained issue selections.

How is it judged?

01 · Given
Restore the data and starting state.
The repository owner is on its issues list with Publish release and Prepare release notes selected. Both are open and depend on the open, unselected Complete release review issue.

02 · When
Perform the interaction.
Click Close in the batch toolbar and observe the result.

03 · Judge
Rationale: The selection defines the user's intended batch. Retaining it after a dependency blocks closure lets the user resolve the blocker and retry without reconstructing the work scope.
Require
On rejected batch close, show clear failure feedback associated with the action and keep the rejected issues open and selected. Explain the open dependency when that rejection reason is available.
Allowed
  • A readable toast, banner, or inline message is acceptable; exact wording and positioning may vary.
  • The list may update in place or re-render if selections and batch context are retained and the failed operation is not presented as success.
  • Valid server-side dependency protection must continue to reject the close; neither bypassing it nor reporting a false success is acceptable.

Who repaired it

More from Gitea

Self-hosted Git forge with issues, CI and packages

Synchronize a canceled workflow in the run list after the reference repair
Developer tools
Synchronize a canceled workflow in the run list
The retained list continues to display Waiting throughout the observation. A separate diagnostic manual reload then displays Canceled for the same run, confirming that the list was stale after cancellation. The final screenshot is after that diagnostic reload; the preceding video shows the defect. This evidence concerns cancellation, not successful runner execution.
#38329
Explain Actions secret naming rules after the reference repair
Developer tools
Explain Actions secret naming rules
Native HTML5 validation blocks submission, focuses Name, and says Please match the requested format. The dialog retains the entered values but does not explain that the initial digit is invalid or how to correct it.
#39221
Use local tabs in the branch selector after the reference repair
Developer tools
Use local tabs in the branch selector
The tab adopts link-like hover styling. Clicking keeps the same Code page, dropdown, active Branches tab, and main branch content; the retained Reproduction issue context additionally reports an added trailing # and focus on Filter branch. The unchanged active-tab content is normal; the misleading link semantics and empty-fragment navigation side effect are the defect. Browser chrome is not present in the replay video, so the URL observation relies on the retained Reproduction context, not visual confirmation in the video.
#39285