On this page
Use case
During new software releases you get to the point where all related issues within Jira have to be released. You could do this using a project event trigger as described in this use case. If you want to have a more fine-grained control you might want to kick-off this process manually. At this point our Manual Trigger comes in handy!
The following rule will build on the project event use case but instead use the manual trigger.
Manual trigger
Create a new rule and name it appropriately.
Providing a description will help you to identify what the rule does but this step is optional.
Add a Trigger → Manual
No further configuration needed. The rule will only be executed if a user hits the Execute button 
.
JQL selector
Add Selector → JQL Selector
JQL Query*
Use the following Expression:
fixversion = nnnnn # Replace nnnnn with the actual version that got released
Transition issue action
Next to the JQL Selector click on Add → Action → Transition issue
Mode*
Choose Transition to Status → Done
The target status has to be reachable from the current status, otherwise, the action will not be executed.
Screencast
This is how the configuration above should look on your screen
Related use cases
| Title | Automated action | Use case description | Complexity |
|---|---|---|---|
| Bulk edit the issue resolution | Set a specific resolution on all completed issues that miss a resolution value. | BEGINNER | |
| Transition issues when assigned to a developer | Transition issue | When the assignee is changed to a user in the "Developers" project role, the issue is transitioned to IN DEVELOPMENT. | BEGINNER |
| Transition affected issues when releasing a version (manually) | Manually transition all issues related to a specific version to DONE. | BEGINNER | |
| Transition affected issues when releasing a version (automatically) | Automatically transition all unresolved issues with a Fix Version that is being transitioned to DONE. | BEGINNER | |
| Schedule the escalation of overdue issues | Periodically escalate all issues where the due date has been reached. | BEGINNER | |
| Schedule issues for re-submission | Transition Issue | Periodically transition all issues to OPEN when the re-submission date reminder has been reached. | BEGINNER |
| Resolve issues when all options of a checklist are checked | When all options of a custom checkbox field are ticked, the issue is resolved and transitioned to DONE | INTERMEDIATE | |
| Keep the status of parents and sub-tasks in sync | When an issue is being rejected, all sub-tasks will be transitioned to the REJECTED status as well - automatically. | BEGINNER |
