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

Priority not assigned based on automation

Alex_1qu7vj

Hi all,

I created a very simple priority assignment rule based on impact field. This part worked for a few days but then stopped. Please see attached screenshot for explanation. The incident submitted two days ago by same person/same form/same fields worked (highlighted in green above), however, since yesterday the match is no longer found (highlighted in red).

Anyone had any idea why it stops working? Note that I had another more complex rule initially implemented which worked for a few days and then stopped for no reason. I thought that logic was too complex so I created a plain rule which worked for a few days and then stopped as well. Any ideas what's goin on? This is a simple 1 input field and I had no changes to anything. I also set 5 seconds delay to re-fetch the data just in case.

Totally at loss what's going on and what am I missing.

Accepted answers

All comments

Walter Buggenhout

Hi @Alex and welcome to the Community!

Is there any reason why you have a Refetch issue data action in your rule? You might have of course, but just looking at your rule I can't really figure out why you would need that here. This may impact the data that's on your issue, so I would suggest to remove this and see what happens.

Hope this helps!

Alex_1qu7vj

Hi Walter, thanks for your reply. I have no idea why it's there but this was a part of the schema used by our corporate to assign priority. This schema works for corporate team, but not for me.

Anyway, I removed that part and will monitor what happens.

Alex_1qu7vj

Just received a few new incidents. Still doesn't work even with data re-fetch deactivated.

Not sure what's going on. I had two rules and both of them worked for a few days and then, suddenly, stopped, the rules are based on a single field.

I guess the field passed via the form is not the same as used by automation? The name is the same though but for some reason it doesn't accept the value passed in it.

Walter Buggenhout

Aha, ok. Is this an advanced form where you can decide to map the form field to a Jira field (one thing to check). And if so, is it mapped correctly.

Next, do you have multiple custom fields with the same name in Jira and indeed - in this case you are referencing the wrong one?

Or is there only one field, but does it have different contexts configured for different projects?

All these options can indeed impact the data being different than what you expect.

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