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

    • 6.03
    • 13
    • Severity 2 - Major
    • 5
    • 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

          Form Name

            [JSWSERVER-11735] Closing and Reopening Estimates Issues Incorrectly Modifies Velocity in Version Report

            romain bonnet added a comment -

            Any workaround?

            romain bonnet added a comment - Any workaround?

            Piotr Wegert added a comment -

            Are you kidding me? First the Sprint Report (https://jira.atlassian.com/browse/JSWSERVER-14984) and now this? Another crucial report is fundamentally broken. It seems like whatever metric/report we want to use there is an underlying flaw that makes it useless.

            Piotr Wegert added a comment - Are you kidding me? First the Sprint Report ( https://jira.atlassian.com/browse/JSWSERVER-14984 ) and now this? Another crucial report is fundamentally broken. It seems like whatever metric/report we want to use there is an underlying flaw that makes it useless.

            Lee Minich added a comment -

            This bug is still present in the current cloud-based release.

            This seemed to occur after adding some additional tasks, adding them to the version, and removing a large (250 SP) placeholder task.

            The Version Report was the primary tool management was using / visualizing project progress, and now it is rendered useless!

            Lee Minich added a comment - This bug is still present in the current cloud-based release. This seemed to occur after adding some additional tasks, adding them to the version, and removing a large (250 SP) placeholder task. The Version Report was the primary tool management was using / visualizing project progress, and now it is rendered useless!

            Till Kothe added a comment -

            I have not tried to replicate this, but does anybody know if this issue is also present in current version of Jira cloud?

            Till Kothe added a comment - I have not tried to replicate this, but does anybody know if this issue is also present in current version of Jira cloud?

            Joe Rutledge added a comment -

            Since it seems a fix is a long time in coming, is there any work-around for this issue? Anything that can be done within our workflow, perhaps?

            Joe Rutledge added a comment - Since it seems a fix is a long time in coming, is there any work-around for this issue? Anything that can be done within our workflow, perhaps?

            Eric Seong added a comment -

            +1 to raise the priority and get this issue to be addressed as soon as possible!

            Eric Seong added a comment - +1 to raise the priority and get this issue to be addressed as soon as possible!

            Greg Reynolds added a comment - - edited

            It is difficult to believe that this is considered only a "medium" priority issue and that it has remained unaddressed for so long. We depend on these reports to forecast our end dates and ensure we are on schedule. For a planning tool to be unreliable at forecasting and planning is unacceptable. This work has to be done painfully by hand. My faith in Atlassian products continues to erode.  

            The Release Burndown report won't even forecast until you have three sprints of actuals recorded! I'm not confident it doesn't have similar bugs.

            Greg Reynolds added a comment - - edited It is difficult to believe that this is considered only a "medium" priority issue and that it has remained unaddressed for so long. We depend on these reports to forecast our end dates and ensure we are on schedule. For a planning tool to be unreliable at forecasting and planning is unacceptable. This work has to be done painfully by hand. My faith in Atlassian products continues to erode.   The Release Burndown report won't even forecast until you have three sprints of actuals recorded! I'm not confident it doesn't have similar bugs.

            fredric.karlsson2084614369 added a comment -

            As reported by other users, this is a vital report for our organisation. As it stands, JIRA is not a suitable product for our agile organisation.

            fredric.karlsson2084614369 added a comment - As reported by other users, this is a vital report for our organisation. As it stands, JIRA is not a suitable product for our agile organisation.

            Joel Robinson added a comment -

            I'm just about to start rolling out Version Reports in a new organization and I'm concerned that this bug will make it difficult for stakeholders to take our forecasts seriously.  WTF Atlassian? Over 2 years to fix a bug that erodes the credibility of such a fundamental report?

            Joel Robinson added a comment - I'm just about to start rolling out Version Reports in a new organization and I'm concerned that this bug will make it difficult for stakeholders to take our forecasts seriously.  WTF Atlassian? Over 2 years to fix a bug that erodes the credibility of such a fundamental report?

            andrew.beck added a comment -

            As others have mentioned, this bug is forecasting erroneous completion dates which defeat the purpose of the Version report and the product.  Without an accurate estimate we cannot use this tool for forecasting project dates to our business units which reduces our credibility and management confidence in our team.   How hard can this be to fix? 

            andrew.beck added a comment - As others have mentioned, this bug is forecasting erroneous completion dates which defeat the purpose of the Version report and the product.  Without an accurate estimate we cannot use this tool for forecasting project dates to our business units which reduces our credibility and management confidence in our team.   How hard can this be to fix? 

              Unassigned Unassigned
              scovey Shayne
              Affected customers:
              59 This affects my team
              Watchers:
              56 Start watching this issue

                Created:
                Updated: