Hi -
I created a BRAG colour field - RAID Level (custom field that has the colour coding added based on the hack mentioned in this Atlassian thread, see my screenshot below).... I added an automation to this field based on the various value ranges in another numeric custom field RAID Severity.
For example:
In the same way I have created other 3 automation rules to set the colour based on the value ranges of the RAID Severity (set Amber 12 to 16; set Yellow for values 9 to 12)
(P.S. - RAID Severity is auto-calculated through a Jira Automation)
I am facing some issues around this.
1. The RAID Level does not auto-set if the RAID Severity (auto-calculation is on)
2. I turned off the RAID Severity, and found that the RAID Level value is set when I manually put in a value in RAID Severity. Also, if I change the value from 3 to 6 the RAID Level colour does not change from Blue to Yellow. The initial colour is retained no matter the value I put in.
This brings in a lot of questions to mind such as does Jira support automation on automation. Is there a way to check for multiple OR conditions (not AND) at once that is have one rule for colour coding instead of 4 different rules and is there way to tell JIRA which rules runs when.
PLEASE HELP!!!
This is possible; I also consolidated it into one rule for ease.
The rule uses...
---
Prerequisites
You're going to use the Option IDs in the rule to set the field value - to get these:
Also take note of the RAID Severity Custom Field's ID at the same time:
---
Rule
---
Notes:
---
Let us know if this works for you!
Ste
Hi Stephen - I really appreciate the time you took to provide each step by step instruction. I have configured per all the instructions, I am not aware of JSON functions, I am just failing on the JSON line of code. When I have 'customfield' in my line of code it is red underlined hence I updated it as below.
1. As you mentioned in Action above, do I need to add something in place of 'customfield_' before the field ID
2. In place of # what do I need to enter
{
"RAID Level": {
"value": "raidLevel.get(issue.10340.format("#"))"
}
}
Thanks,
Kitty
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I didn't use the Advanced section - no JSON should be required.
You can enter the smart value directly into the box below "RAID Level" when selected as the field.
Remove the JSON in Advanced to avoid error.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephen - I have added the smart value under RAID Level (screenshot below), yet the RAID Level field is not auto-populating with any colour value. The RAID Level field ID is also entered correctly.
I know I am almost there just clueless on how to proceed or even troubleshoot.
Thank you once again for helping out.
P.S. The variable name in Create Lookup is all in small caps (raidlevel). Could it be because of Raid Level field value options are neither string or numeric (the colour icons I believe are considered as strings though)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You need to use the Custom Field ID for the number field (i.e RAID Severity) not the RAID Level select list in the "raidlevel.get" smart value.
This is to allow you to compare RAID Severity to the Key set within the Lookup Table.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thankkkk you!!!... It Worked...
... cannot thank you enough .. i learnt something new and advanced further in my journey to understanding Jira
(At times I have to refresh the issue/ticket a couple of times for the rule to take effect, reading on how to improve the triggering of the rules)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome, glad its working!
The rule can take a few seconds to activate - it is completing some more complex logic :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.