I found an inconsistency in showing Estimate and Remaining time in GreenHopper planning board on tasks having sub-tasks. I'm not sure whether it's a feature or a bug, but to me the behaviour is wrong and very inconvenient.
If a task has sub-tasks, Estimate field in GreenHopper shows time without sub-tasks time, but Remaining - with sub-tasks time. On Epic it shows Original Time Estimate without sub-tasks included in the tasks.
So, Estimate on Task with sub-tasks differs from Remaining.
Original Time Estimate on Epic with such task is wrong (without sub-tasks time).
Could you please advcie is there a work-around to have Original Time Estimate on Epic and Estimate on task with sub-tasks reflected correctly?
Hey there, Azat.
Check on the following explanation regarding the issue that you having here. Perhaps it will be able to shed some light:
Hi awesome community! In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs