Issue:
Portfolio tells me that I have 14 unestimated tickets in one sprint in the capacity view of a teams sprint. But I can not figure out, which tickets are unestimated. See first pic
Checks till now:
Version:
we are currently using the following versions. An update is in planning.
----------------------------------------------------
Hi @Christian Huss,
As per your reply:
Unfortunately, all Standard issue types have Story point estimations.
Only the sub-tasks do not have story points. Is portfolio expecting a story point estimation also on sub-tasks?
Can I turn this off somewhere?
You are doing this the way it should be done. Estimating on standard issue types and not on sub-tasks is the way to properly run estimations.
I am not aware of a way to include sub-tasks but exclude story points from the sprint statistic. If you don't use the sub-tasks for estimation, you might maybe consider excluding them all together from your plan.
Plan settings > Exclusion rules > exclude issue type sub-task
I haven't been able to test that approach as I don't have test data at my disposal. But you could try without the risk of losing information.
If that doesn't work - don't bother. I'm sure you have all the processes in place to not start a sprint without unestimated issues in place - I guess that's why you ask the question probably. And the most important thing: all estimated issues ARE counted to calculate the load % of your sprints.
Hello @Walter Buggenhout
I could not find the Plan settings > Exclusion Rules entry. Maybe I do not have the correct version.
I will ignore the "unestimated issues" for the moment.
Thank you very much for your help!
Regards Christian
Hello @Walter Buggenhout
Thank you for your answer.
Unfortunately, all Standard issue types have Story point estimations.
Only the sub-tasks do not have story points. Is portfolio expecting a story point estimation also on sub-tasks?
Can I turn this off somewhere?
Thanks & Regards
Christian
Hello Ahmed,
Unfortunately, I still have the same issue.
We are just ignoring the field now as we could not figure out where the missing estimations are coming from.