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!


Portfolio for JIRA: Why/when are dates assigned to the Later release?

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.jpg

1 answer

0 votes
Chiragkumar Rupani
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 24, 2019

Hi Christophe,

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.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events