The alh-replace: typestory/alh-replace can have one or more Deadlines to meet. The earliest deadline (also called the Effective Deadline) determines when the alh-replace: typestory/alh-replace has to be completed. If this deadline is not met, warnings will be shown on the alh-replace: typestory/alh-replace card and overview.
“Required When” Deadline
In the Required When field a specific deadline date for this alh-replace: typestory/alh-replace can be entered. It is an option to set a specific deadline for when the alh-replace: typestory/alh-replace is required to be completed. It can be seen as the When part of the user story.
If a Required When date is set, this will be included in deriving the effective deadline.The planning date must meet the effective deadline, otherwise warnings are shown.
Deadline from Milestone or Release
If the deadline is related to an event or if more stories or epics must meet the same deadline date, then a milestone with a deadline should instead be created. The alh-replace: typestory/alh-replace can be linked to the milestone from the Relations tab.
A Release is also a milestone with a deadline. Planning the alh-replace: typestory/alh-replace to a release will therefore also mean that the alh-replace: typestory/alh-replace must meet the deadline of the release.
Inherited Deadline
If an epic has deadlines, any story detailing this epic will inherit the effective epic deadline as one of the story’s deadlines. It will also become the effective deadline of the story, unless the story has other earlier deadlines to meet.
