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 based on links

Jakub Szymanski_18iakt

Hi,

I'm trying to setup the automation rules which will be based on few conditions. Main goal is to transition incident ticket to next stage once all of those conditions are met. I used few types of configuration however none of them work as intended.

My first call was to go with:

When: Issue updated -> If: all match -> Issue field condition: field "x" is not empty, Issue field condition: field "y" is not empty, Related issues condition linked issue, blocked by, are present -> Then: trasnition issue to: work in progress

However this formula didn't work as expected, sometimes it was triggered, however most of time don't. I was also trying to use different configuration based on for example When: Issue linked or When: field value change however either of those were working.

Can someone help me please how i can setup the rules based on attached links and updated fields? Many thanks in advance.

Accepted answers

Stefan Salzl

Hi @Jakub Szymanski ,

Does the rule not even get triggered (no entry in the audit log) or is it not performing the expected action (the transition)?
Could you reproduce the behaviour/determine when the rule triggers and when not?
Could the rule be limited to a certain issue type? (that also might be an improvement from performance perspective)
What kind of fields are those you are checking?
--> maybe you could try to trigger the rule and document it with screenshots (including one of the audit log) for gaining a better insight

From my personal point of view I would split the rule as in fact the rule could be triggered by several events (at least it seems so from your conditions).

Looking forward to your answer.

Best
Stefan

All comments

Matthew Day_7dgif0

From your automation list, you can select the 3 dots for your rule to export a JSON file for the actual configuration. If you attached or posted that, it may get a better response than trying to summarize. Unfortunately, I can't help with what you're attempting.

Jakub Szymanski_18iakt

@Matthew DayHi Matthew, would that help? I'm not sure how this JSON file works.

Stefan Salzl

Hi @Jakub Szymanski ,

Does the rule not even get triggered (no entry in the audit log) or is it not performing the expected action (the transition)?
Could you reproduce the behaviour/determine when the rule triggers and when not?
Could the rule be limited to a certain issue type? (that also might be an improvement from performance perspective)
What kind of fields are those you are checking?
--> maybe you could try to trigger the rule and document it with screenshots (including one of the audit log) for gaining a better insight

From my personal point of view I would split the rule as in fact the rule could be triggered by several events (at least it seems so from your conditions).

Looking forward to your answer.

Best
Stefan

Jakub Szymanski_18iakt

@Stefan SalzlHi Stefan,

Rule is triggered, however most of time it is saying that "no action performed" and "The following issues did not match the condition" which is strange, cause all the fields are present and updated. When there is success of the rule, usually is when i'm updating it once again (so if i put all the fields for the 1st time it's not working) but when i'm updating fields for 2nd time it is working as expected.

Yes, i can add some restriction that rule should working only for incidents, how i can do this?

I need to updated:
Urgency - which is JIRA based field of single choice
Assignee - which is also JIRA based field for assignee in the ticket
Severity TEST - this is being auto calcuated based on impact and urgency which i setup different autoamtion rule which is working as expcted. Severity is calculted based on matrix. This is field that i have made on my own.
Linkin issue - this is standard linking between the isses on the JIRA. There is no matter what i will link, what is matter that i need to use "is blocked by" or "blocks" rule.

I cannot seperate those to several rules as all of those fields have to be update to apply this rule, i don't wnat to have 1 field updated and trigger the rule, i need all of those updated to trggered it. Most important here is the link for new issue.

Do you need more details to help me? Please let me know.

Stefan Salzl

Hi @Jakub Szymanski ,

I´ll refer to several parts of your answer in blocks:

most of time it is saying that "no action performed" and "The following issues did not match the condition"

Could you add a "log action" that reads out all the requested fields? (how to debug an automation rule)

Severity TEST - this is being auto calcuated based on impact and urgency which i setup different autoamtion rule which is working as expcted. Severity is calculted based on matrix.

To get that right: This field will be filled by another autmation rule that will be triggered if you fill out the field "Urgency"
eg. we have Story-A
- we insert/choose urgency
- then another automation rule is triggered
- this triggered automation rule calculates a value and fills in this value to Story-A (which was the trigger-issue), field "Severity TEST"
if this is the case could you please send a screenshot of the rule details (from the automation rule of your original question, not the one that does the calculation)
- As one of your fields (checked in the condition) is set/updated by another automation rule your rule from your question needs to be allowed to be triggered by another automation rule. I guess that might be the reason why your rule often triggers on the 2nd change

Yes, i can add some restriction that rule should working only for incidents, how i can do this?

This could be handled by another condition after the trigger that checks for the issue type. The rule would still be triggered by update of any issue tpye but would then at least would stop immediatly after the trigger if the issue type doesn´t match. Otherwise all other checks would be done too. Might only be a small change but I prefer to step out of a rule (if i know the conditions) as early as possible (if the conditions don´t match) to avoid unnecessary processing

Uffff....that´s quite a lot to read. Hope it helps.

Looking forward to your answer.

Best
Stefan

Jakub Szymanski_18iakt

@Stefan SalzlMany thanks for your comment, i really appriciate your help.

I hope i did everything fine, here is screenshot from the log, it's marking as success now after i add debuging, but still not working.

To get that right: This field will be filled by another autmation rule that will be triggered if you fill out the field "Urgency"
eg. we have Story-A
- we insert/choose urgency
- then another automation rule is triggered
- this triggered automation rule calculates a value and fills in this value to Story-A (which was the trigger-issue), field "Severity TEST"

JS: Yes that is the case, however not quite, it's based on two fields Urgency and Impact. I have even removed Severity from rule instead adding just Urgency and Impact as those are manual choice, and still that didn't work. To be honest i'm suspecting that there is some problem when i'm linking issue, however i'm not sure if that's the case. Screenshot looks like this for this rule:

This could be handled by another condition after the trigger that checks for the issue type. The rule would still be triggered by update of any issue tpye but would then at least would stop immediatly after the trigger if the issue type doesn´t match. Otherwise all other checks would be done too. Might only be a small change but I prefer to step out of a rule (if i know the conditions) as early as possible (if the conditions don´t match) to avoid unnecessary processing

JS: Thanks for the hint i will look for that and add it. that might be helpful.

Please let me know what else can i do. And many thanks for all the time you already gave me.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

automation

jira-service-management-cloud

jira-service-management