image
See how Jira and Innovalog's workflow automation can help
1 minute reading time (169 words)
Featured 

Scheduled Actions: automating post-functions outside of workflows [new in Jira Cloud]

scheduled-actions-for-jira-cloud

Schedule actions for one or more JMWE post-functions to run against issues returned by a JQL search.  


Regular workflow post-functions run on transitions, but now you can schedule JMWE post-functions to run against issues returned by a JQL search. For example, you can automatically transition any issue escalated yet not addressed for over 24 hours.

Things to know:

  • ​Works based on predefined times, not based on workflow transitions.
  • Flexible scheduling allows for any frequency (10-minute minimum).
  • Can execute many types of automations, such as workflow transitions, issue status and user changes, all in sequence.

How it works:

​In the Scheduled Actions library, set the schedule according to your requirements:


Then, select your parameters for issues you'd like to target with this automation.


Finally, create post-functions, for example, one to send a custom email, and another one to add a comment.


Here is how the Scheduled Action Editor looks:


Sequence of Post-functions: ensuring a predictable...
Shared Actions: reusing post-function configuratio...

Related Posts

 

Comments 3

Guest - EmmyS on Wednesday, 08 April 2020 20:52

Is there a limit to the number of times a scheduled action can run? We were very interested in the native automation rules that Atlassian recently added (after acquiring CodeBarrel), but found that the execution limits were too low for us. If I were to set up a scheduled action to run every 10 minutes to transition linked issues, would that be allowed?

Is there a limit to the number of times a scheduled action can run? We were very interested in the native automation rules that Atlassian recently added (after acquiring CodeBarrel), but found that the execution limits were too low for us. If I were to set up a scheduled action to run every 10 minutes to transition linked issues, would that be allowed?
Guest - David Fischer on Friday, 16 October 2020 20:33

Hi Emmy,
sorry, I didn't see your comment before. There are some limits to Scheduled Actions, but not nearly as drastic as those of Jira Automation. If you run a scheduled action every 10 minutes, you will be restricted to 150 issues (approximately) per execution. You also need to make sure you don't continuously run the action on the same issues (basically repeating the same action on the same issues every 10 minutes, which would make no sense) or it will have a major impact on your Jira instance performance and we might be forced to disable that scheduled action.
David

Hi Emmy, sorry, I didn't see your comment before. There are some limits to Scheduled Actions, but not nearly as drastic as those of Jira Automation. If you run a scheduled action every 10 minutes, you will be restricted to 150 issues (approximately) per execution. You also need to make sure you don't continuously run the action on the same issues (basically repeating the same action on the same issues every 10 minutes, which would make no sense) or it will have a major impact on your Jira instance performance and we might be forced to disable that scheduled action. David
Guest - VB on Tuesday, 27 October 2020 17:24

can scheduled actions be configured for slack webhook? I am trying to avoid routing email to slack notification)

can scheduled actions be configured for slack webhook? I am trying to avoid routing email to slack notification)
Guest
Sunday, 17 January 2021

Captcha Image