Hi all, I'm trying to set up an automation rule with the following logic: * When I link a delivery ticket to an idea in JPD, I want the custom field of that idea (="Coral Component") to be set to one of the options of that custom field. * Which option it should be depends on the Component (Jira Cloud) field of the delivery ticket. * See my script below. But then somehow Jira Automation is not able to find that custom field in JPD, see: Is there any solution to this error? Thanks!

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; } } }

Editing custom JPD fields through Automation causes errors

Mart Postma

Hi all,

I'm trying to set up an automation rule with the following logic:

When I link a delivery ticket to an idea in JPD, I want the custom field of that idea (="Coral Component") to be set to one of the options of that custom field.
Which option it should be depends on the Component (Jira Cloud) field of the delivery ticket.
See my script below.

automation rules.png

But then somehow Jira Automation is not able to find that custom field in JPD, see:

audit error.png

Is there any solution to this error? Thanks!

Accepted answers

Mart Postma

@Bill Sheboy

Got a reply back from support: apparently there is an issue with the configuration of our Automation bot on our Atlassian site. Don't know if the issue is only applicable to our instance or if it is an Atlassian issue in general. Their engineering team is working on a fix.

All comments

Bill Sheboy

Hi @Mart Postma

Some of the errors automation rules show do not always indicate the actual, root cause of a problem. For what your audit log shows, I wonder...

Automation rules which read / edit issues in multiple projects need to be global or multi-project in scope. A rule which is defined in a single project cannot do so.

What is the scope of your rule: single project or global / multi-project?

Kind regards,
Bill

Marina Rambo_so6vt2

Are you using the customfield_12345 configuration for calling out the field? Or are you using the name? I find the custom field is far more likely to work than the name.

1 . Find the custom field name of your issue by using the Jira API to inspect your JSON.

https://yourdomain.atlassian.net/rest/api/2/issue/AAA-111?expand=names

Replace "yourdomain" in the above with your jira workspace.

Replace "AAA-111" with an issue that has Coral Component selected.

2. Next search the JSON for "Coral Component".

This is easier if you use an online JSON IDE - I used JSON Editor Online. It will format your JSON so it is easier to read, and give you a search tool to find the info easier.

If you use it, copy and paste all the JSON that was returned from your REST API query above.

Once you find the line that says

"customfield_12345": "Coral Component",

you will know you found the right custom field.

Note: this does not address the rest of the automation, just may help find the field you are looking for.

Mart Postma

Hi @Bill Sheboy

The automation scope is set to Global.

Mart Postma

Hi @Marina Rambo

Thanks for your elaborate reply.

I have found the customfield_id for this field, but how can I now use this field to update/set the new value in the automation rule?

Marina Rambo_so6vt2

@Mart Postma

You would then go into > More Options and edit the JSON. Here is some info on how to do that:

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

Hope that helps!

Mart Postma

Hi @Marina Rambo - CC: @Bill Sheboy

I updated the rule with the following JSON (note that XYZ and cf_123 are of course updated in my actual script):

{
   "update": {
      "customfield_123": [{
         "set": "XYZ"
      }]
   }
}

But unfortunately I still receive errors upon running:

Do I need a system-value for "set" as well, rather than the text-value "XYZ"? If so, how to find that one?

Or if not, what could possibly fix this?

Thanks once more!

Mart Postma

@Bill Sheboy

Rohan Parakh_067v9j

@Mart Postma were you able to get this fixed? I am seeing the same issue

Mart Postma

Hi @Rohan Parakh - yes I was able to get this fixed with the help of Atlassian support.

The automation would run under my account, but not under the Automation for Jira account. At the time, I reached out to support and it looks like that only they can fix it, so not unfortunately yourself:

That being said, we identified a small issue with the permissions granted to the Automation bot on your site and are already working on a fix. As soon as I get an update from the engineering team I'll let you know!

So if you have the permissions to do so, reach out to Atlassian JPD support and link this Community thread, or ask your (technical) Atlassian site admin to do so for you. They usually don't undertake any action based on issues on the Community pages.