Skip to content

fix(jira): open the move form when start work's status has a screen - #29

Merged
cornedor merged 1 commit into
mainfrom
start-work-move-form
Nov 19, 2026
Merged

cornedor merged 1 commit into
mainfrom
start-work-move-form

Conversation

@cornedor

Copy link
Copy Markdown
Owner

Start work refused a start status whose transition has a screen and told you to move the issue with s. It now takes that move the way a move picked by hand goes: made at once when the required fields are filled, through the move form otherwise.

In the terminal, start work hands the move to the existing prepareJiraMove path after assigning. In the browser, /work returns the move as Move and the page runs it through takeMove once the start dialog closes; nothing new is built for the form itself.

The two "asks for fields" messages and their Dutch translations are gone, and the start_status line in docs/reference/config.md says what happens now.

Checked: go test ./internal/ui ./internal/web ./internal/i18n/... passes on this branch, with a new server test for the screened move. Not verified: the form opening after a start in the running terminal or browser.

Start work refused a start status whose transition has a screen and told
you to move the issue by hand. It now takes that move as one picked by
hand: made at once when its required fields are filled, through the move
form otherwise.
@cornedor
cornedor merged commit a598bc2 into main Nov 19, 2026
9 checks passed
@cornedor
cornedor deleted the start-work-move-form branch November 19, 2026 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant