Sync Due Dates between parent and child Items.
Due Date Syncing automates the process of matching Due Dates between parent and child Items. This feature ensures that when a Due Date changes on a parent Item, you can easily update the children or vice versa, reducing the number of clicks needed to keep dates aligned.
Use Cases
- Utilize Due Date Syncing to automatically update deadlines for nested tasks when you adjust the parent project's due date. Your project team will remain in alignment, and you'll save time on manual adjustments.
- Due Date Syncing helps you automatically adjust a parent project's due date when a task nested below it requires an extension. The project will automatically update to reflect the extended timeline, helping you maintain accurate forecasts for project completion.
Configuration Options
Important: Due Date Syncing must be enabled and configured by KaiNexus staff. Contact your Customer Success Manager to get started.
Your Customer Success Manager will help you design this feature for your specific use case, but here are some tips for how Due Date Syncing works:
- Due Date Syncing is configured at the Template level, meaning all Items created from the Template will follow the same Due Date Syncing logic. It can't be enabled on an Item-by-Item basis.
- Due Date Syncing only occurs on one nesting level, meaning only the immediate parent or child Items are affected.
- The parent and child Items must both have Due Dates for Due Date Syncing to occur.
- Due Date Syncing can work in two directions: child Items updating their parent and a parent Item updating its children.
Update Parent
Your first configuration option allows Due Date changes on child Items to update the parent's Due Date. You can design the feature to allow users to opt-in to updates or have the updates occur automatically without user intervention.
- User choice: If you want users to decide whether changes to a child's Due Date should update the parent's Due Date, there will be an Update Parent Due Date checkbox when they edit the child's Due Date, allowing them to choose whether the sync occurs. This checkbox can be selected or unselected by default.
- Automatic: If you want syncing always to occur when a child's Due Date is updated, the parent's Due Date will automatically adjust based on the updated child's Due Date. This configuration also allows for the following functionality:
- Due Date Syncing will occur when you update an Item's parent.
- Due Date Syncing will occur when you create a nested Item with a Due Date set on the create screen.
- Due Date Syncing will occur when you add or update a child Item's Due Date during a Status transition.
Important: Each time you update a child's Due Date, there is logic that determines whether the parent's Due Date is also updated. This ensures that only relevant Due Date changes update the parent.
When there are multiple children, the parent will inherit only the child's Due Date with the farthest out date.- Example: If a parent has two children, one with a Due Date of August 15th and one with a Due Date of August 20th, updating the Due Date of the first child to August 16th would not change the parent's Due Date because there is still one child with a Due Date father in the future.
- Example: If a parent has a Due Date of September 1st and all its children have Due Dates in August of the same year, then updating a child's Due Date to a different date in August would not change the parent's Due Date.
After Due Date Syncing occurs, you can still update the parent's Due Date as you wish. However, the next time a child Item's Due Date is changed, the Due Date Syncing logic will run again to determine whether the parent should update.
Pro Tip: Due Date Syncing does not require permission to edit an Item's parent to update it by editing the child Item.
Update Children
Your second configuration allows Due Date changes on parent Items to update their children's Due Dates. You can design the feature to allow users to opt-in to updates or have the updates occur automatically without user intervention.
- User choice: If you want users to decide whether changes to a parent's Due Date should update its children's Due Date, there will be an Update Children Due Date checkbox when they edit the child's Due Date, allowing them to choose whether the sync occurs. This checkbox can be selected or unselected by default.
- Automatic: If you want changes to a parent's Due Date to always update the children's Due Date, the sync will automatically occur after a parent's Due Date is edited. This configuration also allows for the following functionality:
- When you create a nested Item and the Due Date is set on the create screen, the child Item will inherit the parent's Due Date upon saving.
Important: Due Date Syncing will affect all of a parent's children with an existing Due Date, except for Archived and Complete Items. In addition, the children will sync to the parent's Due Date regardless of whether you push out or pull in the parent's Due Date.
After Due Date Syncing occurs, you can still update the child Item Due Dates as you wish. However, the next time the parent's Due Date is updated, the child Items will sync to the parent's due date again.
Limitations
- Due Date Syncing will not affect Complete or Archived Items.
- Due Date Syncing will not occur when you update Item Due Dates through imports or API.
- Due Date Syncing will not occur when you use Bulk Change to update Item Due Dates.
- Due Date Syncing will not occur when you create new Items through Quick Create, Copying, and Standard Work.
- Converting an Item to a Template with Due Date Syncing enabled will not trigger Due Date Syncing.
- When you update an Item's children through Due Date Syncing, the updates will only apply to the first 100 child Items.
- When a parent is configured to automatically update its children's Due Date and the child Item is configured to automatically update its parent's Due Date, the parent's Due Date will take priority.