We have just finished a sprint and some tasks weren't completed in the sprint. Because of this, they've gone back into the sprint backlog but unfortunately they are confusing because the time estimate displayed when dragging the sprint bar up and down is the original estimate, not the remaining estimate.
This means I have a 10 day task (original) that only has 2 days remaining but when trying to plan my sprint it looks like this task is going to take 10 days.
Can this be changed?
Check out https://jira.atlassian.com/browse/GHS-5282 Though it's marked as resolved, it appears Remaining Estimate is not supported for estimation. Burndown charts can now be based on Remaining Estimate and Time Spent. I know some team "split" incomplete stories before they complete a sprint; others just let those stories go back to the back log.
Depending on how strong you feel about using remaining estimate for Rapid Board planning, you may create a feature request with Atlassian.
By the way, I just saw Atlassian's GreenHopper product manager's comment about adding a "Split story" function in the future: https://answers.atlassian.com/questions/69248/technical-tasks-as-subtasks-of-stories-a-bad-idea?page=1#69482
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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