Problem could be caused by a caching issue, or maybe your custom statuses are not consistently defined globally... Did you search this tracker ? There's been several reports of similar issues in the past, maybe this will help.

Note that styles for status colors is dynamically generated. Try to access the CSS file directly, http://example.com/mantis/css/status_config.php and see if the colors match. If not maybe you can debug/troubleshoot from there.

Well I do not believe the issue is with how the custom statuses are defined because there was no issue prior to the update i.e the colors displayed, furthermore when I omit the custom status, the issue persist with the defaults.

When I go to inspect the page, I cannot find reference to where status color is defined in the css / it's not defined like it should be, the line is missing all together.

@jut

• what's your setting of $g_status_enum_string?
• are all status icons black, or just the ones of some status values?
• which MantisBT version did you use before the upgrade?

@dregad while looking at some code around the status colors, I found that the cache_key we use for that is questionable (based on MantisBT version and user).
So the key will not change if someone changes a color.
I am wondering if the cache_key should just be based on the colors.
e. g. instead of

'cache_key=' . helper_generate_cache_key( array( 'user' ) )

have something like

'cache_key=' . md5( serialize( config_get( 'status_colors' ) ) )

@atrol as you pointed out yourself in 0023324:0057631, status config can be user / project specific.

This means that in a situation where this is actually the case, I guess your suggestion would effectively force the cache to be refreshed every time a user switches to another project and/or logs in with a different account, kind of defeating the purpose of the cache don't you think ?

@dregad

I guess your suggestion would effectively force the cache to be refreshed every time a user
switches to another project and/or logs in with a different account

It will just be refreshed, if the colors for a project or a user are different.
I guess that's not that typical for most of the installations, as they typically set the colors in config_inc.php.

Won't you get wrong colors (or not set black) if you don't change the cache key after someone changed colors (in general, or for a certain project)?

As a side note: Our current approach does not work if issue status from mutiple projects are displayed on a single page (e. g. "View Issues" page if "All Projects" is selected) and the colors are set on a project level.