-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
1000.5.0 Cloud, 7.2.1, 7.2.2, 7.2.3, 7.7.0, 7.6.2, 9.4.9
-
7.02
-
33
-
Severity 3 - Minor
-
7
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
Steps to Reproduce
- Administration > Issues > Issue Types
- Edit any issue type (Eg: Task)
- select image
- Choose any icon from or upload a new avatar
- Update
- Check Issue type schemes page (https:// {instance url}
.atlassian.net/secure/admin/ManageIssueTypeSchemes!default.jspa), the avatar is not changing.
Expected Results
Avatars should be changed after updated.
Actual Results
Avatars did not update on some pages.
Note
- This issue also happens on Create Issue screen and Edit Issue screen.
- View Issue screen and Issue Navigator are showing the correct avatar.
- Re-indexing does not fix the issue
Workaround
Restart JIRA for the icons to be updated
- relates to
-
-
- Closed
-
-
-
- Gathering Impact
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
[JRASERVER-60897] Changing of Issue Type Icons Do Not Apply to Screens and Administration Page
At first I tried everything without success. The new icon was appearing everywhere except the Kanban Board. However, I discovered that I had the board swimlanes grouped by Stories (which is the icon I changed). I reset the board to group by epic, then changed it back to stories and now the new icon is displaying. 
This has been open since 2016? What a joke. Atlassian can't even fix icon display. That says a lot about the UI/UX skills behind the development teams.
Hello,
There is another workaround that is to update the issue type scheme => You can change the issuetype order and save and then roll back the original order.
This will update the issuetype with the new avatar.
PS : Tested with Jira 8.3.4
Best Regards,
-g.
This one affected us last night with the Bug icon. We are running 8.5.1.
The proposed workaround to reorder the issuetypes in the issuetypes scheme resulted in a partial fix.
On the create screen if Bug was selected we'd see the old icon, if Story was selected Bug would show the correct/new icon. Looking a the resources being called in each scenario they were different.
/secure/viewavatar?size=xsmall&avatarId=10300&avatarType=issuetype & /secure/viewavatar?size=xsmall&avatarId=10303&avatarType=issuetype respectively.
We did a rolling restart and now we are only shown the correct icon and in both the above locations are returned
/secure/viewavatar?size=xsmall&avatarId=10303&avatarType=issuetype
Hello Colleges, This is a very annoying bug. Ho wouldn't be tired of explaining the users you did the change already.
Workaround that works for me:
is to edit the Issue type screen scheme > shuffle the issue types around > and save
Let me know if worked as well for you.
Br,
Tomas / tomaskondelka.com
Bug is also present in 7.13.5. We found the following workaround:
- Remove the issue type from the issue type scheme
- Save the issue type scheme
- When now opening again the issue type scheme the icon has changed to the new one. Drag again the issue type to the left column and save the issue type scheme.
The issue icon is now displayed correctly for that single issue type scheme. Unfortunately this has to be done for every single issue type scheme. The icon is also changed when the Jira service is restarted.
This bug is annoying to power users and confusing to the team. Visual distinction of icons helps us a lot with coaching our process. Can you please bump up priority?
The work around I know of is the icon will show up after a Jira service restart. I'm sure that's not a great work around, but if you can move your icon changes to the end of day and restart the server in the middle of the night that should work.
Bug is still open on dedicated server v7.13.0#713000-sha1:fbf4068. Fix this please or provide a workaround.
+1