🚀 Automation delay action + new 3rd-party connector updates are now GA

[#1]

We’re excited to share that the new issue & alert remediation capabilities we shared earlier this month are now GA for all eligible customers. This includes:

🆕 Action - Delay:

One of our most highly-requested automation features! Temporarily pause your automation rule before proceeding to the next step for up to 15 minutes.
For Jira Service Management Cloud Premium and Cloud Enterprise plans, as well as Jira Cloud Premium and Cloud Enterprise plans

🆕 Action - Run a query in New Relic and get data back:

Connect to New Relic and run a query using New Relic Query Language (NRQL).
For Jira Service Management Cloud Premium and Cloud Enterprise plans.

🆕 Action - Launch a job template in Ansible:

Start an existing job template in your Ansible instance.
For Jira Service Management Cloud Premium and Cloud Enterprise plans.

🆕 “Wait for response” capability:

Run JEC, Azure, AWS, Ansible, and New Relic actions, and then temporarily pause them until the connector receives a response from the connector.
For Jira Service Management Cloud Enterprise plans.

🆕 Action - Change alert status:

Toggle the status of an alert between open, acknowledged, snoozed, and closed states
For Jira Service Management Cloud Premium and Cloud Enterprise plans.

We’re excited to share these new features with you, and look forward to hearing your feedback. Feel free to check out the FAQ below as you get started with them, or sign up for our AMA next month to dig in deeper with us:

AMA - Automating your work in Jira Service Management

August 27th, 2024
10:00am PDT / 1:00pm EDT
Sign up →

---

Frequently asked questions

Do the delay action and new “wait for response” functionality count toward automation time limits?
No, it isn’t counted toward the time limit. We don’t account for the time elapsed during a delay action, or when a rule is paused using the “wait for response” capability.

Each rule has a 60-minute overall execution time limit, but time elapsed during those periods does not count toward it.

Does the delay action count toward automation rule run limits?
Yes, the delay action is counted toward rule run limits.

Is the delay action available on Jira Cloud plans, too?
The delay action is also available on Jira Software Cloud Premium and Cloud Enterprise plans, regardless of whether or not you have a Jira Service Management plan. The other functionalities in this release require a Jira Software Management plan (see the top of this post for details on plan-level availability).

If I have one of the Jira Service Management plans described above, can I still use the new automation features for that plan across Automation for Jira?
Yes, you can. The new functionalities available to your Jira Service Management plan will also be usable across Automation for Jira, regardless which Jira Cloud plan you have.

Are there any pre-built rules or examples available to get started with these new functionalities?
We recommend pointing your team or customers to the in-product automation template library, which has some example rules using these new actions.

---

Don’t see your question answered? Drop it below or sign up for our upcoming AMA.

[Graeme Baker]

Can you detail when this will arrive in Data Centre please, for the delay action?

[Andrew B]

Standard Plan becomes more useless by the day.   
It's all about the $!!!!
Won't ever go premium, will just go elsewhere. 

[Masayuki Abe]

I am so excited that you released delayed execution!
Plus, it is very cool that you have made it non-countable for execution time.