Automation and epic colours by assignee

[Alexis Manouvrier]

Hello everyone,

For our project, we are trying to change the epic colours depending on the assignee which gives us a good and visual export for reviews. We, of course, would like to do it by automation where when I assign myself, for example, my epic will now be yellow and when my colleague assign herself, it becomes orange etc.

Right now, when I set it up in automation as:

- When ticket is assigned

- When assignee is "xxx"

- Edit ticket field:

{"fields":
{
"customfield_10012" : "ghx-label-3"
}
}

I have an error telling me the field doesn't exist while it should be (I have the square on the top left of my epic to change it manually).

Is there a setting I missed ? Thanks in advance!

[Trudy Claspill · Accepted solution]

Hello @Alexis Manouvrier 

Welcome to the Atlassian community.

Are you sure you have the correct custom field id?

Have you tried using "Epic Color" as the field name instead of "customfield_#####"?

In this article it mentions that the epic color would be derived from the Issue Color field in the future. Have you tried that field instead?

[Alexis Manouvrier]

Hello @Trudy Claspill ,

I have tried with all three of them and the error is still the same everytime.

[Bill Sheboy]

Hi @Alexis Manouvrier -- Welcome to the Atlassian Community!

Yes, and...to Trudy's answer:

The correct field is now the "Issue color", and the custom field id may be used in that JSON edit to change it.

And...a later Jira change altered the allowed color values.  When I just checked some examples, the color values appear to be people-friendly names now: orange, purple, grey, dark_purple, etc.

I recommend using experimentation and an issue search to look at the Issue Color field to find the names you want to use.

Kind regards,
Bill

[Trudy Claspill]

I used the following, and it worked.

I tried in both a Team Managed and a Company Managed Software project.

The Issue Color field is not explicitly shown in the Screen configuration or Layout, nor in the Field Configuration.

[Alexis Manouvrier]

Thanks for this information, it is now working properly :)