nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Copy Element Connect Field with JSON in Automation

Gor Greyan

Hi Colleagues.

Please help me with this case.

I have automation, which opens sub-task. In the main ticket I have Element Connect field, which I want to copy in the sub-task via Additional fields JSON, but I can't.
Kindly ask you to help with the JSON syntax.

Thanks in advance.

Accepted answers

Simon Laffont

Hello @Gor Greyan

I am part of the Elements Connect support team.

Where is the Automation rule triggered, in the sub-task or in its parent? Can you please share a screenshot to show us how your automation rule is configured?

Kind regards,
Simon.

All comments

Zuri Suwru

Hey there,

Make sure to copy the custom field's value "asJsonStringArray".

"customfield_12345" : {{ issue.customfield_12345.asJsonStringArray }}

I would also suggest double checking whether the custom field is properly configured for your sub-tasks or not.

Hope this helps,
Zuri

Gor Greyan

Hi @Zuri Suwru ,
Tried this, but got the following error.
Error while parsing additional fields. Not valid JSON.

Gor Greyan

Zuri Suwru

Pardon me, I though you were interested in the syntax for the specific field in question. I did not think you need a complete JSON code.

Can you try it like this?

{
"fields": {
"customfield_20137": "{{parentIssue.customfield_20137.asJsonStringArray}}"
}
}

Simon Laffont

Hello @Gor Greyan

I am part of the Elements Connect support team.

Where is the Automation rule triggered, in the sub-task or in its parent? Can you please share a screenshot to show us how your automation rule is configured?

Kind regards,
Simon.

Gor Greyan

Hi Dear @Simon Laffont ,
Automation is triggered when the issue goes to Recruitment status, after that sub-task is created with this automation. I want to copy the Element Connect field from the Recruitment task into the created sub-task.

Simon Laffont

Hi @Gor Greyan

Alright, thank you.

I think @Zuri Suwru's answer was good, but you should use "triggerIssue" instead of "parentIssue", like this:

{
  "fields": {
    "customfield_20137": {{triggerIssue.customfield_20137.asJsonStringArray}}
  }
}

Can you please try it and let me know if it works?

If the problem persists, please tell me the type of the connect field you are using (Live Text, Live User, Snapshot Text, etc...) and also if it's single or multi-value.

Kind regards,
Simon.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

data-center

json

jira-service-management

jira-service-management-data-center