Description
This is a simple background job (JIRA service), which triggers a transition on all issues, which are found by a certain JQL query.
Configuration
Add the service
See Atlassian's documentation for more information how to confiugre JIRA services.
You must enter the following value as class.
| Code Block |
|---|
ch.beecom.jira.jsu.jiraservice.TransitionTriggerService |
Define all paremeters
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 '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.
Target status in the workflow
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 to perform the transition.
Example
See the details of the above screen shot. Often people forget (or are too lazy) to close all resolved issues. With the above configuration they will be automatically closed after 2 weeks.