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,558,909
Community Members
 
Community Events
184
Community Groups

Why does the Auto-Scheulder overwrite Releases when I specifically set it not to?

We've recently upgraded to Portfolio 3.0 (currently 3.9) and I'm tasked with evaluating it prior to the rest of the organization using it.
I'm noticing odd behavior with the Auto-Scheduler where we specifically set it to not overwrite Releases if the fields are not empty, yet it goes ahead and clears the value anyway.

Here are some screenshots:

Portfolio Auto-Scheduler 1.pngPortfolio Auto-Scheduler 2.png

Is there any reason why it seemingly isn't following its own rules?

Thank you

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events