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?
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:
The Portfolio for Jira team wants to hear from you. Share your top tips for building a great Portfolio for Jira plan for a chance to win some Atlassian swag. Do you structure your teams i...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot