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

How can I make an automation rule more performant?

Danny_qtq7b3

Hello Community,

I thought I would throw this out to the Atlassian Community hive mind to help me improve.

The problem

I have a JSM Cloud project that relies on an approval to be handled by a single user depending on the department that "owns" the request, e.g. HR, Legal, Ops.

Departments are listed in a cascade field, which has multiple child values underneath every department.

On creation of the request, the creator selects which department they are putting the request against.

Each Department has an owner. An active request needs to have an approval from the appropriate department owner that the creator selected.

Steps Taken

I have set up an automation rule that looks for the department value of a new request and assigns the appropriate department owner to approve.

Currently, I have an IF/ELSE conditional statement for each department option that the rule loops through. Unfortunately, the rule takes up to 10 seconds to process a run.

My Question

Can I make this more performant?

Thanks all for reading my question.

Accepted answers

All comments

Stefan Salzl_0i980g

HI @Danny ,

How is the department field (especiall the owner) configured? Could you give a screenhot for more insights to that?

I´m pretty sure that processing through your departments with if/else might take a lot of time :-/ Something that came to my mind in this case (without knowing further details, the field configuration, etc.... so it´s more a guess) are smart values and (maybe) variables. Did you think about that way or might that be something that sounds feasable?

Best
Stefan

Danny_qtq7b3

Hello @Stefan Salzl

Each Department is a parent value in the cascade field.

The owner is applied from the automation rule.

Automation

Trigger

When field value changes: Department & Cost Code field

IF/ELSE Block JQL Condition

status = "budget holder" AND project = PROJ AND "Department & Cost Codes[Select List (cascading)]" in cascadeOption(10020)

Action

Edit field value Approvers

How would smart values or variables be applied in this context?

Thanks,

Danny

Stefan Salzl_0i980g

Isn´t the cascding list automatically asking for providing/choosing the child value? As soon as I choose the parent value the child list opens. I´m just thinking of the automation purpose as the field/entry anyways has to be clicked away manually after I choose the department.

does each parent only consist of the owner in the child-option? or are there more than 1 options in the child field?
how is the owner then identified?

Would definitly help to see your setting to gain a better picture of how the rule should act.

Best

Stefan

Danny_qtq7b3

Hi @Stefan Salzl

The child is used for cost center codes within the department though the budget holder remains the same.

The automation condition is listening for the parent value to be set. The child values are needed for the support team though not required for the automation rule.

There are more than one cost code per department. Though the budget holder only needs set at the department level.

The budget holder is pre-defined in the automation rule.

Do you want a screenshot of the rule summary page? Does the text above not demonstrate the trigger, condition, and action components of the rule?

Thanks,
Danny

Welcome!

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

Quick Links

Find more posts tagged with

cloud

automation

approver

cascading-select

jira-service-management