Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I keep issues in backlog and prevent them to be assigned to a sprint by calculation?

I'm using standard backlog for issues that are not yet assigned to any sprint since they are e.g. ideas not yet technically designed or customer didn't approve work estimate yet. 

When trying to create a plan with jira portfolio, all those backlog issues were placed to sprints by calculation. Is there any possiblity to keep them in backlog and don't assign them to any sprint?

1 answer

0 votes
Bree Davies Atlassian Team May 25, 2017

Hi Jussi, 

There is an easy workaround in JIRA for this. 

For work that is not ready to be worked on (so you don't want it to be scheduled into any kind of Portfolio plan) use a label to denote it as 'not-ready' or a certain status. 

Or conversely, if you could label issues that are ready with a 'ready-for-dev', if this is going to be the least amount of effort. 

Create a new filtered board which excludes any issues matching this label, and connect your plan to this board. 

This will prevent any issues you don't want to see from appearing in your plan as they are created. 

The other option would be to create a 'backlog' release with a fixed start date in the future, and then manually assign all of your 'not ready' issues to this release, so they aren't scheduled to any upcoming sprints. You'd still see this issues in your scope table and within your plan, but you'll be forcing their lower priority. 

Hope these help



Hi Bree; is there a way to exclude items by state? We've run into two issues thus far with the solution you described:

  1. The "Open Issue" workflow action removes all fix versions and manually adding a Fix Version interferes with other queries we run which look for empty Fix Version issues
  2. We prioritize work on a variety of separate boards, and keeping parallel boards which filter out items that aren't "Selected" isn't scalable.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

122 views 8 10
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