| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, |
...
see our JSU Cloud documentation. |
| Info |
|---|
The 'Transition Trigger Service' is available from JSU 2.0 |
Description
This is a simple background job (JIRA Jira service), which triggers a transition on all issues, which are found by a certain JQL query.
The 25680470 post function provides Linked Transition and Follow Up Transition post functions provide also some functionality to trigger a transition on some issues. Depending on your use case you might use this service or that those post functionfunctions.
Configuration
Add the service
See Atlassian's documentation for more information on how to confiugre JIRA configure Jira services.
...
You must enter the following value as class.
| Code Block |
|---|
ch.beecom.jira.jsu.jiraservice.TransitionTriggerService |
Define all
...
parameters
In the following screen, you can configure the details of the transition trigger service.
...
User to run the JQL query and the workflow transition
Be aware that depending on the user who runs the JQL query, the result might be different. Not all users have the same permissions, so might not see all JIRA projects.
In real production, it is a good idea to create a separate 'technical' user (not used by any real human), with a special name (for exmample example 'automatic transition'). This will appear in the history of any changed issue. With a separate 'technical' user with special name it is transparent for the end users of JIRAJira, what happened.
JQL query
Any valid JQL query.
We recommend to use using a JQL query which that returns issues only with a status, which actually does have a transition to the target status.
Otherwise, it will not be possible to trigger a transition, and as a cause of thattherefore, they remain in the result of the JQL query. Those remaining issues would then would be unnecessary unnecessarily processed again and again.
...
Workflow conditions and validators might prevent to perform performing the transition.
Example
Cleanup
See the details of the above screen shot. Often people forget (or are too lazy) to screenshot. Users did not close all resolved issues. With the above configuration, they will be automatically closed after 2 two weeks.
Scheduled status change
Some of our customers are also using the transition trigger to schedule some automatic status changechanges.
Consider a workflow with a status Ready and a status Executed. And a custom field 'Execution Date/Time'. We then use the following parameters:
| Code Block |
|---|
JQL query: status = Ready AND 'Execution Date/Time' <= now() |
To trigger on those issues the transition to the
| Code Block |
|---|
Target status: Executed |
In that transition, you might for example use some Webhook to trigger an action on an external system.
...
| Code Block |
|---|
[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 self is not affected after Jira successfully started.