I am working through the process of upgrading our Jira instances, We have a staging server, production server and I am working with containers to test configurations and document a migration and upgrade deployment.
Is there a file I can change in the installation that would allow me to label the different instances. Our staging and containers use the same beta database that is refreshed from production weekly so any changes are wiped out and would carry between all containers.
Ideally a heading that identified the server and distro.
Thanks Steve
Hi,
I understand you are looking to customize the look between a product Jira site and that of a development or staging instance. For most setups, I would first want to make sure that the admin is aware of the Look and Feel page directly. That link cites the documentation on how you can customize the logo, site title, favicon, etc. Personally, I feel like using this page in the Jira admin panel is the best way to customize this. There is a fun feature where you upload your own custom logo and Jira will automatically change its color schemes to more closely match the colors in your logo.
For example I made two logos of different colors:
Uploading one of these via that panel is a good way to distinguish between the two sites in most cases.
But I understand that you might not be looking for this specific solution. Given what you have stated about cloning the production database to use in the staging/dev instance, I believe it could clone this setting.
While investigating this I came across a method that I think could help your use case here.
This way the logo change is not being stored to the database, but rather to the installation directory itself. Perhaps this method can help in some ways to show you which server you are on. The drawback of this approach is that I don't think this is a supported way to change that icon for one, and two, it doesn't benefit from using the logo upload which can automatically change other colors to match your logo.
I hope this helps.
Andy
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.