Hi there,
Just wondering if the colour of issue schedule bars on the timeline view can be automated? Is there a way we can assign a specific colour through an automation rule?
Thanks,
Dominique
Hi @Domi
Yes, that is possible. The field used for this is the epic's "Issue Color", and that can be edited using an advanced edit with JSON, as described here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Text-custom-field
For example,
{
"fields": {
"customfield_10017": "orange"
}
}
As a tip, to learn how things work behind-the-scenes in Jira and learn if automation can change those things, there is a how-to article to learn any supported smart values for fields, and their syntax: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/
Using this, you can find an example issue with your field, look for the field's smart value, and see the impact when you change it.
Kind regards,
Bill
Thank you, Bill. That helps. I've set up this automation rule, but it doesn't currently work. I'm getting this error and can't figure out what it means / how to solve it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm assuming this isn't working because the custom field number is incorrect. Would you know where in the inspect code, I can find this number?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please try this how-to article when you need to find the smart value or custom field id for a field. Essentially you identify an issue with your field, call a REST API function from a browser, and then search for the field in the results to learn the correct one for your site.
https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/
And, would you please post an image of your complete audit log details for the execution? That may provide some context for where that error is occurring. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the documentation, Bill. That's awesome! I may have found the custom field number now. We'll see if it works.
Here are some more screenshots of the audit log. Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Would you please post an image of your complete rule in one image, and another of the edit action where the error is occurring? (You can capture the entire rule in one image using a scrolling capture, either with a browser addon or app.)
That will help to see the full context of where the error is showing in the rule. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Would you please upload those as static images of the complete rule and audit log, and not as video captures? The video continually moving does not help to identify where in the rule the error is happening.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill,
Great news! I can confirm the automation rule is now working. I've got the correct custom field number. It's automatically setting a particular colour to the epic based on the criteria I have in the automation rule.
Thanks for your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome; I am glad to learn it is working!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Domi
I'm not sure that you can do this via automation but please check any issue with those colours set if value exist in a ticket via rest api. If yes, you will be able to do this via automation.
Regards,
Seba
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.