-
Type:
Bug
-
Resolution: Not a bug
-
Priority:
Low
-
None
-
Affects Version/s: 10.3.0
-
Component/s: System Administration - Look and Feel
-
None
-
10.03
-
Severity 3 - Minor
Issue Summary
This is reproducible on Data Center: yes
The "Look and Feel" was updated including the “Header - background colour“ for 9.12.x and after upgrade to Jira 10.3.0 the “Header - background colour“ is missing the "Revert" button.
Steps to Reproduce
- Install Jira 9.12.x
- Under "System > Look and Feel" change the color for “Header - background colour“
- Ensure the revert button is highlighted
- Upgrade the Jira to 10.3.0
- After successful upgrade check "System > Look and Feel" and look for “Header - background colour“
- The "Revert" button would be missing.
Expected Results
Visible revert button to revert back to the original color
Actual Results
The revert button is missing as observed in the screenshot below
2024-12-05 19:29:55,816+0530 Caesium-1-1 INFO ServiceRunner [c.a.upgrade.core.DefaultUpgradeTaskFactoryProcessor] Upgrade task [factory=host,buildNumber=10020000] completed in 45 milliseconds 2024-12-05 19:29:55,816+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] Start of the cleanup the old defaults from DB so new defaults can be applied 2024-12-05 19:29:55,817+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The value of 'jira.lf.top.bgcolour' is CUSTOM (#ffffff), so it will be left as it was. 2024-12-05 19:29:55,818+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The value of 'jira.lf.top.hilightcolour' is CUSTOM (#36739e), so it will be left as it was. 2024-12-05 19:29:55,818+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The value of 'jira.lf.top.textcolour' is CUSTOM (#292929), so it will be left as it was. 2024-12-05 19:29:55,819+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The value of 'jira.lf.top.texthilightcolour' is CUSTOM (#ffffff), so it will be left as it was. 2024-12-05 19:29:55,819+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The value of 'jira.lf.top.separator.bgcolor' is CUSTOM (#2d404d), so it will be left as it was. 2024-12-05 19:29:55,819+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The value of 'jira.lf.menu.textcolour' is CUSTOM (#ffffff), so it will be left as it was. 2024-12-05 19:29:55,820+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The value of 'jira.lf.menu.bgcolour' is CUSTOM (#36739e), so it will be left as it was. 2024-12-05 19:29:55,820+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The property 'jira.lf.menu.separator' is not set in DB, means it is default. 2024-12-05 19:29:55,821+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The property 'jira.lf.text.headingcolour' is not set in DB, means it is default. 2024-12-05 19:29:55,821+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The property 'jira.lf.text.linkcolour' is not set in DB, means it is default. 2024-12-05 19:29:55,821+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The property 'jira.lf.text.activelinkcolour' is not set in DB, means it is default. 2024-12-05 19:29:55,821+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The value of 'jira.lf.hero.button.text.colour' is CUSTOM (#ffffff), so it will be left as it was. 2024-12-05 19:29:55,822+0530 Caesium-1-1 WARN ServiceRunner [c.a.j.upgrade.tasks.UpgradeTask_Build10020002] The value of 'jira.lf.hero.button.base.bg.colour' is CUSTOM (#418bc0), so it will be left as it was.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
