We base our plans on original and remaining hour estimations. Portfolio does it's capacity-calculations based on the original estimate, not the remaining estimate.
For us, this leads to the following problem:
A story doesn't get finished within a sprint and therefore moves on to the next sprint. the Original estimate was e.g. 10h. During the last sprint 6 hours of work were done, leaving 4 hours of remaining ours (the remaining Estimate value). Portfolio now calculates the full 10 hours of work in the following sprint despite the assignee only will need 4. This is at least not my expected behaviour.
I thought this was misunderstanding on my end, but it is starting to look like a bug. My Epic is ongoing since March and supposed to end in 2 weeks. Portfolio keeps showing it as starting today and using not the remaining, but ALL the estimate, which basically makes the epic end in June.
This is really bad in my opinion as the idea as we signed with Portfolio was to get an Executive overview of the epics so we know if we are on track or not. Will someone from Jira answer this?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...
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