Near the end of a sprint, we find that some items didn't finish, and will need to carry over into the next sprint. It would be convenient if we could use Portfolio to incorporate those items into the plan for the next sprint, perhaps by noticing that if an item in the current sprint has a Remaining Time Estimate that is larger than the number of days left in the sprint, the carry over time should be scheduled into the next sprint, and deducted from the assignee's capacity in that sprint. Is there a way to do this? Are there other workflows for carrying over an item in the currently open sprint into the next sprint?
UPDATE: After working on this more, it's worse than I thought. Let's say we've got two days left in Sprint 10, and I'm trying to plan Sprint 11. There are Stories still open in Sprint 10. If the time estimates are greater than the time left in Sprint 10, Portfolio will not be able to schedule those items any more, and any dependencies of those items in Sprint 11 will not be schedulable. What's the correct workflow here? We don't really use time logging to update the Remaining Time Estimate, but maybe that's the key?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Recently, as part of a series of Portfolio for Jira case studies, we spoke with Carl DiClementi, Director of Product Management at Factom about how he uses Portfolio for Jira. In...
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