You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When I started using Portfolio, the Later release didn't contain any start or end date. But recently I noticed that in some cases (plans) a start and end date is actually assigned to the Later release...and the start date is not always after the end date of the last known release in the plan.
What is the reason for this? Can we change it?
Thanks in advance
Later release is the placeholder for all the issues that scheduler cannot schedule into any of the releases. The Later release is used as a last resort by the scheduler.
The start date of the Later release is the start date of the issue starting first. User cannot change this date as issues cannot be assigned manually to Later release.
I hope this helps.
Portfolio for Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.