The JQL selector can be used with all trigger types and will process all issues that were found by the specified JQL query.
JQL selector configuration
Below you will find a detailed description of each parameter needed to configure the condition.
JQL query*
Enter a JQL query that returns only specific issues. Field codes can additionally be entered.
If used with an issue event trigger, the "Select field" dropdown can be used to inject field values directly into the query.
Run as
Select the user that will be used to execute this action.
Only issues that this user is able to view (e.g via permissions, security levels) will be returned by the JQL query.
Use cases
Use case | Automated action | Use case description | Complexity |
---|---|---|---|
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. | BEGINNER | |
Bulk edit the issue resolution | Set a specific resolution on all completed issues that miss a resolution value. | BEGINNER | |
Transition affected issues when releasing a version (manually) | Manually transition all issues related to a specific version 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 |
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. | BEGINNER | |
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. | INTERMEDIATE |
If you still have questions, feel free to refer to our support team.