On this page
Use case
When doing a lot of manual work, some steps can be forgotten from time to time, even if they are tightly related to each other, e.g. transitioning an issue to "In Development" when the assignee is changed to a user in the "Developers" project role. In this example we will configure a rule that will automatically transition those issues.
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 Assignee
Changed to*
Choose Any Value
No further configuration needed. The automation rule is triggered every time an issue is being transitioned.
User condition
Add Condition → User condition
User to evaluate*
Choose User in field → Assignee
Check against*
Choose User in Project role(s) → Developers
Transition issue action
Next to the User Condition click on Add → Action → Transition issue
Mode*
Choose Transition to status → In Development
The target status has to be reachable from the current status, otherwise, the action will not be executed.
Run as
Choose User in field → Assignee
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.