Hello, Please advise on Jira automation, is it possible to change automation, that firstly it would check summary and then transition? Because right now it checks every single ticket and affects our automation limits. Or please advise if it can be done other way.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira automation

Anastasia Krutitsenko

Hello,

Please advise on Jira automation, is it possible to change automation, that firstly it would check summary and then transition?

Screenshot 2022-05-23 at 17.36.53.png

Because right now it checks every single ticket and affects our automation limits. Or please advise if it can be done other way.

Accepted answers

All comments

Marco Brundel

Hi @Anastasia Krutitsenko ,

To move issues from Resolved to Done I have set up a scheduled automation rule (trigger = scheduled). I then have this rule performed once a day.

Maybe this is an option for you.

Regards, Marco

DasJo

Are you using any add-ons that extend the post functions? Then you could change a custom field if the condition is true. In the automation you can then choose "Field value has been changed" as trigger.

John Funk

Hi Anastasia,

The automation rule will only fire on a triggering event. So unless you are changing the Summary field value, that can't be your trigger.

But if your rule is only on a single project, you have unlimited executions, so that should not affect your limits.

Anastasia Krutitsenko

Hi,

No, the rule is for several projects, therefore the limit is being full quite fastly.

Anastasia Krutitsenko

But there will not be any changes in the summary. Would it be possible setup firstly to check summary, then transition?

DasJo

For that reason I asked about the extensions in the post function. I know that there are some post functions that set a field value when a condition is true.
It can be a field that is not displayed. Then the trigger (in automation) can react to that.

John Funk

Then your best option is to create a scheduled rule and run that once a day (or even a couple of times a day) as Marco suggests.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud