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
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I too have this problem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.