Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-3128

Reports - Planned vs. Committed Story Points terminology needs to be consistent for the distinction

      Issue Summary

      Reports - Planned vs. Committed Story Points terminology needs to be consistent for the distinction. As per the article, "Stories Committed: The count of stories planned in the sprint." There are reports in Jira Align where the term "Planned" vs "Committed" is being utilized interchangeably causing confusion. 

      Steps to Reproduce

      1. Login
      2. Observe below reports for the labels 'Planned' vs 'Committed'
        1. Sprint Coaching
        2. Sprint Metrics
        3. Sprint status
        4. Points Planned vs Points Accepted
        5. Planned vs Earned Velocity

      Expected Results

      The terminology is consistent across reports

      Actual Results

      The terminology is not consistent

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        1. Screen Shot 2021-05-04 at 10.39.42 PM.png
          365 kB
          Vishwajit Vinchurkar
        2. Screen Shot 2021-05-04 at 10.40.36 PM.png
          189 kB
          Vishwajit Vinchurkar
        3. Screen Shot 2021-05-04 at 10.42.13 PM.png
          209 kB
          Vishwajit Vinchurkar
        4. Screen Shot 2021-05-04 at 10.45.11 PM.png
          150 kB
          Vishwajit Vinchurkar
        5. Screen Shot 2021-05-04 at 10.47.32 PM.png
          101 kB
          Vishwajit Vinchurkar

            [JIRAALIGN-3128] Reports - Planned vs. Committed Story Points terminology needs to be consistent for the distinction

            Don Fuller added a comment -

            Hi everyone, 

            Thank you for sharing your feedback.  

            Over the past several months, Jira Align Product and Engineering teams have reviewed over 1,000 JAC tickets in an effort to better understand the biggest problem areas, and make a concentrated effort to respond to your feedback more efficiently.

            With this renewed focus and organization, we have decided to deprioritize and close this ticket. Here are a few reasons this ticket might be getting closed:
             - The ticket had an impact score of <4 (combination of watchers, participants, votes and linked issues)
             - The bug was older than 18 months (from Oct 1, 2022) with an impact score of <=6
             - The bug was created more than 30 months ago
             - The bug was part of a component (functional area) listed for deprecation

            Moving forward, you will notice the following:
             - all existing tickets with a bug status will be addressed within the next few quarters;
             - all new tickets with a bug status will be addressed according to Atlassian's Cloud Bug Fix Policy;
             - all new and existing tickets with a suggestion status will be considered as part of our product roadmap, which will be communicated during our quarterly roadmap webinar;
             - all tickets with a won't fix status will be deprioritized.

            To elaborate on tickets with a suggestion status, we will either create new projects that address the underlying issue, or incorporate these tickets into existing projects.

            Thanks, Sam Ugulava | Sr. Product Manager

            Don Fuller added a comment - Hi everyone,  Thank you for sharing your feedback.   Over the past several months, Jira Align Product and Engineering teams have reviewed over 1,000 JAC tickets in an effort to better understand the biggest problem areas, and make a concentrated effort to respond to your feedback more efficiently. With this renewed focus and organization, we have decided to deprioritize and close this ticket. Here are a few reasons this ticket might be getting closed:  - The ticket had an impact score of <4 (combination of watchers, participants, votes and linked issues)  - The bug was older than 18 months (from Oct 1, 2022) with an impact score of <=6  - The bug was created more than 30 months ago  - The bug was part of a component (functional area) listed for deprecation Moving forward, you will notice the following:  - all existing tickets with a bug status will be addressed within the next few quarters;  - all new tickets with a bug status will be addressed according to Atlassian's Cloud Bug Fix Policy;  - all new and existing tickets with a suggestion status will be considered as part of our product roadmap, which will be communicated during our quarterly roadmap webinar;  - all tickets with a won't fix status will be deprioritized. To elaborate on tickets with a suggestion status, we will either create new projects that address the underlying issue, or incorporate these tickets into existing projects. Thanks, Sam Ugulava | Sr. Product Manager

            Kyle Clark added a comment -

            Note that there is a clarification in the help article linked in the description. Review this text, which sits above the quote that was referenced:

            "The Committed Plan: All values in this section are calculated prior to the start of the sprint. After a sprint has begun, removing a story or story points will not reduce a value."

            In our reports, this general rule applies:

            • "Committed" refers to values that measure stories that are planned PRIOR to the sprint start date.
            • "Planned" refers to values that measure stories that are planned ANYTIME in the sprint – prior, during, or after the sprint start/end dates.

            If there are any inconsistencies between a committed label and the help article's text, please let us know. Our content team is currently checking the 5 reports mentioned in this ticket to ensure labels match their explanations.

            Kyle Clark added a comment - Note that there is a clarification in the help article linked in the description. Review this text, which sits above the quote that was referenced: " The Committed Plan:  All values in this section are calculated prior to the start of the sprint. After a sprint has begun, removing a story or story points will not reduce a value. " In our reports, this general rule applies: "Committed" refers to values that measure stories that are planned PRIOR to the sprint start date. "Planned" refers to values that measure stories that are planned ANYTIME in the sprint – prior, during, or after the sprint start/end dates. If there are any inconsistencies between a committed label and the help article's text, please let us know. Our content team is currently checking the 5 reports mentioned in this ticket to ensure labels match their explanations.

              9ca9aa5ad14e Sam Tsubota
              e992016a60b0 Vishwajit Vinchurkar
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: