I've got a question from one of our project managers he has noticed that there some differences between Version workload report and Agile time etimate even tough it's the same milestone that is being measured.
ex Version Workload Report says 3180 hours while Agile says 6132 hours have anyone else noticed any diferences in their projects.
I think it is a question of interpretation. It is not good to have two definitions of what is remaining, but in a way they are both right.
My own solution is to set the remaining estimate to 0 when resolving issues (They are done, right?). Unfortunatly I found other differences that I could not explain.
I am seeing a similar problem - we have time remaining against issues in a "Reviewing" state, i.e. not "Done" - but this is not being added into the Total Time Remaining in the Version Workload Report .
I think its a straightforward bug - The Time Tracking report shows 21d 6h 25m remaining, the version workload report only 20.5d.
Greenhopper shows the correct remaining time.
We have JIRA v5.1.5.
At Atlassian, we believe in our own products – that's why we use them, even at the enterprise level. Doing so gives us first-hand experience of how they perform at scale; to do this, we monitor each ...
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