fixed issue start dates and auto-schedule

[Craig A]

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

Example-

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

https://community.atlassian.com/t5/Advanced-Roadmaps-questions/Fixed-start-date-requirement-in-auto-scheduling/qaq-p/1384682?tempId=eyJvaWRjX2NvbnNlbnRfbGFuZ3VhZ2VfdmVyc2lvbiI6IjIuMCIsIm9pZGNfY29uc2VudF9ncmFudGVkX2F0IjoxNjAyMTc3Mzk1NTQ4fQ%3D%3D

Thanks in advance.

[Bernhard H_]

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.

[Bernhard H_]

Hi all,

I found a service request https://jira.atlassian.com/browse/JPOSERVER-2563 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.

[Yves Tellier]

Same for me

[minhtrietbkit]

I too have this problem