We created custom sprints for a team. Portfolio automatically assigned stories to sprints. But when the first sprint time was over, Portfolio didn't move stories to the next sprint and didn't signalized that we failed.
Could anybody explain why, please? What is the reason of using Portfolio if it doesn't signalize about such failure and doesn't move stories on and on.
http://prntscr.com/868iaj - printscreen
The same situation is with automatic sprints (sprint1 ... sprintN) http://prntscr.com/868mak
Hi Vladimir, thanks for raising this question - the way it is designed right now is that stories move on only as part of explicit plan updates (Plan > Update from date) - this sets a new start date from when to schedule, and stories will be scheduled only from that date forward. Currently the start date of your plan is Aug 10, so work will be scheduled starting from there. If you run a plan udpate and set the new start date of the plan to let's say Aug 20, sprints before Aug 20 will be ignored and items scheduled into sprints after that.
However, all that said we're working on a tighter integration with JIRA / JIRA Agile as part of addressing our top-voted issues over the coming months (https://jira.atlassian.com/browse/JPO-10, https://jira.atlassian.com/browse/JPO-42, https://jira.atlassian.com/browse/JPO-13) which will significantly simplify and automate this update process. Best, Martin (Product Manager for JIRA Portfolio)
The Portfolio for Jira team wants to hear from you. Share your top tips for building a great Portfolio for Jira plan for a chance to win some Atlassian swag. Do you structure your teams i...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot