Hi Martin, Is there a way to stop portfolio from auto assigning issues to JIRA created sprints if there is excess capacity available? Portfolio created/suggested sprints are very useful, but it would be good if portfolio doesn't auto assign stories to manually created sprints in JIRA

Hi, how does this work with multiple stages that are split across sprints?
I can see how the portfolio side works but it doesn't update the JIRA issues with a sprint.

I can see from the help that issues that span multiple sprints aren't auto assigned back to JIRA. Is there a preferred / recommended approach to this?

Perfect, now is working!
My team was connected to the project instead of using the board.

Thanks

Hi rjuanpere1515137438, so this option should show up if:

• the team is connected to a board (in the teams section, ensure the team has a "preferred issue source" directly under the team name in the dropdown, and this source is a board) - so we know which board to actually commit to
• there is a future sprint created on that board, i.e., you create the next sprint on the board first (likely empty), then Portfolio makes suggestions as to what could fit into these, then you bulk-assign those)

>>essentially you can verify if this is the case, if the name of a non-active future sprint you've defined on the board shows up in Portfolio.

If that's the case, switch to the story hierarchy view and break down the schedule by team. then click the sprint name and the option to assign all scheduled issues to the sprint should show up. Once you've assigned it, make sure to commit the changes back to JIRA via the commit dialog.

Hope this helps, I've also asked to review and improve this doc section to make it more clear. Thanks!

Could you detail how to make the bulk-assignment of issues to sprints from portfolio?
I'm trying to use this help but I cannot see the mentioned option on my portfolio cloud.
Thanks

This issue has been addressed as part of new Portfolio live plans, which are now out of labs and the standard way of working with 2.0.

We have made the following improvements around sprints with live plans:

• Dynamically load sprints and sprint assignments from the boards
• Option to bulk-assign issues to sprints
• Committing manual sprint assignments back to the boards

The following sprint-related suggestion is still open:
Ability to create future sprints from Portfolio plans

As a work-around it is quite easy to just create the future sprint on the board and then bulk-assign the issues Portfolio scheduled into the sprint via the schedule in Portfolio.

Hi all, I've just posted an update above. Live Plans already address this 1 way already today, from agile boards into Portfolio. Until the final release, we're still planning to provide an option to also push suggested sprint assignments in Portfolio back to the board.

Cheers, Martin
Principal PM, Portfolio for JIRA

We want to use Portfolio but since the teams themselves use Jira Agile - it means we need to maintain spints both in Jira and Portfolio and keep them synched.

We did not use Portfolio previously as it did not fit our way of working. Portfolio Live has got us using the service, but a big drawback is the lack of sprint synchronisation. There seems little point in estimating sprints if you can't then sync those plans back to Jira.

I want this feature too. Hope we have it available soon.