When you come a sprint, all open stories get carried over to the next sprint. How should I handle the modification of the task "Original Estimate" and "Remaining Estimate"? For example, from the previous sprint, the "Original Estimate" was 10 hours and the "Remaining Estimate" was 4. If the task gets carried over to the next sprint, should you update the "Original Estimate" to be reflective of the remaining hours left on the task?
Depending on the team leads, we either
1) Reset the original estimate but it may not be equal to the remaining estimate since the cost might be greater to continue to work.
2) Clone the issue so you can close off the original issue and start using the cloned copy.
In any case we want the work estimate never to be greater than what was estimated for the sprint.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs