Repository navigation
Make rebuild agent transition Jira issues to In Progress state - #887
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This patch makes the rebuild agent transition Jira issues to In Progress state as its first workflow step, matching the behavior of backport and rebase agents. The JIRA_ALLOW_STATUS_CHANGES env var gate is handled inside tasks.change_jira_status() and the code is literally the same as in those agents, it was just missing in rebuild agent. Not a big deal functionally but we had a complain about this from the management as it didnt show correctly on some board or something because of this so here we go.