Copying multiple choice field from JSM project to JS project

[Greg Smart]

I have a form which allows people to create a JSM ticket.  In this form they can define a set of report types to be produced which is contained in a multi-select custom field.

When the JSM issue is created, an automation rule creates an equivalent issue in a JS project as an Epic.  A second rule is then triggered which creates a task under the epic.  I want to copy the Report Type into a field in the Task.

An extra wrinkle is that in the JSM form they can specify that the task is repeated multiple times, and a task is created for each time.  This bit is working fine.  It's the copying of the multi-select I can't get to work.

For now, I've switched this second rule to be triggered manually for debugging purposes.

So inside the for loop for creating multiple tasks if required I:
Set a variable equal to the report type value from the linked JSM issue:

{{#issue.issuelinks.outwardissue.customfield_10184}}{"{{value}}"}{{/}}

This produces a value like this:

{"Lugano, PERCIST"}

I then create a task, and in the task I set the report type field (it's the same field):
{
"fields": {"customfield_10184": [{{{PETCTReportTypes}}}]}}

And this errors, because of course the value I'm trying to add isn't JSON.

I have read various articles and support tickets.  I think fundamentally my problem is that the values that get set in the custom field are enclosed in a set of quotes.  As in {"value 1, value 2}" whereas what I want is {"value 1", "value 2"}.

Any help would be much appreciated.

[Stephen Wright _Elabor8_]

Hi @Greg Smart 

Is the Report Type field on the Epic, and the Task?

If yes, could you not copy the value into the Epic at creation (via automation), and then do this again when creating the Task?

That should be possible without JSON.

Ste