Execute a specific transition or transition to a specific status. The action will be performed on the issue currently being processed.
Transition issue configuration
Below you will find a detailed description of each parameter needed to configure the action.
Mode*
Select the way the issue should be transitioned. It can be chosen from one of the following options:
- Transition to status - the first available transition to the target status will be executed.
- Execute transition - select any transition from active workflows.
Additional options
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.