Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11735

Closing and Reopening Estimates Issues Incorrectly Modifies Velocity in Version Report

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • 6.3.13.0, 6.6.41, 6.6.51, 7.1.0, 7.2.0, 7.3.0, 7.2.2
    • Reports
    • 6.03
    • 14
    • Severity 2 - Major
    • 8
    • Hide
      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:

      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

      Show
      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

      Description
      By transitioning an estimated issue from a closed to open status multiple times, the Agile Version Report will continuously move the projected velocity for the Version. The estimated release becomes closer and closer the more an issue is transitioned from open to closed and back.

      Steps to Reproduce

      1. Install JIRA+Agile
      2. Create 'Sample Scrum Project' Agile project
      3. Open Version Report, switch to 'Version 2.0'
      4. Transition issue SSP-19 from Done to In Progress and back
      5. Reload Version Report

      When first opening the Version Report, we can see that the estimated release date is ~March 5th:

      Here we've moved SSP-19 to In Progress:

      After transitioning SSP-19 to Done, we can see that the estimated release has bumped up to ~February 23rd:

      Transitioning SSP-19 to In Progress and back to Done once more, we can see that the estimated release date is now Feb 18th:

        1. VersionReport1.png
          VersionReport1.png
          148 kB
        2. VersionReport2.png
          VersionReport2.png
          118 kB
        3. VersionReport3.png
          VersionReport3.png
          149 kB
        4. VersionReport4.png
          VersionReport4.png
          148 kB

              Unassigned Unassigned
              scovey Shanye
              Votes:
              59 Vote for this issue
              Watchers:
              56 Start watching this issue

                Created:
                Updated: