feat(jiraonprem): transition issues between statuses - #6756
Open
purisev wants to merge 3 commits into
Open
Conversation
The cloud provider takes a transition_to name on notify and moves the ticket after the update or the create; on-prem had no way to change a status at all, so a workflow that closes a ticket when its alert resolves could not be written against Jira DC. Port the same two helpers and the same parameter, with the on-prem request shape: bearer header, the configured verify, a timeout. The name is matched case-insensitively and an unknown one fails with the transitions the ticket actually offers, so the result payload and the error text stay identical between the two providers. Signed-off-by: Iurii Purisev <92510590+purisev@users.noreply.github.com>
Add the resolved-alert example next to the cloud one it mirrors, and a short section on the on-prem page: the parameter, the permission the PAT needs, and a pointer to the cloud page for the longer walkthrough. Signed-off-by: Iurii Purisev <92510590+purisev@users.noreply.github.com>
This was referenced Sep 3, 2026
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
1 participant
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.
Problem
See #6754.
transition_toworks on Jira Cloud and does not exist on the on-premprovider, so a workflow that moves a ticket when its alert changes state cannot
be ported by changing
type.Fix
Two commits. The provider gets
__get_available_transitionsand__transition_issue, following the Cloud implementations, and_notifygetstransition_to, applied after an update and after a create. A name is matchedcase-insensitively against what Jira offers for that ticket; an unknown one
raises with the names that exist:
The token needs the
TRANSITION_ISSUESpermission on the project. A workflowthat passes no
transition_tosends no transitions request.Tests
tests/test_jira_provider.pygrows to 14 tests, all passing: a transitionapplied after the id lookup, a name matched in the wrong case, an unknown name
and the message it produces, a created issue transitioned in the same step, and a
notification without
transition_tomaking no transitions call.Docs
The on-prem page gets an "Auto-Transition Workflows" section and points at the
Cloud page for the longer walkthrough, plus the example workflow
examples/workflows/jira_on_prem_transition_on_resolved.yml. The on-prem_notifydocstring gained anArgsblock, so the regenerated snippet nowcarries a comment per parameter instead of empty ones.
Note on the other Jira PRs
#6755 fixes the priority reset in the same
_notify, and the two edit the samesignature line, so whichever lands second needs a one line resolution. #6752 and
#6753 cover the remaining two reports and touch this provider elsewhere.
Fixes #6754