Copy field from Trigger issue as JSON?

[Mark Almeida-Cardy]

I am looking for examples of what a JSON payload would look like for:

Copy Field from Trigger Issue

We are basically cascading data in fields from Epics, to Tasks, then sub tasks

Any examples would be helpful

[Simeon Ross]

Hey @Mark Almeida-Cardy,

Can you provide a bit more context? I'm not really sure what your question is about/trying to get to?

Cheers,

Simeon.

[Mark Almeida-Cardy]

Simeon,

I am looking for some advice on how to copy the values from a trigger issue to a new issue using JSON. I am able to copy other fields without issue, however, drop-down fields (single select) are throwing an error:

Error: Could not find valid 'id' or 'value' in the Parent Option object.

An Example of the JSON payload is:

{
"fields": {
"customfield_10251":"{{triggerIssue.fields.customfield_10251}}",
"customfield_10253":"{{triggerIssue.fields.customfield_10253}}",
"customfield_10269":"{{triggerIssue.fields.customfield_10269}}",
"customfield_10270":"{{triggerIssue.fields.customfield_10270}}",
"customfield_10250":"{{triggerIssue.fields.customfield_10250}}"
}
}

[Simeon Ross]

Hi @Mark Almeida-Cardy,

No worries, with you now. So the best thing to do with these fields is have a look at how they're represented in the rest view (XXXX.atlassian.net/rest/api/2/issue/SP-49?expand=names). In the case of my sample project a custom drop down when set on an issue and viewed via the above URL, looks like this:

...

customfield_11200: {
self: "https://codebarrel.atlassian.net/rest/api/2/customFieldOption/10101",
value: "2",
id: "10101"
},

...

So, with that in mind, we need to set the id in the same format in the advanced JSON:

{
"fields": {
"customfield_11200": { "id": "10101" }
}
}

or, using a smart value:

{
"fields": {
"customfield_11200": { "id": "{{triggerIssue.etc}}" }
}
}

Hopefully that helps and makes sense :)

Cheers,

Simeon.

[Mark Almeida-Cardy]

Simeon,

Yes, make perfect sense.  Thank you!

For single select drop downs, I found that "value" was required.

"customfield_10254": { "value": "{{triggerIssue.fields.customfield_10254}}" 

However, I still have one outstanding field that isn't pulling through.  What are your thoughts on User lookup fields?  I have tried both of the following with no luck or errors to referance.

"customfield_10250": { "accountId": "{{triggerIssue.fields.customfield_10250}}"

"customfield_10250": { "displayName": "{{triggerIssue.fields.customfield_10250}}"

[Mark Almeida-Cardy]

I fact,   I have solved this thanks to your guidance.  Lookup fields look like so.

"customfield_10250": { "accountId": "{{triggerIssue.fields.customfield_10250.accountId}}"

 Thanks Again.

[Simeon Ross]

No worries mate! Nice work :D