We are stuck in a time tracking issue on jira.
We usually estimate our stories in days and later on the stories are broken down in tens of sub-tasks. Each developers again estimates each of the sub-tasks and logs time on sub-tasks
What it effectively means is that the total estimate gets over-inflated because we are counting the estimate twice (once on parent story and then again on sub-tasks).
Things get even more complicated when you run agile, and due to this the burndown get over-inflated.
What is the possible solution to our problem of double counting of estimates?
It's kind of astounding to me that this is still a problem. The closest thing I've seen resembling an answer was a comment in another thread to the effect of, "Atlassian uses the assumptions of Scrum, which means you don't include sub-tasks in estimates. This makes no sense at all to me - we don't all work in pure Scrum environments. Some of us just want a way of quickly showing the totals of all the work involved in an Epic. Atlassian, please pay attention.
There are some requests in https://jira.atlassian.com regarding the estimation in subtasks:
Some of them (last two) have some workarounds suggested in the comments, which might be helpful for your case.
Hope it helps!
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG