Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


fixed issue start dates and auto-schedule

How do I fix a hard start date to an issue that wont be overwritten by Auto-schedule.



I have an issue that cannot be started until 10/15, because parts will not be in house.

How do I force advanced roadmaps to respect that date even when I auto schedule?


For reference, I'm have the exact issue explained here


Thanks in advance.

3 answers

Unfortunately, for whatever reason, Atlassian removed the feature "Earliest Start Date" from the new planning interface. 

Next to switch back to the old planning interface (old name Portfolio4JIRA), as a workaround, you can try to assign the second story to a release which has the intended fixed start date as start date of the release. Then, according to the documentation, the auto scheduler starts the calculation of the story at the start of the release.

Hi all,


I found a service request which requests to bring back the former "Earliest Start Date" feature to the new interface. Please vote for it if you are interested in getting it back. It should help to solve your (and honestly my) problem.

Same for me

I too have this problem

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events