Cloud Migration Resources
Planning a Jira Cloud migration? These resources can help you get started:
→ JSU Cloud features – Review Cloud features and understand key differences between DC and Cloud.
→ Migration support from Appfire – Learn how we can help you migrate smoothly.
Transition Trigger Service
This is the documentation of JSU for Jira Data Center. If you are using JSU for Jira Cloud, see our JSU Cloud documentation.
Description
This is a simple background job (Jira service) that triggers a transition on all issues found by a specified JQL query.
The Linked Transition and Follow Up Transition post functions also provide some functionality to trigger a transition on some issues. Depending on your use case, you might use this service or those post functions.
Configuration
Add the service
See Atlassian's documentation for more information on how to configure Jira services.
You must enter the following value as class:
ch.beecom.jira.jsu.jiraservice.TransitionTriggerServiceSelect the configuration options
User to run the JQL query and the workflow transition
Depending on the user who runs the JQL query, the results may differ. Not all users have the same permissions, so they might not see all Jira projects.
In production, it is a good idea to create a separate 'technical' user (not used by a real person), with a special name (for example, 'automatic transition'). This will appear in the history of any changed issue.
JQL query
We recommend using a JQL query that returns issues only with a status that has a transition to the target status. Otherwise, it will not be possible to trigger a transition, and therefore, they remain in the result of the JQL query. Those remaining issues would then be unnecessarily processed again and again.
Target status in the workflow
The origin status of the issues is irrelevant. As long as there is a valid workflow transition to the specified target status, this will be triggered. If there is no valid workflow transition, no action is taken on those issues. Workflow conditions and validators can prevent the transition from being performed.
Example
Cleanup
In the example screenshot, users did not close all resolved issues. They will be automatically closed after 14 days.
Scheduled status change
Some of our customers use the transition trigger to schedule automatic status changes.
Consider a workflow with statuses 'Ready' and 'Executed', along with a custom field called 'Execution Date/Time'. We then use the following parameters:
JQL query: status = Ready AND 'Execution Date/Time' <= now() To trigger those issues the transition to the Executed status.
Target status: ExecutedDuring this transition, you can use a Webhook to trigger an action on an external system.
Known issues
This method is not supported in an UnloadableJiraServiceContainer
The following error message can appear during startup in the atlassian-jira.log file.
[INFO] [talledLocalContainer] 2020-10-20 18:25:00,010 Caesium-1-4 ERROR anonymous dadada [c.a.jira.service.ServiceRunner] An error occurred while trying to run service with ID '16900'. This method is not supported in an UnloadableJiraServiceContainer
[INFO] [talledLocalContainer] java.lang.UnsupportedOperationException: This method is not supported in an UnloadableJiraServiceContainer
[INFO] [talledLocalContainer] at com.atlassian.jira.service.UnloadableJiraServiceContainer.setLastRun(UnloadableJiraServiceContainer.java:86)This only affects Jira Version 7.3.x during Startup. The Transition Trigger Service itself is not affected after Jira successfully starts.
Need support? Create a request with our support team.