Sometimes resolving issues depends on fields set to a specific value. In this case, the issue is automatically resolved and transitioned to "Done" when all options of the checkbox custom field are ticked.
Field changed event
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 → Field changed event
Choose your checkbox custom field
Choose Any value
No further configuration needed. The automation rule is triggered every time an issue is being transitioned.
Add Condition → Boolean condition
Transition issue action
Add Action → Transition issue
Choose Transition to status → Done
The target status has to be reachable from the current status, otherwise, the action will not be executed.
Enable the rule by clicking on the Enable button →
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.
|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.
|Transition affected issues when releasing a version (manually)|
Manually transition all issues related to a specific version to DONE.
|Transition affected issues when releasing a version (automatically)|
Automatically transition all unresolved issues with a Fix Version that is being transitioned to DONE.
|Schedule the escalation of overdue issues|
Periodically escalate all issues where the due date has been reached.
|Schedule issues for re-submission||Transition Issue|
Periodically transition all issues to OPEN when the re-submission date reminder has been reached.
|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
|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.