Many users have similar requirements when it comes to tasks they want to automate. This page contains a few of them.
Make sure to come by once in a while since the number of use cases will grow over time.
|Use case||Automated action||Use case description||Complexity|
|Sum up value in parent issue on field change in sub-tasks|
Calculate field values from all sub-tasks and writes the sum into a corresponding field in the parent issue.
|Remind users to close inactive issues||Periodically add a comment mentioning the assignee to all unresolved issue that haven't been updated for more than 30 days.|
|Notify the project lead on priority changes|
When the priority is changed to "Blocker", a comment will be added with a user mention alerting the project lead.
|Notify assignees when components are merged||Add a comment to an issue as soon as one of the selected component has been merged.|
|Re-assign issues and leave a comment|
Assign all issues from a user on vacation to another user and add a comment to inform the team.
|Update assignee and reporter to facilitate user deletion|
To facilitate deleting a user account, all issues will be reassigned and the reporter changed to avoid potential problems when deleting the user.
|Assign an issue to the last assignee on a transition|
When an issue is transitioned to the DRAFT status, the issue will be automatically re-assigned to the last assignee from the project role "Developers".
|Add sub-tasks to an issue on creation||Automatically create 3 sub-tasks - Documentation, Marketplace and Newsletter.|
|Create sub-tasks depending on selected values in a custom field||When an issue is created, sub-tasks for each option selected in a checkbox custom field will be created.|
|Track issues mentioned in comments|
Automatically link issues based on comments.
|Bulk edit the issue resolution|
Set a specific resolution on all completed issues that miss a resolution value.
|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.
|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.
|Schedule the escalation of overdue issues|
Periodically escalate all issues where the due date 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 priority of parents and sub-tasks in sync||When the priority of a parent issue is updated, all sub-tasks will be updated accordingly.|
|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.
|Schedule issues for re-submission||Transition Issue|
Periodically transition all issues to OPEN when the re-submission date reminder has been reached.