Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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

How to stop the auto-assignment of issues to releases

From sprint to sprint, my team works on a variety of cards.  Right now, it's as common for them to be assigned to releases as it is for them to be unassigned to a release.  I want to see all of the cards my teams work on in Portfolio.  However, I do not want Portfolio to automatically assign cards that aren't assigned to a release.

I am new to using Portfolio, so I'm hoping there's a way to accomplish what I'm looking for but I just haven't found it yet.  If anyone knows of a way to prevent Portfolio from automatically assigning issues to releases, I would love to hear it.

1 answer

I am still quite new to Portfolio as well, but one way that I found is to remove the Story Points from the ticket. Then Portfolio won't know how to schedule it and it won't be assigned to a release.

Thanks, Phillip - I'll give that a shot! 

THANK YOU PHIL!!  Removing the story points from issues that were automatically assigned to a release reverts that auto-assignment!  Although do I still believe that Portfolio should provide the ability to either: prevent the auto-assignment of issues to releases or remove issues from releases without assigning them to another one, this is a great workaround!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events