Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

estimated sub tasks are still appearing as NON ESTIMATED while starting the sprint

Nishant March 29, 2022

time tracking is enabled in Sub Tasks in Jira and sub task is also estimated (in Hours), yet while starting the sprint i get a dialog box which says that the sub tasks are not estimated. While the User Stories [Tasks] are accepted as ESTIMATED because story points are provided in stories and not Hours like in Sub Tasks.

this is not a correct behavior and provides a wrong picture. Please provide me the resolution of how i can have the sub tasks account to the time tracking in the right manner.

1 answer

1 accepted

1 vote
Answer accepted
Haddon Fisher
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 29, 2022

Your scrum board can be configured to use "Story Points" or "Time Tracking" but it's one or the other; you cannot use both at once in the same place.

If you are estimating your stories and tasks in points, then it sounds like your board is configured to use points; this would result in your sub-tasks, whose "story points" field is empty, to be treated as unestimated.

I would say most best practices would say:

  • You should not be estimating sub-task level issues
  • You should not be converting time into story points or visa versa

But, if you are OK ignoring these, you could build an automation rule which sets the "Story Points" field based on the value of one of the time tracking fields. This would show both standard and sub-task estimates in the same metric without you giving up time tracking for your sub-tasks.

Nishant March 31, 2022

thanks for a detailed answer, I think thats the limitation in Jira, as it doesnt allow the conversion of SubTasks estimate and story points, ideally would have been great if Same can be linked either ways, because that could have presented a clearer picture to Sprint and also the other metrics like burndown chart etc. Like it exists in other tools like Agile Central, Urban Turtle etc. 

Suggest an answer

Log in or Sign up to answer