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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,344
Community Members
 
Community Events
176
Community Groups

How do you manually set an issue to the later release?

The system will automatically assign certain issues to the later release based on your dates & capacity.

My question is how do you manually set an issue to specifically be in the later release?

It's very annoying for Portfolio to automatically add assign issues to sprints when I don't plan on doing them anytime soon.

1 answer

Not possible. 'Later' isn't really a release but more of a status indicating it's falling outside any named/date-defined release.

In my view, the fact that it's not possible is a big problem.

The system doesn't do a good job of placing things into the "later" release.  The scheduling algorithm is not transparent and it's would be VERY useful to say "this work is going to be done later".

This is particularly relevant when you have epics sitting on your backlog that you are avoiding.

Rick Crow is right here. And it does not do it based on dates or capacity. As soon as an issue is "plannable", Portfolio will put it into the later release so it can be shown on the visual data-driven roadmap.

When is something plannable? As soon as it has an estimation, target start or end date, sprint assignment or release. When it doesn't have any of these an item is not plannanble and will not appear on the roadmap.

 

So to close it off (and as Andrew already said): when something is plannable but has no release assignment it will get into the later release which actually is not really a release but needed to show it on the roadmap.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events