You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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]