Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


New Experience - Optimize. How to exclude stories from optimization?


I'm using Portfolio with New Experience turned on. I'm trying to apply this handy functionality to SAFe we running in our team. So I have a portfolio plan for the release train of multiple agile teams in order to visually track and manage dependencies.

But there is something I can't understand. If I want to optimize (that button on the top right) a Roadmap for one team (keeping the rest unchanged), then it looks like I always have to create a separate Portfolio Plan. Otherwise if I press Optimize in a plan where there are multiple teams, then optimization will be applied to all of them and there is no way I'm able to limit optimization to only stories of one team...

Can anyone give me a hand here?

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 28, 2019 • edited Apr 02, 2019

Hi @Georgii Lumpov ,

The ability to run the scheduling algorithm on only parts of a plan is something we are aware of, but unfortunately at the moment don't support.

I'm afraid if you're looking to only schedule one team, you'll need to create a separate plan that only shows that team's work. I know this isn't ideal.

One challenge we will need to solve is that when you schedule for a sub-set of a plan, whether to take into consideration what other teams are doing. It could be that you get a different result depending on whether you schedule for all teams, or just a sub-team. I would love to hear your thoughts on this topic. 


Thanks for a detailed reply @samrobertsofficial !

"It could be that you get a different result depending on whether you schedule for all teams, or just a sub-team" — for sure. For a sub-team there is less possibilities to optimize, less variables to consider. I think it is pretty much expected.

And to be honest this is what I desire to see. By doing a scheduling for a sub-team I'm basically saying "Hey Jira, freeze all those guys for now, except this folks and optimize what you can in that isolated set of tasks."


And just some more context for the use-case. For me it is a sort of a QoL thing and is related to the two topics

  1. tracking dependencies b/w sub-teams. I have asked that question separately (how to show external dependency?). 
  2. creating only one Portfolio Plan vs. multiple just for doing "optimize"

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events