On this page
Use case
One major advantage of Jira is the creation and implementation of customized workflows. But as fast as new workflows are created, mistakes happen. A common misconfiguration is forgetting to set a resolution on the final workflow transition.
By default, in Jira you cannot bulk edit resolutions. With this rule you can!
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:
project = TIS and statusCategory = Done and resolution is empty # Customize the JQL to your needs
Update field action
Next to the JQL Selector, click on Add → Action → Update field
Field*
Choose Resolution
Update to*
Choose Selected Value
Value*
Choose one of the given resolutions (e.g. Done)
You can also use this rule to delete resolutions from issues that are obviously not done!
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 |
