-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 7.0.0-OD-07, 7.0.0, 7.0.5, 7.1.0, 7.2.0, 7.2.4, 7.2.6, 7.10.2, 8.5.1
-
Component/s: System Administration - Look and Feel
-
7
-
14
-
Severity 3 - Minor
-
0
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
As mentioned at Change Site Logo, user should be able to revert the color scheme if they don't like it. Once the logo is changed, clicking Undo button does not revert the color scheme.
We'll automatically change the colour scheme to match your logo, and if you like it, there's nothing more you need to do. We'll give you the option to undo the colour change with a single click, just in case you're not happy with the result.
Steps to reproduce
- Go to Look and Feel configuration
- Change the logo with different background color (othen than blue)
- The color scheme will be changed to match the logo's color
- There will be notification message to offer users to Undo it
- We've updated the color scheme to match your logo. Undo.
- Click on Undo button
Expected Result
The color scheme should be reverted back
Current Result
The color scheme remains the same
NOTES:
in testing the custom color code applied that is changed when the logo is uploaded cannot be reset to the same value:
exe: if you set Header background color to #ff03ee and it is reset when the logo is uploaded reseting it to #ff03ee will not change the color BUT any other color i.e. #ff03ed or #ff03ef will allocate the change.
Workaround:
- Note all custom color codes applied manually
- i.e.#ff03ee
- Select Reset to default and all jira default colors are applied and logo removed
- Upload the Custom Site Logo While Default colors are set
- Do not select the undo option when automatic color change is applied
- Manually re-apply custom color values to the desired values you noted initially
- relates to
-
JRACLOUD-45829 Unable to revert the color scheme after changing logo
-
- Closed
-
- blocks
-
GHS-168875 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...