Priority image not updating in JIRA 7.13 from svg to png

[Dawn Fama]

We recently upgraded JIRA from 6.4 to 7.13.  The team doesn't like the arrow icons for high, medium, and low priorities.  They prefer the colored initials H, M, L.  When I try to update the priority icons to use the png files after selecting update, Jira defaults back to the svg icon.  I am the Jira admin so I'm not sure why this is not taking. 

Thank you for any support.

[Andy Heinzer · Accepted solution]

How exactly are you trying to update those icons?

Are you following the steps in How to upload Custom Priority Icons in Jira?  Or using some other method?

If you're following that KB, you will either need to refer to an external URL where those files are stored, or place your png files into the $JIRAINSTALL/atlassian-jira/images/icons/

If you select the latter option, you should then just be able to refer to these by their path of /images/icons/filename.png

I did notice that if you are selecting the default options by clicking on a visible icon, those filenames appear to be png, but the file being used by Jira appears to be svg.  It looks like the default icons have both formats (png and svg) located in that directory.   I don't believe you would need to use svg for your file format here.  In my testing png works just fine by itself. 

However I'm concerned that if you're removing the default priority files and trying to replace them with files by the same names, you might be circumventing the way that icon picker menu works in Jira.   It might be best to avoid that method and stick to trying to follow the KB steps instead.

[Dawn Fama]

Thank you Andrew,

I actually copied the old style png icon from our older instance of JIRA that had the letters for priorities and when I add it to the directory, JIRA just keeps reverting it back to svg.  It refuses to use the png style.  Also, we do not have an image hosting site so I cannot use the URL method.  I was able to do this in the past.  I'm not sure if it is a permissions issue with 2016 server where JIRA is installed.

[Andy Heinzer]

Ah, yeah, that is what I was suspecting.  Instead of trying to overwrite the default priority icon names like blocker.png, high.png, highest.png, medium.png, low.png, etc, try giving each of your own custom icons their own unique names, like H.png, M.png, and L.png.   Basically try using different names to the system defaults.

If you do it this way, and then copy your custom png files directly to the $JIRAINSTALL/atlassian-jira/images/icon/ folder you can then go into Jira's System admin page, more specifically /secure/admin/ViewPriorities.jspa

On this page, I'd then recommend editing the icon for each of these and specifying the "Icon URL" for each of these as "/images/icon/H.png" for High as an example and then click the Update button on that page.

I'm thinking that by having overwritten the default filenames, Jira is trying to be clever and utilize the svg files that also exist in that directly.  This is only happening for those 5-6 default priorities.   I haven't been able to make it do that when using a custom filename like H.png.

This ability to customize priority icons in Jira wasn't something that was directly supported in older versions of Jira.   So I'm betting that your work-around was one way to make this work in Jira in older version.  But in at least 7.12 and higher, Jira can now accept custom icons for priorities.  I hope this helps.

[Dawn Fama]

BINGO!  Thank you Andrew, your suggestion worked like a charm!