📣 Introducing new automation templates for Jira Product Discovery!

[#1]

Hi Community!

We’re excited to announce that we’ve recently launched nine new automation templates to handle the most common, repetitive tasks in Jira Product Discovery and help you save time. Our new templates include:

Project automation templates:

• When idea is “Done” → then archive it

• When idea transitions to “Discovery” → Add watchers

• When idea transitions to “Delivery” → Create a delivery ticket

• When idea transitions to “Delivery” → update Slack channel

• When idea is created → Create a corresponding Confluence page

• When idea has been idle for 3 months → notify assignee

• When idea has been idle for 4 months → move it back to “Parking lot”

Global automation templates:

• When delivery ticket is created → Copy description from idea

• When delivery ticket is "Done" → Mark idea as “Done”

To start using our new project automation templates, you must be a project admin in Jira Product Discovery. Go to your Project settings → Automation → select the Templates tab. From here, select any automation template you wish to use.

To access global automation templates, just click Global administration (in red on the screenshot above). From here you can view and select automation templates that will be applied across projects. Note you must be a Jira admin to enable global automation templates.

As always, if your team has other tasks they wish to automate, you can always create your own automation rules with our no-code rule builder.

For any feedback or questions, leave a comment on this post or submit in-product! 

Cheers,
Hermance, PM @ JPD

[Sam Hepworth]

@Hermance NDounga Automation is awesome. We have already created a lot of automation to improve our workflows in JPD. So sad that the new limits on automation execution force us to limit how much we use automation.

[Omer Meshar]

I second what @Sam Hepworth has said, and I would even suggest not to use the templates as mentioned above, since they will be too costly this way (we have only 500 successful runs a month!!?!?!).

For example, having two rules on the same trigger (idea transitions to Delivery) is sadly wrong now, and should be a single rule with complex logic and multiple actions. So sad...

[Yael Geffen]

Hi, I'm trying to find a way to set up the following rule:

When a delivery ticket is created → Copy value score from idea

I have a custom field both on the product Jira discovery board and on the different projects on Jira software. On the Jira product discovery board, the value score is a result of a formula.

[Matteo Pacenti]

Hello, 

if the idea is transitioned to done from another Jira project's automation, will the "When idea is Done → then archive it" be triggered? 

I'm asking because the Idea is correctly moved to DONE by the Jira automation but the idea is not archived and there are no logs in the Discovery automation at all.

[Omer Meshar]

@Matteo Pacenti you can configure on each rule if you want it to be triggered by another rule. If you decide to check this flag, then yes, the idea will move to Done and then to Archived.

@Yael Geffen You currently can't use formula fields in automation:

Project Automation is only partially supported

You can use Project Automation in Jira Product Discovery projects, with the following limitations: 

• Some fields aren't supported in automation rules, in particular: 
  • Formula fields
  • Vote fields
  • Insights field
  • Delivery progress/status fields
  • People fields
• Project Automation doesn’t support triggers or actions for an idea’s Insights

from: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Known-limitations-of-Jira-Product-Discovery/ba-p/2069648

[Adam Gustafsson]

We usually have more than one delivery ticket (in several Jira projects). Is it possible to setup an automation that closes the idea when the last delivery ticket is moved to done?

[Thorsten Kamann]

Hi,

the new automation templates are very useful. Especially the one to create a confluence page. But I see that only content templates (templates available in the chosen space) are supported not the global templates or blueprints. So the most templates are not usable.

Could you change this to make this action more usable?

Thanks

Thorsten

[Hermance NDounga]

@Adam Gustafsson hey Adam, yes it's possible - it's a slight change in the rule describe here : https://support.atlassian.com/jira-product-discovery/docs/automate-actions-in-the-delivery-panel/ (makes it a bit more complex :) ) 

[Hermance NDounga]

@Sam Hepworth & @Omer Meshar The new limits on automation are by definition, new, both for Atlassian, but especially for Jira Product Discovery, as we did not count under any previous limitations. We based this limit on the current automation usage for Jira Product Discovery projects, with only 0.1% of sites breaching this limit. 

The current threshold of 500 is subject to change if we notice many more users go over it, and most importantly, as long as we don't have a Premium edition and that our users are not able to upgrade to a higher plan, we will review case by case breaching limits and move forwards with exceptions when necessary ;) 

Also note that for the two global templates, the rule execution is counted under Jira Software (or Jira Work Management if that's where you delivery is happening). 

[Sam Hepworth]

@Hermance NDounga With the new calculation method we used 420 CPD executions in September and we used 383 in October. That is very close to the limit, and our usage will increase since we are scaling up.

[Adrián Plaza]

Hi Hermance,

There is any plan to support the manual tigger in JPD?

Thanks for your help

[Sam Hepworth]

@Hermance NDounga I can see that @Adrián Plaza asked if Manual Trigger for automation is something you have on the roadmap for JPD?