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; } } }

Version report unestimated line... what is the criteria for this data?

Chris Rudram

The Version report shows an 'unestimated line'. This seems to incorporate the sub tasks for the user stories, which we don't generally estimate on. Is there a way to stop sub tasks being counted as 'unestimated' so the data here is much more clear and accurate?

Accepted answers

Andrew Grant_cwjzoc

This is a known bug which is being tracked at these locations:

https://jira.atlassian.com/browse/GHS-7154

https://jira.atlassian.com/browse/GHS-8152

Feel free to vote for it to be fixed!

The work-around at the moment is to create a new board that uses a filter to exclude all unestimatable issues/tasks/sub-tasks. Its a bit fiddly, so hopefully a fix will be coming soon.

All comments

Andrew Grant_cwjzoc

This is a known bug which is being tracked at these locations:

https://jira.atlassian.com/browse/GHS-7154

https://jira.atlassian.com/browse/GHS-8152

Feel free to vote for it to be fixed!

The work-around at the moment is to create a new board that uses a filter to exclude all unestimatable issues/tasks/sub-tasks. Its a bit fiddly, so hopefully a fix will be coming soon.

Chris Rudram

Thank you. Up voted those items.

Thom Franklin

We bulk changed all the unestimated features to the average of 4.501 points! That strange point value indicates it is not estimated, but it helps us build out the chart.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

version