Closing and Reopening Estimates Issues Incorrectly Modifies Velocity in Version Report

Atlassian Update – 08 Jan 2020 Hi everyone, The bug was created more than three years ago yet it has never been triaged or updated by the development team. It's all the more glaring given the considerable interest it has gathered. Please let us apologise for the lengthy silence and explain the current status of this issue. At the moment, the team is focused on other bugs related to reporting, namely JSWSERVER-13783 and JSWSERVER-14984 . This is because these bugs have affected more customers and lead to more severe consequences. That's why we are moving this bug to 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. To better understand how Atlassian prioritises and processes bugs please see https://confluence.atlassian.com/display/Support/Atlassian+Server+Bug+Fix+Policy We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. 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 will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Jira Server Bug Fix team