Advanced copy field value from epic to task

[Anastasia Seidaridi]

Hi everyone,

I have the below automation working in several of our projects.

The requirement is to add one more field to this automation which is not present in the dropdown menu. It says to use the More Options where I tried to figure out what I need to write but I failed. I found this example online

{
      "edit": {
        "customfield_id": [
           {{#triggerIssue.customfield_id}}
               {"add": {"value": "{{value}}"}}{{^last}},{{/}}
           {{/}}
       ]
     }
}

and tried it but I am getting the following from the audit log:

I don't know if it matters but the field that I trying to include is locked. 

Help?

[John Funk]

Hi Anastasia,

It sounds like they field is not available - which would explain why it is not in the dropdown as well. Check the Context for the custom field to be sure it includes the project you are working with in this rule. If it is, check to see if it is on the Create screen for that project. 

[Anastasia Seidaridi]

Hi @John Funk

It is a locked field and it says:

It is associated with my screens and I can see it in all the projects.

[John Funk]

Okay - thanks for sharing that. What type of project are you using? Team-managed? Company-managed? Jira Work Management?

[John Funk]

Take a look at these other posts as well:

https://community.atlassian.com/t5/Advanced-Roadmaps-questions/Can-Automation-set-the-Team-field-when-an-issue-is-assigned/qaq-p/1616145

https://community.atlassian.com/t5/Advanced-Roadmaps-questions/TEAM-field-support-in-automation/qaq-p/1604343

[Anastasia Seidaridi]

It is a company-managed project.

[John Funk]

Very good - see the other posts - not looking good right now. 

[Anastasia Seidaridi]

I tested it with other fields that work for sure and I am getting the same result. 

I think the json is wrong. 

[John Funk]

Can you share the actual json that you have?

[Anastasia Seidaridi]

{
"edit": {
"customFieldId_10001": [
{{#triggerIssue.customFieldId_10001}}
{"add": {"value": "{{value}}"}}{{^last}},{{/}}
{{/}}
]
}
}

I am really not literal with json so I wouldn't find a mistake

[John Funk]

Should be customField_10001 not customFieldID_100001

[Anastasia Seidaridi]

Sorry John, 

I can't see what do you mean. Both of them are customFieldId_10001. I copy-pasted the value from the field's info.

[John Funk]

You do not need the letters ID in there.

[Anastasia Seidaridi]

Oh, I see now, I thought the extra 0 was the issue. I just tried it and unfortunately got the same result.

[John Funk]

Hi @Anastasia Seidaridi  - So sorry, this got buried somewhere and I missed the email. Did you ever get this working? 

[Anastasia Seidaridi]

Hello @John Funk

No worries, I managed to get it to work by setting automation in each project separately. Unfortunately couldn't set it as a global automation but it works for now.

[John Funk]

What type of field is this? Strange that it would not show in a dropdown or allow you to create globally. Is there a Context on the field that limits which projects/issue types it is available for? 

[Anastasia Seidaridi]

It is the "Team" field that is not available in the dropdown and is also locked. 

[John Funk]

Ah, that would explain that then. I think they are still working on the functionality of that field and it will be available at some point. I don't know of any timeframe though.