We have a team that get ideas in via our JSM portal.
I previously set up an automation to create an item on their backlog on their JS project which copies across the values to those exact same fields in their JS project on their issue view.
This worked beautifully until they wanted to use a multi-select field. After adding in the multi-select field and updating the automation so this passed the correct info across I noticed that everything is copied over except the multi-select field values (even when only a single value is selected in the field).
I did some digging and came across this article, wondering if the bug also applied to JS, not just Jira Product Discovery.
I tried the solution outlined here and get an error when the automation runs. The rule doesn't work at all now due to the Advanced JSON in my automation.
Does anyone have another solve for this? I discovered this last week and used a single select field instead on another item, but multi-select is the most appropriate and cleanest way to get this to work for this particular team.
I've included screeenshots of my automation below, incase I'm the problem and have made a mistake I haven't seen. 😅
Thanks in advance!
In the step where you are creating the variable, change
{{#issue.customfield_12209}}{"value": "{{profpoints}}"},{{/}}
to
{{#issue.customfield_12209}}{"value": "{{name}}"},{{/}}
The {{name}} part of that will give you the display name of the values selected.
I agreed with @Mikael Sandberg
When one setting up local variable in the automation rule, you can also reference the following link to see how json format is used-
https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/
Hope this also helps.
Best, Joseph Chung Yin
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.