-
Suggestion
-
Resolution: Unresolved
-
0
-
2
-
NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding suggestion.
Progress Stories In Backlog are not marked in red when tracking exceeds the original estimation
In the first versions of the JIRA portfolio plugin when in a Story or Epic the tracking hours exceed the original estimation the progress bar was labeled/marked in red . Now seems this feature is not available . (Or at least I'm not able to see this now)
In our company (Ebay Enterprise) this is a derired feature .
It is possible to fix this ? or at least provide a way to configure this?
- is related to
-
- Gathering Interest
[JRACLOUD-89786] Show progress of Stories in Backlog as red when tracking exceeds the original estimation
Hi,
We are facing the same issue. As some of our projects are executed with a time-based estimation, it would be useful to see at a glance when tracking exceeds the original estimation.
daria
added a comment - To me it make sense to have a % of the progress at a epic level (that is calculated based on the child completed user stories) but at a story level I don't see much value in having a progress bar if it is not time based. As it will always be either grey or green (not started or completed).
I am a product owner and before it was really useful to be able to quickly see which tasks went over estimated time so that I could identify easily the features that went overbudget.
I used to review the tasks that had a red bar with the team in order to refine the estimates and get more accurate in future features.
daria
added a comment - To me it make sense to have a % of the progress at a epic level (that is calculated based on the child completed user stories) but at a story level I don't see much value in having a progress bar if it is not time based. As it will always be either grey or green (not started or completed).
I am a product owner and before it was really useful to be able to quickly see which tasks went over estimated time so that I could identify easily the features that went overbudget.
I used to review the tasks that had a red bar with the team in order to refine the estimates and get more accurate in future features. Hi, this has been a conscious change from the former "Time spent" column to the "Progress" column we have right now. The challenge with the previous model was that it did not give any indication of what is still missing. Time spent was compared against the estimate in the Portfolio backlog. If people logged time but extended the remaining estimate, it did not reflect in Portfolio. Thus, we changed this metric to focus on "how far along are we actually with this?" (here are details of how this is calculated: https://confluence.atlassian.com/display/JIRAPortfolio/Status+and+Progress+Tracking ) Yet, this calculation method means progress can never go >100% (which is intuitive for progress, I can't be more than done). previously the meaning was "how much of the originally estimated time did we already spend" (this can go above 100%, and Portfolio highlighted it in red above the 100%). Also, we needed to find a solution that works for all planning methods, for example when using story points, we don't typically have any indication on how much effort is actually spent on an issue.
All that said on the background of the change, could you provide some background on why this feature would be needed, and who looks at it in which way? The reason I'm asking is that when we made this change, we thought that the information on whether I spent more or less than estimated is of course good and valid as well, but probably could be depicted in a better way rather than as part of the progress bar.
Hi everyone,
Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team - Jira Cloud Product Management