Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Once you commit changes made in Portfolio into JIRA , how do you use Portfolio to re-simulate


Once you commit the changes made in Portfolio Plan into JIRA, each story is assigned a sprint. 
To my understanding this prevents Portfolio from moving these stories in its next plan simulation (sandbox). so we are left with a fixed plan that only way to re-plan it is by moving back all stories from Sprints to Backlog.

How should you use Portfolio to re-simulate after the first Plan commit?


Note: we are working with the non-improved interface.

1 answer

1 accepted

0 votes
Answer accepted

Hi Gil,

A commit finalizes that the values and sets them on the issue.  Once you commit a value to the sprint field the sprint is set and as you noted needs to be cleared to make changes to the plan as the scheduling algorithm is using the sprint field as one of the weighted items to calculate the issues position in the scope.  So once the sprint is set it anchors the issue to that committed sprint location.

If there is not an active or future sprint avaliable to add an issue too, Portfolio will populate a logical placeholder sprint that will not anchor the issue to that committed sprints location and use the alternate scheduling factors in the schedule.

So if you are looking to have more leniency in the sprint commitment you can set up your sprint planning more ad-hoc by only having the current sprint created then only create future sprints where the resources commitment can be confirmed, so that portfolio will place issues into the logical place holder sprints when running the calculations based on the other scheduling factors vs using the committed values of the sprint for the scheduling factors.


Thank you Earl,

This is what was our understanding as well (and work like that with some groups)

It does raise couple of more questions on they way we could work and get specific reports, so I will open these in a different thread.

Thank you again,


Like Earl McCutcheon likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

238 views 2 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you