unestimated issues in Sprint capacity view
Asked by Christian Huss:

++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:++

* I check that all tickets have story points
* In the scheduling option in portfolio, the story point filed is selected for estimation (See second pic)
* In the board option, the story point field is selected for estimation (see thrid pic)

++Version:++

we are currently using the following versions. An update is in planning.

* Jira 8.5.1
* Portfolio 3.21.0

----------------------------------------------------

![unestimated_issues.png](https://community.atlassian.com/t5/image/serverpage/image-id/120381iC834E768FD06238B/image-size/large?v=v2&px=999 "unestimated_issues.png")![scheduling.png](https://community.atlassian.com/t5/image/serverpage/image-id/120380i81A422B13227294C/image-size/large?v=v2&px=999 "scheduling.png")![estimation.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/120382i03637FBF2A8064F0/image-size/large?v=v2&px=999 "estimation.PNG")


Answers:
author: Christian Huss
body: Hello [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225)

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

comments: author: Ahmed Saleh
body: I am running into the same issue, Did you find a way around this [@Christian Huss](/t5/user/viewprofilepage/user-id/802309) ?


author: Christian Huss
body: 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.


author: Walter Buggenhout
body: Hi [@Christian Huss](/t5/user/viewprofilepage/user-id/802309),

The easiest way to figure this out, is to simply click the link **Filter issues by this sprint** as per your first screenshot.

Then, limit the hierarchy in your plan so you can only see the story level *(and optionally sub-tasks)*.

Make sure you add the **Story Points** custom field to your view. All issues that don't have an estimate are your unestimated issues:

![Screenshot 2020-12-02 at 17.32.52.png](https://community.atlassian.com/t5/image/serverpage/image-id/120408i078DDCDC7D519529/image-dimensions/586x132?v=v2 "Screenshot 2020-12-02 at 17.32.52.png")

comments: author: Walter Buggenhout
body: Hi [@Christian Huss](/t5/user/viewprofilepage/user-id/802309),

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.


author: Christian Huss
body: Hello [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225)

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


Tags: advanced-roadmaps

server