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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Release fixed start and end dates have changed



I am trialling Portfolio as we hope to utilise it for our resource planning. I currently have two projects showing in Portfolio and am happy with the scheduling so i have applied fixed start and end dates to all the Releases associated with the two projects.

I have now introduced a third project, but rather than scheduling the work around the committed workload and dates for the first two projects, it has changed the fixed Release dates assigned to the second project - the fixed Release dates for the first project that I introduced remain unchanged (Note: The only difference between the first and second project is the first project has dependencies from start to finish, where as the second project only has dependencies for the the first half of the project).

Why have the fixed Release dates for the second project been changed now I have introduced a third project? Do the fixed dates not necessarily mean they cannot be changed?

Best regards


0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events