Why can't I upload icons for new priority, issue and workflow step entries?

[Danny At Resolute]

I have created a new workflow step (waiting) and I am creating a new priority (background). In each case I am asked to select from existing icons stored in JIRA or to give a path to some icon elsewhere. I would really like to be able to upload icons through the browser for this, just like new project icons.

I could go to the server and drop the icons in to the JIRA folder, but our infrastructure team, deeply paranoid about such things, have placed barbed wire and machine gun nests around the servers. I don't look good with bootpolish on my face and black overalls, so I won't hack in as root just to solve a simple icon upload.

Have I missed some security issue or some expected way of doing this?

[Foong · Accepted solution]

feature request:

https://jira.atlassian.com/browse/JRA-21246

[Dan Pohl]

Thank you Matt Doar.  Brilliant solution.  I suppose the only thing I'll need to be careful about is permissions.  I'll need to ensure that all future users have permissions on that image attachment in the fake issue.

[David Toussaint [Communardo]]

Hi Daniel,

No, there is just no other way of dooing it apart from dropping you image files in that folder. Sorry for that one.

Cheers, David

EDIT: I like your description of your IT department. Kindof feels familiar ;)

[David Toussaint [Communardo]]

another way would be to host you images somewhere elase and insert the URL to those images for each status/priority.

Avoids machine guns.

[Danny At Resolute]

I have responded to that suggestion over at https://jira.atlassian.com/browse/JRA-21246

All the assetts inside JIRA could be hosted externally somewhere. That means asset management and polar expeditions to find long lost icons, users having put icons inside a location where only they know the password, which they forgot, and perhaps exposure to third party advertising executives who think that your icon for "issuetype-waiting.png" should say "Eat at Joe's". Its just a bit too ad hoc.

An alternative might be to configure an external asset repository path at a system level so these 3rd party things are in a big bucket somewhere. Then each icon can be addressed relative to the path to the bucket. No spill, no mop.

This would also allow server admins to configure a different security zone around our custom icons and our own upload function to ensure only internal users have access.

[MattS]

Sneaky hack time. Upload the new icon to an issue. Go to manage the attachments on the issue and copy the URL for the icon. Then use that URL when you define the new priority.

[Danny At Resolute]

Thank you @matt-doar for your "sneaky hack" suggestion. For those running both JIRA and Confluence it leads me to a perfectly valid solution.

Create a page in confluence that is a key to your new states and priorities and what have you. This is a reasonable and stable place to store such images. You can then do as Matt suggests and use the url to the image in Confluence as the location to give to JIRA.

I would still, as an old codger with a slightly pessimistic attitude who just knows these things will go wrong, prefer for the images to be in JIRA though, with the confluence page linking to the image in JIRA.

[E]

If the Queen of England can parachute down from a helicopter to save Tim Berners-Lee and his NeXT server.....

[Danny At Resolute]

...then surely...