Hello!

We are facing the same problem, look and feel configuration is not beeing picked up.

Even worse, other configurations like jira.title, jira.baseurl and others are also not picked up.

Does this have to do with settings that are stored in the database have a higher precedence over values from jira-config.properties?

If so, it would be nice to explain this in the documentation here:  https://confluence.atlassian.com/adminjiraserver073/advanced-jira-application-configuration-861253983.html

Regards,

maurice

First I would like to thank @ATLASSIAN for making one of the most frustrating day(s) in my career!

For me solution from @greg.forties did not worked out of the box, I had to do some additional steps:

After spending couple of days struggling to do a "simple color change" in Jira by modifiing jira-config.properties and some .XML file,  I gave up, because both of the proposed solution simply does not work!
I stumbled upon on this page and I saw already that lots of people complaining on this bug that is here from 2012!?
So I tried couple of things on my own, and one of them is actually the solution on how to force Jira to pick up colors from the database:

Solution:
After you did what @greg.forties said here, make sure that you delete all of .cachedfile files from $JIRA_HOME/tmp/webresources as well.
After founding no files there, during startup, Jira will eventually pick up the values from the database. And you will be able to see the desired color that you update your database with.

Hi gregor.novak1,

Unfortunately, this has not made our short-term back backlog yet so we can not estimate when it will be fixed at this time.

Please watch the issue for updates, I will change its status as soon as we have more information that we can share about a potential fix.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

I can reproduce this error in 7.0.10

The following settings are not propaget to the the running instance

jira.lf.top.bgcolour=#54B948
jira.lf.top.separator.bgcolor=#54B948
jira.date.time.picker.use.iso8061=true

What is the plan to address this issue? It has been open more than 3 years ago?

Confirmed look and feel values not getting updated in the database from jira-config.properties.

Steps
0) Follow the Repro Steps above
1) Log into the database and check for the existence of 'jira.lf.top.bgcolour' in the propertyentry table:

jira=> select * from propertyentry where property_key='jira.lf.top.bgcolour';
 id | entity_name | entity_id | property_key | propertytype 
----+-------------+-----------+--------------+--------------
(0 rows)

2) Change the "Header Background Color" value to '#f20505' on the Look and Feel setting GUI

3) Check the database again:

 jira=> select * from propertyentry where property_key='jira.lf.top.bgcolour';
  id   |   entity_name   | entity_id |     property_key     | propertytype 
-------+-----------------+-----------+----------------------+--------------
 10602 | jira.properties |         1 | jira.lf.top.bgcolour |            5
(1 row)

4) The value for 'jira.lf.top.bgcolour' is store in the propertystring table:

jira=> select * from propertystring where id=(select id from propertyentry where property_key='jira.lf.top.bgcolour');
  id   | propertyvalue 
-------+---------------
 10602 | #f20505
(1 row)

Workarounds:

• Run UPDATE statements against the database directly, followed by a Jira restart. Something like this:

  jira=> UPDATE propertystring SET propertyvalue='#ffffff' where id=(select id from propertyentry where property_key='jira.lf.top.bgcolour') ;
  UPDATE 1
  jira=> select * from propertystring where id=(select id from propertyentry where property_key='jira.lf.top.bgcolour');
    id   | propertyvalue 
  -------+---------------
   10602 | #ffffff
  (1 row)
  

• Use the Jira REST API. This is the officially recommended workaround. Here's someone else with the same problem, and how he solved it:

https://answers.atlassian.com/questions/220540/automating-the-look-and-feel-of-jira

The behavior I'm seeing is the same as Tony Atkins described above. It only seems to apply to some settings. For example, the 'jira.lf.gadget.color1' custom property works, however none of the other 'jira.lf.*' properties seem to be applied.

Repro Steps:
1) install fresh atlassian-jira-6.4.tar.gz
2) place jira-properties.config with look and feel properties (above) in /home/jira
3) restart jira
4) run through the Jira web gui setup wizard
5) you are dropped at the jira dashboard, which still has the default colors (except for jira.lf.gadget.color1):

6) the look and feel setting page, however show the correct colors as defined by jira-properties.config:

7) restart jira and repeat steps 5 and 6
8) same results - restarting jira has no effect

Other Notes:

• changing the color via the Look and Feel settings page works
• clicking on a color on the Look and Feel settings page and clicking the Update button without changing the color's value does NOT change colors

Further Thoughts:
I suspect that the look and feel settings that are not getting updated properly actually live in the database, and that the code that handles processing jira-properties.config is not updating the values in the database.

Is it only look and feel that get missed? If there are other configs then this is more than Trivial!

I can still reproduce this is Jira 6.4.

root@packer-debian-7:/home/jira# cat jira-config.properties 
# This file used to override advanced jira properties.
# Syntax:
# <property-name> = <value>
#
# A full list of property names and default values can be seen in:
# <jira-application-dir>/WEB-INF/classes/jpm.xml   
jira.home = /home/jira
jira.lf.top.hilightcolour = #76c748
jira.lf.top.textcolour = #fff426
jira.lf.top.separator.bgcolor = #329441
jira.lf.text.headingcolour = #292929
jira.lf.top.bgcolour = #169e2b
jira.lf.menu.bgcolour = #f20505
jira.lf.hero.button.text.colour = #ffffff
jira.lf.hero.button.base.bg.colour = #ff6b6b
jira.lf.top.texthilightcolour = #f0f0f0
jira.lf.text.linkcolour = #3b73af
jira.lf.gadget.color1 = #169e2b
jira.lf.text.activelinkcolour = #3b73af
jira.lf.menu.textcolour = #ffffff

Added to backlog due to it being really visible and because clip was yelling at me about it :/

I have just verified this in our testing of the QA instance of our support site for the upgrade to JIRA 5.2, and with a standalone instance of JIRA 5.2.

All of the colors and display settings entered in the jira-config.properties file are loaded and appear in the interface, but are not applied to the live settings.

Try using these settings in your jira-config.properties file:

jira.lf.top.bgcolour =  #ff0000
jira.lf.top.separator.bgcolor = #ff0000
jira.lf.menu.bgcolour = #ff6600
jira.lf.text.linkcolour = #6600ff

The colors will appear in the "Look and Feel" administrative panel...

...but the defaults are still what appears in the actual header.

With that, you should be able to reproduce the problem and debug further.