How to disable com.atlassian.jira.darkfeature.CommonHeader

hi.

in just installed new 6.0.

now my header is completely messed up..

i enabled com.atlassian.jira.darkfeature.CommonHeader in jira 5.x and after installing 6.0 it looks terrible.

i want to revert the dark feature from previous install. where can i do so?

the key "jira.enabled.dark.features" is empty but i got no clue why the header is broken

3 answers

also the dashboar gadgets seem to be messing up...any context i.e. administration Cog will show the menu places behind gadgets...makes it unable to select some entries.. :(

even if i disable the header on that url "/secure/admin/SiteDarkFeatures!Default.jspa" it remains set

JIRA 6 now got the new look and feel feature, the design is very different from JIRA 5.x.

See the release note:

https://confluence.atlassian.com/display/JIRA/JIRA+6.0+Release+Notes

If you using the dark feature in JIRA 5.x, I believe you add the propery:

com.atlassian.jira.darkfeature.CommonHeader

into your Advanced settings. Try to delete it from Administration » System » General Configuration » Advanced Settings and see it it hleps.

Or maybe give it a try to delete the dark feature in JIRA 5 first, then do upgrade again.

thanks for the comment. i already did this befor...

the problem was that the header was totally damaged after upgrading to 6.0 so my first thought was that maybe activating the commonHeader in 5.2.11 messes up the new design that is shipped in 6.0

it wasn't. even if i disabled the commonHeader it won't help. so the resolution here was...

in Jira 6.0 the file "/opt/atlassian/jira/atlassian-jira/ui/aui-layout/issue-view.less"

differs completely to previous version.

i have made some modifications to that file to let "Issue Security Vaues" appear bold and red in issue view...that worked with any other earlier version of JIRA

so during the upgrade process this file was put in "5.2.11-modifications.txt" like all other configurationfiles and images that we ran before...so copying all previous modifcations into JIRA 6.0 installation dir was my mistake.

i just copied issue-view.less (contains #security-val .note by default now) from a fresh 6.0 into the damaged instance fixed my problem

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Jira

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,088 views 0 8
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you