On this page
Use case
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
Field*
Choose your checkbox custom field
Changed to*
Choose Any value
No further configuration needed. The automation rule is triggered every time an issue is being transitioned.
Boolean condition
Add Condition → Boolean condition
Use the following Parser Expression*:
numberOfSelectedItems(%{trigger.issue.c11500}) = numberOfAvailableItems(%{trigger.issue.cf11500})
#Replace field code with the field code of your custom field. Use the field dropdown to automatically insert the field code
Transition issue action
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.
Enable the rule by clicking on the Enable button 
→ 
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 |
If you still have questions, feel free to refer to our support team.
