Hi everyone,
We apologise for taking that long to revisit this issue. The estimate for resolution provided in the previous status update has been long exceeded. As Atlassian values openness, let us bring clarity to this case and explain how we currently deem the bug.
The last time we investigated it, we have decided that neither its impact nor the interest it had gathered were sufficient for us to prioritise fixing it. We have now examined it once again and reached the same conclusion. The fact that the impact and interest growth trends have remained steady since the previous evaluation only confirms that we made the right call. This and our current product priorities are the reason why we are once again deciding not to include it in our bug fix plans for the foreseeable future.
The bug will remain in the "Long term backlog" status. It denotes that while currently it is not as severe nor pervasive as other issues, it is within the cohort of bugs which are the strongest candidates for being included in the bug fix roadmap during future reevaluations of it.
We understand how disappointing this decision may be, but we hope you will appreciate our transparent approach and communication. To understand how we organise and prioritise bug fix work I encourage you to read Atlassian Server Bug Fix Policy. More importantly, if you would like to find out what the Jira team is currently focused on and has recently delivered see the following dashboards:
Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Thank you,
Pawel Drygas,
Jira Server Bug Fix Team