nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

unestimated issues in Sprint capacity view

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

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

Comments

Walter Buggenhout

Hi @Christian Huss,

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

Christian Huss

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

Walter Buggenhout

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.

Christian Huss

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

Ahmed Saleh

I am running into the same issue, Did you find a way around this @Christian Huss ?

Christian Huss

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

advanced-roadmaps