[COMPLETED] AMA: Automating your work in Jira Service Management - LIVE on Aug 27

[#1]

UPDATE: It’s a wrap for our AMA on automation in Jira Service Management! Thank you again for joining us to hear about the latest in automation, and for sharing your questions and feedback. If you have any questions we didn’t address in the AMA, in this post, or in the comments below, we encourage you to leave them on this post. Otherwise, stay tuned for more updates coming your way!

Look forward to hearing your questions and feedback as we continue to share new updates for automation.

Resources mentioned on the AMA:

• Automation playground

• New features recap

→ Watch recording

---

Hey Community!

We’re hosting a live AMA later this month for you to ask questions about all things automation in Jira Service Management. We’ll answer your questions live at 10am PST / 1pm EST on August 27th, 2024.

→ Register here

Last month, we released a handful of new functionalities to help accelerate alert and issue resolution: like the delay action and new 3rd-party connectors. We’ll cover a brief overview of those new functionalities, followed by a live Q&A with our product experts.

Feel free to ask us about things like:

• Tips for bringing new automation functionalities into your work

• Best practices for setting up common automation use cases

• Tips for optimizing your rules & minimizing duplicative tasks across them

…And any other questions you have about effectively automating your work in Jira Service Management! Feel free to drop your questions below ahead of the AMA - we’ll answer them here, and cover them again live during the AMA on August 27th.

[Dirk Ronsmans]

Always interesting to see happens with Automation.

One use-case that I've always had trouble with was a decision driven/sequential (sub) task "flow".

Meaning that based on an initial request we would need to have subtasks created both initially (after approval for example or another state change) and then new subtasks get created when the previous one is closed.

That in itself is nothing special but a more decision/parameter driven flow is always a bit of a pain to model.

A side problem here is that there is no visibility in what will come next (so users can prepare) or on the actual flow that will will guide the process.

[Ashlea Shaw]

Hi everyone, great to be here and to learn more about the JSM!