Dear community, * I have 2 projects (Project A and Project B) where the customfield_1 is set in Project A. * customfield_1 is a Select List (single choice) and has two options. * In Project B, I have customfield_2, which also is a Select List (single choice) with two options * I want to use an Automation to create a new issue in Project B and set customfield_2 based on the selection of customfield_1 in Project A using "Additional fields" and JSON, essentially mapping the values from one Select List * In my initial tests I managed to do this by using conditional logic and the if-else statements, but I was only able to do so by typing the option of the customfield_1, which might be changed by other administrators in its exact wording. I used something like "customfield_2": { "value": "{{#if(equals(triggerIssue.fields.customfield_1.value, "Option 1 name in Project A"))}}Option 1 Name in Project B{{/}}{{#if(equals(triggerIssue.fields.customfield_2value, "Option 2 name in Project A"))}}Option 2 Name in Project B{{/}}" Is there a way to reference the options of a custom field based on the option id instead of their name? I know how to find the option id in the custom field settings but I don't know how to do the mapping and didn't find yn documentation If anyone has a clue, please let me know :)

Hi @Philip Kroos - TEAM XALT - I'm wondering if you could add an IF block that checks if {{triggerIssue.fields.customfield_10633}} is EMPTY before it even attempts to do the Edit.

Hi @Darryl Lee , in the end we decided to not use ids but values, this makes the automation work. However, if we don't fill the field for customfield_10633, the automation doesn't work ("Error creating issue Specify a valid value for NAME (customfield_10632)") I tried {{#if(equals(triggerIssue.fields.customfield_10633.value,NULL))}}{{/}} but this doesn't work and still gives me the same error message. Basically, if customfield_10633 is empty, customfield_10632 should also remain empty when creating a new issue

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

Setting custom field value by option id (select list)

Philip Kroos - TEAM XALT

Dear community,

I have 2 projects (Project A and Project where the customfield_1 is set in Project A.
customfield_1 is a Select List (single choice) and has two options.
In Project B, I have customfield_2, which also is a Select List (single choice) with two options
I want to use an Automation to create a new issue in Project B and set customfield_2 based on the selection of customfield_1 in Project A using "Additional fields" and JSON, essentially mapping the values from one Select List
In my initial tests I managed to do this by using conditional logic and the if-else statements, but I was only able to do so by typing the option of the customfield_1, which might be changed by other administrators in its exact wording.

I used something like

"customfield_2": { "value": "{{#if(equals(triggerIssue.fields.customfield_1.value, "Option 1 name in Project A"))}}Option 1 Name in Project B{{/}}{{#if(equals(triggerIssue.fields.customfield_2value, "Option 2 name in Project A"))}}Option 2 Name in Project B{{/}}"

Is there a way to reference the options of a custom field based on the option id instead of their name? I know how to find the option id in the custom field settings but I don't know how to do the mapping and didn't find yn documentation

If anyone has a clue, please let me know

Accepted answers

All comments

Darryl Lee

Hi @Philip Kroos - TEAM XALT --

I think this should work:

"customfield_2": { "id": "{{#if(equals(triggerIssue.fields.customfield_1.id, "optionId-1-a"))}}optionId-1-b{{/}}{{#if(equals(triggerIssue.fields.customfield_2.id, "optionId-2-a"))}}optionId-2-b{{/}}"

Samuel Gatica _ServiceRocket_

HI @Philip Kroos - TEAM XALT

To reference the option ID in the field you can use the following smart value:

Best regards

Sam

Darryl Lee

Documentation for Advanced Field Editing for Single-select custom fields:

Select a single value from a defined list of values. You can address them by value or id.

"customfield_11449" : { "value": "option3" }

or

"customfield_11449" : { "id": 10112 }

Bill Sheboy

Hi @Philip Kroos - TEAM XALT

Yes, and...to the other suggestions offered:

I recommend using a lookup table rather than conditional logic to translate the field value. That will be easier to maintain / debug in the rule. Please look here to learn more about lookup tables:

https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798

Kind regards,
Bill

Philip Kroos - TEAM XALT

Hi @Darryl Lee , I agree, this should work, yet it doesn't

My formula is currently

"customfield_10632":
{ "id": "{{#if(equals(triggerIssue.fields.customfield_10633.id, "11392"))}}11390{{/}}{{#if(equals(triggerIssue.fields.customfield_10633.id, "11393"))}}11391{{/}}"

customfield_10632 equals customfield_2 in Project B.
- 11390 equals optionId-1-b in Project B (since this is where customfield_10632 is).
- 11391 equals optionId-2-b in Project B (same as above).
customfield_10633 equals customfield_1 in Project A.
- 11392 equals optionId-1-a in Project A (since this is where customfield_10633 is).
- 11393 equals optionId-2-a in Project A.

In other words, the mapping is as follows:

When customfield_10633 in Project A has option ID 11392, set customfield_10632 in Project B to option ID 11390.
When customfield_10633 in Project A has option ID 11393, set customfield_10632 in Project B to option ID 11391.

Maybe I'm missing something obvious but the formula should work

Bill Sheboy

Hi @Philip Kroos - TEAM XALT

Context is important for automation rule questions, so without seeing your complete rule and where that expression is used, diagnosis is challenging.

One thing is certain: please note you have nested the double-quotation marks in the expression, and so that is unlikely to evaluate correctly. The workaround for that would be to determine the id value, saving it to a variable, and then use that variable in the JSON expression.

Kind regards,
Bill

Welcome!

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

Quick Links

Find more posts tagged with

custom-field

jira-cloud

automation

smart-value

functions