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