Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Time Tracking in Greenhopper

I am estimating in story points and time tracking in hours. I want the remaining hours field in the user story to be the total of the remaining hours in the sub-tasks. But I cannot enter sub-task remaining hours in Plan mode, only in Work mode. The user story is not available in Work mode until I start the sprint. But if I start the sprint without remaining hours in the user stories, the ideal burn-down chart is not plotted.

It's a Catch-22 situation. The only way I can get the initial burn-down plotted is to put guesswork hours remaining nto the user stories, whereas they should be the sum of the sub-task hours remaining. But I can't enter the sub-tasks hours remaining until I've started the sprint.

Surely I should be able to enter sub-task hours remaining in Plan mode?

Jira 5.2.5 Greenhopper 6.1.2

2 answers

1 accepted

1 vote
Answer accepted

You cannot edit the Sub-tasks' remaining estimates directly in the Plan mode, but you should be able to edit the field in the Sub-task's Edit Screen (click Actions > Edit in the Sub-tasks section of the Story's detail pane). Would that be a suitable workaround for you?

I can't speak for the original poster, but given the workflow we're talking about, it's an inefficient workaround at best.

My team have basically 2 hours for our Sprint Planning meeting every two weeks and we have to get through a lot of stories... selecting which stories to include, then breaking down with sub-tasks how we'll approach each one. With an average of 30-35 stories, half of which need to be broken down into 2-5 sub-tasks each, I figure there are ~50 or so times we need to enter a sub-task remaining estimate during the 60-75 minutes we have left after agreeing on the sprint contents.

You can see how the inefficiency can multiply quickly when its core to the workflow...

Maybe there's just a better way to organize our workflow that aligns with the software design?

I asked the very same question on the Configurating Estimation and Tracking page and would love to hear an answer on this!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Jira Cloud Performance Improvements

Hello everyone, I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extr...

146 views 1 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you