Files
orca/tests/tools
fd8198f001 feat(jira): reorder the Tasks board lanes by dragging their headers (#30597)
* feat(jira): reorder the Tasks board lanes by dragging their headers

Jira's board configuration decided the lane order and there was no way to change it in Orca. Column headers are now drag handles, with ArrowLeft/ArrowRight as the keyboard equivalent, and the resulting order is saved per board on the device. Jira's Agile API exposes board column order read-only, so this is an Orca view preference and never edits the Jira board.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix(jira): make the saved lane order survive Jira column inserts and filtered lanes

Review follow-up. Board column keys were derived from the column index, so inserting a column in Jira orphaned every saved lane position; they now come from the column's status ids, which Jira keeps stable across config edits. Saving a reorder also replaced the stored order with only the lanes currently on screen, dropping the saved position of any lane a filter had hidden; the new order is merged into the saved one instead. A keyboard move now restores focus to the lane it moved, and the rendered probe asserts two arrow presses in a row land.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix(jira): tell screen readers a lane's issue count and its arrow-key move

Review follow-up. The lane header's aria-label replaced the visible header text, so assistive technology no longer heard how many issues the lane held, and nothing said the header moves with the Left and Right arrow keys. Both now ride on aria-description, translated in every catalog including the newly added Portuguese one, which also gains the existing reorder label.

Also registers the lane-order storage module in the WSL-move localStorage inventory, as the sibling view-mode change did, and follows the jira-types move on main.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(jira): keep the saved lane order across a runtime reconnect

Review follow-up. The lane order was stored under the status-order cache key, which ends in the provider runtime session generation. That counter restarts at zero on every launch and moves on every runtime focus change and remote session start, so a reconnect or a relaunch read the order back under a different key and silently fell back to Jira's order.

The storage key is now built from the task source, the owner's identity without the generation, and the Jira project. The generation-free identity is split out of getEnvironmentRuntimeContextKey rather than duplicated, and the status-order cache keeps its generation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Neil <neil@stably.ai>
2026-11-16 02:12:19 -08:00
..