-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
10.92
-
3
-
Severity 3 - Minor
-
No
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
- Login
- Observe below reports for the labels 'Planned' vs 'Committed'
- Sprint Coaching
- Sprint Metrics
- Sprint status
- Points Planned vs Points Accepted
- 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
- relates to
-
JIRAALIGN-3992 Planned vs. Earned Velocity report displays incorrect Planned velocity for sprint value
-
- Closed
-
-
ALIGNSP-8797 You do not have permission to view this issue
-
ALIGNSP-12558 You do not have permission to view this issue
- is connected to
-
JARDA-208 Failed to load
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