-
Bug
-
Resolution: Fixed
-
Highest
-
10.105.3, 10.104.2
-
2
-
Severity 3 - Minor
-
No
Issue Summary
In Feature details panel and team room, progress bar for an Accepted Story with all Tasks done shows 0% when all tasks have 0 hours logged.
Steps to Reproduce
- Progress bar setting is set to Progress by Story Point
- Have a Story with a parent Feature
- Add tasks to the story in Done status - they will get added with 0 hours
- Change Story status to 'Accepted'
- Navigate to Parent Feature, expand Stories and observe the progress bar
- Navigate to Team room with this story and observer the progress bar
Expected Results
When a Story is Accepted and all the Tasks are done, it should show complete progress despite having 0 hours logged.
Actual Results
Currently, with the above settings, it shows 0% progress.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available.
Progress by Count option can also be used and displays the progress bar correctly, please read more about it here: 10X: Configure Progress Bars
- is related to
-
-
- Closed
-
- is connected to
-
JAWM-2966 Loading...
- resolves
-
-
[JIRAALIGN-3963] Story Progress Bar for an Accepted Story with all Tasks done shows 0% when all tasks have 0 hours logged
I know there have been questions about the release timing for this issue. We are actively working on the issue now and plan to release it shortly. Since this change impacts progress bars we are doing our due diligence so we do not introduce bugs or cause confusion with how the completion of work will be displayed in the future.
I cannot provide a release date at this time, but it is under active development and review.
Hi Atlassian team, Every client is impacted by this bug, which is causing confusion for EVERY user in Align. While the severity might technically be minor they impact to user experience and confidence in Align is HUGE. Please get this fixed asap.
Do we have an update on this bug?
Several users within our Jira Align instance are getting impacted by it
Atlassian ticket: https://getsupport.atlassian.com/servicedesk/customer/portal/30/PS-91784
Submitted
Hi Atlassian team-
Is there any general idea of when this bug fix will be in production?
Appreciate any update on this. Thanks!
The fix for this issue was released in version 10.108.2.