Map to Multi-select field value in Jira Product Discovery project

[David Friedrich]

I have 2 projects:
1 Service project (CSHP)
1 Product Discovery project (SIR)

If someone submits an idea via portal, first automation automatically creates a new and linked idea ticket in the PD project (SIR). Also the same automation copies the value of a normal jira field multi-select list "Roadmap-Ziele" into the new idea ticket (same field).

Now I want a second automation to run in SIR project and map the value of the jira field ("Roadmap-Ziele") to that of a Multi-select field in PD ("Ziel"). The rule is triggered but I get this error:
Edited issue successfully, however some of the set fields aren't available. Fields ignored:

Ziel (customfield_10073)

I tried different ways of mapping the values of the two Multi-select lists but always get the same error message. 

[Bill Sheboy]

Hi @David Friedrich 

First thing: for rules with the Issue Created trigger, I recommend always adding the Re-fetch Issue action immediately after that trigger.  This will prevent timing problems where some of the issue data may not be available yet to the rule.  The re-fetch will reload the data before proceeding with the rule steps.

You describe two different projects, but the rule scope is single-project and the rule does not appear to access the issue in the other project.

• Your Jira Site Admin will need to help change the rule scope to multiple-project
• The rule will need to use the Lookup Issues action to access the JPD Idea to copy the field value

Kind regards,
Bill

[David Friedrich]

Hi Bill,
thanks for recommending re-fetch. I implemented it, but didn't solve the issue.

The screenshot is from the second rule. 

The ticket gets successfully created in JPD from 1rst rule and data is copied (value from jira custom Multi-select field "Roadmap-Ziele"). Now the second rule is triggered to sync the value from the Jira custom field to the "Discovery"-field "Ziele" within the same JPD project and same ticket, so scope should be fine. But field is ignored. I suspect that a discovery field isn't accessible by the Rest api.

I tried many ways including different JSON in "additional fields" to map the values, always the same error message field ignored. 

[Bill Sheboy]

If both issues are in the same project, you are correct that single-project scope will work.

As the field you are trying to update is multiple-option select, you may need to use JSON to update it if the field types are different...even if the values are the same: 

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Multi-select-custom-field