JIRA Automation - I want to set EPIC Color when a field changes to a specific setting.

[markus_neuwald_canon_at]

I followed the instructions from the Atlassian documentation article “How to update the Epic Color Field using the automation rule?” to set the Epic Color via automation when triggered.

However, for some reason, it’s not working.

The audit log shows an error indicating that the custom field is not available.

I used the JQL search as described in the article to identify the custom field ID for Epic Color.

Is there a step or detail I might have missed?

[Bill Sheboy · Accepted solution]

Hi @markus_neuwald_canon_at 

I added this separate thread so you can comment and accept this one.  That will help others reading this in the future with similar questions.  Thanks!

Some additional things to check are the work item fields and permissions:

Using this how-to article, you may confirm if that field is available to the work item and its value.  The essential steps are:

• identify the key for the work item you are trying to update
• with a new browser tab, enter your key with your Jira URL:
  • yourJiraURL/rest/api/2/issue/yourWorkItemKey?expand=names
• search on the page for your field, such as with CNTRL-F (Find)

For permissions, who is the actor for the rule in the details at the top?  Is it the default of "Automation for Jira" or was it changed to someone else?

Kind regards,
Bill

[markus_neuwald_canon_at]

Hi Bill,

to set the actor to "Automation for Jira" solves the issue.

Thank you,

Markus

[Akhand Pratap Singh]

Hello @markus_neuwald_canon_at ,

Good day, Welcome to Atlassian Community!!

Instead of using the old "Epic Color", you should use the "Issue color" custom field.

Please refer this article, do let me know if it works Change the Issue Colour through automation | Jira and Jira Service Management | Atlassian Support

Do let me know if it works or if you face any issue.

Best Regards,
Akhand

[markus_neuwald_canon_at]

Hi Akhand,

Thank you for the suggestion — unfortunately, the result remains unchanged.

[Bill Sheboy]

Hi @markus_neuwald_canon_at 

Some fields may only be set from rules using the custom field ID rather than the smart value name.  Have you tried using customfield_11441 in the JSON expression?

Kind regards,
Bill

[markus_neuwald_canon_at]

Hi Bill,

sorry for the late response, i was on vacation.

yes, i tried it and today i tried again with the same result.

[Bill Sheboy]

Hi @markus_neuwald_canon_at 

Some additional things to check are the work item fields and permissions:

Using this how-to article, you may confirm if that field is available to the work item and its value.  The essential steps are:

• identify the key for the work item you are trying to update
• with a new browser tab, enter your key with your Jira URL:
  • yourJiraURL/rest/api/2/issue/yourWorkItemKey?expand=names
• search on the page for your field, such as with CNTRL-F (Find)

For permissions, who is the actor for the rule in the details at the top?  Is it the default of "Automation for Jira" or was it changed to someone else?

[markus_neuwald_canon_at]

Hi Bill,

the reason was the actor. I don't know why or how it happens, but my account was set as actor, which i never did. All of my other rules have "Automation for JIRA" configured as actor.

Do i have to click on "accept the answer" from Akhand in that case?

Thank you,

Markus