New status colors not applied on Jira 8.2 and above
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
The information in this page relates to customizations in Jira. Consequently, Atlassian Support cannot guarantee to provide any support for the steps described on this page as customizations are not covered under Atlassian Support Offerings. Please be aware that this material is provided for your information only and that you use it at your own risk.
Also, please be aware that customizations done by directly modifying files are not included in the upgrade process. These modifications will need to be reapplied manually on the upgraded instance.
Solution
Problem
Jira 8.2 and higher brings status colors, as described on the Release Notes page. However, after upgrading Jira to version 8.2 or higher, new status colors are not applied and old ones are still visible on issue screen:
Possible causes
Cause 1: custom CSS overrides status colors
It is possible that there is a custom CSS that overrides the colors to the old ones, as explained here. Custom CSS can be injected through the Announcement banner or through a custom add-on script.
Cause 2: custom add-on overrides status colors
There are some custom add-ons that revert status colors to old ones. For example, Zephyr for Jira is one of these add-ons (version 5.5.1.55108513). Disabling custom add-ons one by one (preferably on a test environment) will help to determine which add-on is the culprit.
Workaround
Possible workaround is to inject the following custom CSS through the Announcement banner. It will set the colors to the default ones shipped with Jira 8.2 and above.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
<style type="text/css">
.aui-lozenge.jira-issue-status-lozenge-yellow, .aui-lozenge.jira-issue-status-lozenge-inprogress
{
background-color: #0052cc !important;
border-color: #0052cc !important;
color: #fff !important;
}
.aui-lozenge.jira-issue-status-lozenge-blue-gray, .aui-lozenge.jira-issue-status-lozenge-new
{
background-color: #42526e !important;
border-color: #42526e !important;
color: #fff !important;
}
.aui-lozenge.jira-issue-status-lozenge-green, .aui-lozenge.jira-issue-status-lozenge-done
{
background-color: #00875a !important;
border-color: #00875a !important;
color: #fff !important;
}
</style>Resolution
Resolution for Cause 1
Remove the custom CSS that overrides the colors: check the CSS injected through the custom add-on script or through the Announcement banner.
Resolution for Cause 2
In some cases, upgrading the culprit add-on to a higher version updates colors to the new ones.
If upgrading the add-ons does not help, apply the workaround and contact the add-on vendor for more information.
Was this helpful?