Atlassian Update – 20 Jan 2020 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. It's been a couple of months since it was first noticed in Jira 8. During that time, it has collected very few votes, watchers and support cases. Because of this and also due to the minor severity of it, it is very low on our priority list and we will not fix it the foreseeable future. That's why we're resolving it as Won't Fix. Although we're aware that this issue is still important to those of you affected by it, we want to manage expectations towards our bug fix plans in a transparent and realistic manner. We do our best to prioritise issues that have high and critical impact which we assess based on several different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communication. We will continue to watch this issue for further updates, so please feel free to share your feedback in the comments. Thank you, Jira Server Bug Fix Team