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
Community Members
Community Events
Community Groups

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

Atlassian Community Events