Custom Field Copy when Splitting Ticket Automation not working

Nikolaos Vlachos
Contributor
February 2, 2023

Hello Everyone,

 

I am trying to create an automation that whenever a ticket is split a custom field I created will be copied to the new ticket. 

Any help on how to fix this will be appreciated.

 image.pngimage.pngimage.png

 

 

2 answers

1 accepted

2 votes
Answer accepted
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 2, 2023

Hi @Nikolaos Vlachos - I see a couple potential things to look into:

  1. Is there a reason that you're trying to do this in the Advanced json section of the Edit Issue action vs selecting the desired field?  Then you can simply select copy from trigger issue
  2. If you do still find yourself needing the advanced json, you should not need "fields" in your smart value 
    1. {{triggerIssue.customField_10055}}
Nikolaos Vlachos
Contributor
February 2, 2023

Thank you @Mark Segall . Sorry I didn't clarify that in my question.  The field that I wanted doesn't appear under the "Choose field to set..." so that is the reason I am trying to do it using Advanced json. 

 

I did try your second suggestion and I am getting the below error: 

image.png

Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 2, 2023

What is the field type for the custom field?

Nikolaos Vlachos
Contributor
February 2, 2023

It is Select List (cascading)

Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 2, 2023

Ok - This makes sense.  These are a little more tricky.  You want to format the json something like this:

{
  "update": {
    "customField_10055": [
      {
        "set": {
          "value": "{{triggerIssue.fields.customField_10055.value}}",
          "child": {
            "value": "{{triggerIssue.fields.customField_10055.child.value}}"
          }
        }
      }
    ]
  }
}
Nikolaos Vlachos
Contributor
February 2, 2023

@Mark Segall  that worked perfectly.

 

Thank you very much for your support. 

Like Mark Segall likes this
1 vote
Pierre Darquenne
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 5, 2023

Actually, I tried the above and got an error message 

image.png

I had to specify that I wanted to update the ID of the team. As follows

{
"fields": {
"customfield_10100" : "{{triggerIssue.fields.customfield_10100.id}}"
}
}

Alexa
Contributor
September 22, 2023

This solved my problem, thank you so much!!

Like Pierre Darquenne likes this
Pierre Darquenne
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 22, 2023

Thank you. Appreciated 👍

Like Alexa likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events