I've read several of the posts with questions on subtasks and the general complaints that it has on Jira reports when time tracking is used.
The use case:
Either way, it seems that if you use subtasks for estimation or time tracking, then your reports will be inaccurate.
Real world use case:
User Story is to Add Shiny New GUI feature:
Using Jira with this use case, where the Design, Development, and QA teams can track their time independently on the Subtasks makes it virtually impossible to have accurate reports for sprints and releases.
I know that there are other people with this issue based on looking at some of the posts already, but I haven't found a clear solution on how to handle this scenario without either sacrificing the accuracy of the reports or losing the visibility of time tracking using Subtasks.
Anyone found a way to accomplish both? [If your only answer is to not use subtasks, please keep it moving and don't waste your time or mine]
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events