Issue with Jira Automation sourcing custom fields

[Jonathan Do]

Good morning all,

We're working on streamlining some workflows and are attempting to use Jira Service desk to aid in this purpose. Here's a general layout of how we want it to work.

1. Users goes to JSD and fills in the request and all relevant fields.

2. Using Jira automation, when a ticket is created from this request type, it will create 5 new tickets with each populating fields from the original ticket.

The issue i'm running into is that I don't see the custom fields no can I call out a source field from the original. Is there a configuration I need to make?

[Angélica Luz]

Hello Jonathan,

Thank you for reaching out to Atlassian Community!

When using Automation, it's possible to copy values from custom fields from the parent issue, but some fields are not supported as mentioned on the automation.

With that said, you can use JSON to set the fields that are not available on the list.

For more details, please check the documentation below:

• Advanced field editing - JSON

Regards,
Angélica

[Rogelio Tonatihu Rodriguez Rodriguez]

@Angélica Luz 

Im having a similar issue.

Im trying to copy the Team Field from an epic to its child when the child issue is created.

As you mentioned, the Team field is not one of these available on that list.

I am able to "hardcode" the team using this code:

{
"fields": {
"team": "1",
}
}

But what I need is copying it from the epic.

Trying this:

{
"fields": {
"team": {{issue.epic.team}},
}
}

Throws an error:

Edit issue

Error while parsing additional fields. Not valid JSON.

[Rogelio Tonatihu Rodriguez Rodriguez]

Just solved my issue by doing this:

{
  "fields": {
    "team": "{{issue.epic.team.id}}"
  }
}