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; } } }

Filter issue type on automation trigger

Emiliano Visioli_eb2tr1

Hi all,

I have a project which involve several issue type.

I configured an automation based on a status transition trigger but as there are several issue type, the rule starts a lot of times because the status is used in all of them.

Is it possibile to pre-filter a trigger? I set a condition on issue type to apply the actions only on a specific issue type (and it works) but as I said in the log I can see that this rule is launched many times (with "no actions performed).

My goal is to engage the trigger only for a specific issue type from the very beginning.

Here the first part of the rule with the conditions:

Screenshot 2024-04-09 153731.png

In addition, I've noticed that it took almost 25 seconds to complete the automation, that is a huge amount of time. Could be possible to reduce it?

Accepted answers

Yong Yang

Hi @Emiliano Visioli

Welcome to our community.

Could you please try Issue Type equals condition directly?

Thanks,

YY哥

All comments

Yong Yang

Hi @Emiliano Visioli

Welcome to our community.

Could you please try Issue Type equals condition directly?

Thanks,

YY哥

Emiliano Visioli_eb2tr1

Hi YY哥,

thank you, with this change, the speed has definitly increased.

But I guess is not possible to "pre-filter" a trigger as the conditions are applied after the trigger is engaged.

Thank you,
Emiliano

Yong Yang

Hi @Emiliano Visioli

The automation rule builder block is triger -> condition -> action. So we can't limit a condition before a trigger.

Thanks,

YY哥

Kalyan Sattaluri_iinm1n

The major criteria for your rule's time to execute is:

Your subsequent steps in the rule (your first steps are not whats bogging the rule down), and
the load on your infrastructure at the time of your rule trigger (if its peak hour and a lot of people are accessing / working in jira when your rule is run, it will be slower and nothing to do with your rule specifically) and
the hardware on your premises

Some of these things you cannot control such as load / hardware and I would not bother, if its a concern, try executing the rule in off / peak hours and check the time.. If its better, also see if you can change the trigger to scheduled so that you control when rule is run. Again, depends on use case but big picture, I wouldnt worry too much about execution time unless it 5 mins or so.

Welcome!

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

Quick Links

Find more posts tagged with

data-center

jira-service-management

jira-service-management-data-center