Combining rank and priority is indeed confusing, since the priority field can contradict the rank. In most agile scenarios it is outright pointless. Multiple tickets can have the same priority but only one rank, so rank is more precise and useful anyway.

I found that I can enter a data URL as the image on the Priority definition, which helped a ton since I don't have filesystem access on our Jira server. 

data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw== 

Would be good to do this in Cloud too.

If this is fixed in server, will it be fixed for cloud as well. Do I need to raise this as a separate ticket?

I hope Atlassian could quickly prioritized this function...

Another workaround: https://confluence.atlassian.com/jirakb/how-to-hide-priority-icon-in-agile-board-779160907.html.

I found that on community: https://community.atlassian.com/t5/Jira-questions/Jira-Hide-Priority-field-from-list-views-and-cards/qaq-p/622226

It would be great to generally manage "default" fields like priority or epics rather than only being able to manage "extra" fields on cards, both in backlog as well as active sprint/kanban board.

When the backlog and boards are already prioritized in order, having another priority icon is redundant, conflicting, confusing, and difficult to maintain. The priority icon seems to be a legacy of the old heavy Jira workflows and no longer is needed in the new agile design.

Daniel,

Attempted to put your CSS above in our Announcement Banner but it just shows it as text in the banner

<style type="text/css">
.ghx-priority

</style>

My need is to replace the standard Priority field with a Custom Severity field; so requiring general configuration of the Plan View columns.