Today all time (estimate, capacity etc) is displayed in the format of days and hours. If you type in 16h it will be converted to 2 days.
We only work in hours when calculating estimates and capacity etc. So this is only confusing. It would be wery nice if we could select by configuration to use format d h or only h. Seeing and working with total number of hours is more intuitive for us.
Is this only supposed to affect how time-based estimates are visualized in a record's estimate field?
Asking because days will show up in the release retrospective and the release capacity bar tool tips for "capacity remaining" & "work remaining over capacity" (messages when you hover over the release capacity bars on the feature board).
I see so many of us are asking for this functionality. Why is it the lowest priority for the company to implement a small change?
I'm not sure why this is still on the backlog. It will make a big difference for those that estimate in time and it should be a small addition to the application. Please implement this
I really wish you would reconsider this idea. Story points do not work for this. If you intergate with Jira and you want to track time in any way, then story points do not work like time. I also think this would be a fairly trivial setting to add in.
A welcome addition to the functionality in the ability to show the time measurement in hours. Certainly avoids having to take the calculator out.
Thanks
I have the same issue. I see Ron Yang provided a work around. But why would you force the user to do something that is not intuitive when you are saying the product is user friendly and intuitive.
All LOEs from our developers are provided in hours and that's how we would like to track this. It will only make your product better. Currently its confusing.
Thanks Rose for pointing me to this item.
Thanks for the note. One workaround would be to select the capacity units based on Story points (instead of Time). This would keep everything in the same configuration (without any conversions). Given this workaround, we are going to mark this as Already exists.
We don't have near-term plans to make changes in this area, but using Story points should achieve the same goal to keep things intuitive for the team.