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.
G’day Bamboo customers, As we approach GA for Bamboo Data Center , we would like to inform you that the Data Center Apps Program for Bamboo starts this quarter. How long does it take? We are g...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events