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 to populate custom field value based on if else criteria using Automation

Laxmi Swamy

Hi Community Members,

I have created two custom fields, customfield_1 (which can store single value from the list - High, Medium, Low) and another customfield_2.

I am trying to populate customfield_2 (number data type) using the Automation based on the values stored in customfield_1.

Automation rule is successfully running without any errors but customfield_2 is not getting populated with the required output value.

Please let me know the correct syntax or any other way that I can achieve the required logic without going for any third party plugins.

Thanks in advance.

Here is the alternate JSON codes tried in Advance field editing:

{ "fields": {

"customfield_2": "{{#if(equals(issue.fields.customfield_1, \"High\"))}}50{{/}} {{#if(equals(issue.fields.customfield_1, \"Medium\"))}}25{{/}} {{#if(equals(issue.fields.customfield_1, \"Low\"))}}10{{/}} {{#else}}0{{/}}"

}

-----

{ "fields": {

"customfield_2": "{{#if(equals(issue.fields.customfield_1, "High"))}}50{{/}} {{#if(equals(issue.fields.customfield_1, "Medium"))}}25{{/}} {{#if(equals(issue.fields.customfield_1, "Low"))}}10{{/}} {{#else}}0{{/}}"

}

-----

{ "fields": {

"customfield_2": "{{#if(equals(issue.customfield_1, \"High\"))}}50{{/}} {{#if(equals(issue.customfield_1, \"Medium\"))}}25{{/}} {{#if(equals(issue.customfield_1, \"Low\"))}}10{{/}} {{#else}}0{{/}}"

}

-----

{ "fields": {

"customfield_2": "{{#if(equals(issue.customfield_1, "High"))}}50{{/}} {{#if(equals(issue.customfield_1, "Medium"))}}25{{/}} {{#if(equals(issue.customfield_1, "Low"))}}10{{/}} {{#else}}0{{/}}"

}

Accepted answers

Jovin

Hi @Laxmi Swamy

Can I recommend something a bit simpler? Rather than putting the code directly into the JSON, use more of the visual aspects to create automation flows. Here is what I would do for your solution.

Trigger: Whatever you desire
Condition: IF ELSE
1. IF Condition: Issue fields condition
  1. Field: customfield_1
  2. Condition: equals
  3. Value: High (it should be a dropdown for you)
2. THEN: Add an action: Edit issue
  1. Field to edit: customfield_2
  2. Value: 50
3. ELSE Condition: Issue fields condition
  1. Field: customfield_1
  2. Condition: equals
  3. Value: Medium (it should be a dropdown for you)
4. THEN: Add an action: Edit issue
  1. Field to edit: customfield_2
  2. Value: 25
5. ELSE Condition: Issue fields condition
  1. Field: customfield_1
  2. Condition: equals
  3. Value: Low (it should be a dropdown for you)
6. THEN: Add an action: Edit issue
  1. Field to edit: customfield_2
  2. Value: 10

Following this your customfield_2 will be updated

Joseph Chung Yin

@Laxmi Swamy -

To supplement @Jovin suggested, can you verify that the customfield2 is exposed to your project in question (meaning the context for the custom field is configurated properly).

I would recommend the triggering event should be "Field value changed" for all issue operations. In your rule, then setup the If/else condition to check for customfield1 value and then edit issue option to set the customfield2 value.

Hope this also helps.

Best, Joseph Chung Yin

Tommaso Gionfriddo _Adeptask_

Hi @Laxmi Swamy

Welcome to the Atlassian Community!

I would also recommend avoiding using the advanced field json, however I think that the most future proof option is to use the (relatively new) lookup table functionality to define the relationship between the value in customfield_1 and customfield_2.

This allows for up to 200 possible values in customfield_1 in only 3 steps.

When: Value changes for customfield_1
Then: Create lookup table
Then: Edit issue.
1. Field: customfield_2
2. Value: {{relationship.get(issue.customfield_1)}}

All comments

Jovin

Hi @Laxmi Swamy

Can I recommend something a bit simpler? Rather than putting the code directly into the JSON, use more of the visual aspects to create automation flows. Here is what I would do for your solution.

Trigger: Whatever you desire
Condition: IF ELSE
1. IF Condition: Issue fields condition
  1. Field: customfield_1
  2. Condition: equals
  3. Value: High (it should be a dropdown for you)
2. THEN: Add an action: Edit issue
  1. Field to edit: customfield_2
  2. Value: 50
3. ELSE Condition: Issue fields condition
  1. Field: customfield_1
  2. Condition: equals
  3. Value: Medium (it should be a dropdown for you)
4. THEN: Add an action: Edit issue
  1. Field to edit: customfield_2
  2. Value: 25
5. ELSE Condition: Issue fields condition
  1. Field: customfield_1
  2. Condition: equals
  3. Value: Low (it should be a dropdown for you)
6. THEN: Add an action: Edit issue
  1. Field to edit: customfield_2
  2. Value: 10

Following this your customfield_2 will be updated

Joseph Chung Yin

@Laxmi Swamy -

To supplement @Jovin suggested, can you verify that the customfield2 is exposed to your project in question (meaning the context for the custom field is configurated properly).

Hope this also helps.

Best, Joseph Chung Yin

Tommaso Gionfriddo _Adeptask_

Hi @Laxmi Swamy

Welcome to the Atlassian Community!

This allows for up to 200 possible values in customfield_1 in only 3 steps.

When: Value changes for customfield_1
Then: Create lookup table
Then: Edit issue.
1. Field: customfield_2
2. Value: {{relationship.get(issue.customfield_1)}}

Laxmi Swamy

Thanks Tommaso, tried the above solution it works like a charm. The only thing I need to cover is if I want to assign '0' value in case if the customfield_1 has blank/empty value (instead of High, Medium, Low values) as it is an optional field for the users to enter.

Laxmi Swamy

Thanks Jovin, for your support. The above solution is working as expected.

Laxmi Swamy

Thanks Joseph, I will use the same. Does it also covers the use case for Issue Creation as well.

Tommaso Gionfriddo _Adeptask_

Hi @Laxmi Swamy ,

For this base case you can simply add a default to the smart value, as per this documentation. The value will be output when nothing is returned by relationship.get().

Your edit issue value should now be {{relationship.get(issue.customfield_1)|0}}

Joseph Chung Yin

It should. However, you may want to add "Re-fetch issue data" action before your edit issue action.

Hope this helps. If my suggestion helped you, please click on "Accept answer" when you have a chance, so others with similar asks will see this posting as an answered one.

Best, Joseph

Laxmi Swamy

Thanks Tommaso, for your support.

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