...
This is a simple background job (Jira service) , which that triggers a transition on all issues , which that are found by a certain 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.
...
| 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.
...
Select the configuration options
...
User to run the JQL query and the workflow transition
...
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. With a separate 'technical' user with special name it is transparent for the end users of Jira, what happened.
JQL query
Any valid JQL query. We recommend using a JQL query that returns issues only with a status that does have 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.
...
The origin status of the issues does not matter. 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, nothing happens with those issues. Workflow conditions and validators might prevent performing the transition.
Example
Cleanup
See In the details of the screenshot above. Users example screenshot, users did not close all resolved issues. With the above configuration, they They will be automatically closed after two weeks14 days.
Scheduled status change
Some of our customers are also using use the transition trigger to schedule automatic status changes.
...
In that transition, you might use some a Webhook to trigger an action on an external system.
...
The following error message can appear during startup in the atlassian-jira.log file!.
| 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) |
...