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

Automation rules looping assignment.

wisanu wirojtecha

Hi everyone,

I'd like to check with you. As now I'm set the automation rule for assign the ticket to the assignee with workload balance. As a check on the work log, I found one case has a loop assigned the case to my agents as attached picture.

Screenshot 2021-09-27 124426.png

Do you have any idea why JIRA loop the assignment?

Refer to screenshot above. Is no one touch or manual assign the ticket. All is from automation rule.

Accepted answers

Callum Carlile _Automation Consultants_

Hi @wisanu wirojtecha

Usually this is caused when the trigger of the rule is the same event as one of your actions.

E.g. if your rule is triggered when an issue is assigned to someone, and one of your actions is to assign the issue to someone. This action would then trigger the rule again, which would assign it again, which would trigger the rule again..... etc etc.

If this is the case with your rule, I would consider changing the trigger, e.g. to a status change or custom field update

All comments

Callum Carlile _Automation Consultants_

Hi @wisanu wirojtecha

Usually this is caused when the trigger of the rule is the same event as one of your actions.

If this is the case with your rule, I would consider changing the trigger, e.g. to a status change or custom field update

wisanu wirojtecha

Hi Callum,

This is the current setting for my automation rule. As you can see the trigger that I'm using now is when an issue is created.

Screenshot 2021-09-27 162409.png

I believe this trigger should be executed only one time when an issue is created. Just wonder it having the issue as I mentioned earlier.

Callum Carlile _Automation Consultants_

@wisanu wirojtecha Hmm yeah you're right.

Is it definitely just the one automation rule which is being triggered? You can check this by going onto the issue in your first screenshot and clicking on the Automations 'field', which will show you all of the recently triggered automation rules for that issue.

If it is just the one rule being triggered, does the audit log for your above rule give any clues? I.e. are there 3 logs created for the 3 assignments in your first screenshot?

wisanu wirojtecha

Hi Callum,

Yeah, you are right!!! I'm found the root cause. It having some test rules that I'm created for testing purposes and it caused this issue.

Now I'm already disabled this rule. Hope this issue will be fixed.

Thanks for your suggestion. I will close this case now.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management