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

Freeze Scope


my plan is based on several Jira boards. From these boards I am interested in scheduling some issues (issue 1, 2, 3) of a release (release A) in Portfolio for Jira.

When new issues (issue 4 and 5) are added to a release (which is included as an issue source), I don't want these issues to show up in the scope. Is it possible to freeze the scope, so that no issues are pulled, no matter what?

Thanks and regards,


2 answers

2 accepted

0 votes
Answer accepted

Hi Scott,

thanks for the answer.

I like your suggestion and am pretty sure that this would work. Unfortunately we are not allowed to introduce new custom fields in our project.

Based on your idea I searched for (and found) an existing field that helped me to set a filter that excludes the redundant issues.

Thanks and regards,


Great, I'm glad I was able to help! Could you mark the answer as "accepted" so others can find it more easily?


0 votes
Answer accepted

Hi Phil,

I'm new to Portfolio, so this may not be the best way to accomplish this, but here's my suggestion anyway....

  • Add a custom field as a yes/no check box to your issue view called "Freeze Program Scope."
  • When you are ready to freeze the scope of the project  do a bulk update of all the issues in the project to change the check box to "Yes."
  • Copy the filters you currently use for the boards and add a clause for "Freeze Scope = Yes"
  • Use the new filter for your Program. 
  • Lock down or hide the "Freeze Scope field so only an admin can update it. 

This should keep your Program limited to the initial scope of the projects while allowing new issues to be added to a project. 

One caveat though...Like I said, I'm new to Portfolio, so i don't know if adding issues that are not part of the frozen scope would have an unintended consequence to the program. I can think of a scenario where a bug or sub task is added to the project that causes an issue from the scope to be delayed or moved to a later sprint, which could impact your program's timeline. 

If you try this make sure you test it out...and post the results here. If it works, please mark the answer as "accepted" so others can find it.

Hope this helps, 


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...

142 views 1 3
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