Allow change of task due date with CTA due date change

@catherine.spevak sorry for the inconvenience. This is made purposefully I think, task due date cannot be higher than the CTA due date. 

Hi, I understand the general restriction, but this restriction seems to be too fine since I’m not able to briefly circumvent the restriction to update the WHOLE CTA’s due date. Does the flow that I’m trying to follow make sense?

@catherine.spevak I want to understand the use case better. What should happen to task due date if CTA due date changes? (We don’t want to remove the restriction of task due date < CTA due date since tasks are a part of that CTA and hence, cannot have a higher due date)

Hi, When I configure a task’s due date to be the same as the parent CTA’s due date, I would like to then be able to update them together as well! For example, if I create a CTA from a playbook where all tasks have the same due date as the parent, and then a week later I want to move that CTA’s timeline up, I would like a workflow where I can do these all at once rather than editing each task individually. We sometimes have playbooks with 15-20 tasks with the same due date.

Thank you!

Catherine

Understood your use case @catherine.spevak. Do you also create manual tasks? If you do, what should happen to that due date? (given the task due date < CTA due date restriction).

We don’t typically create manual tasks, but it would make sense to me to just have the relationship between task due date and CTA due date behave in the same way regardless of if the task was created manually or with a rule.

Upvote this.

This is basically to have the ability to auto adjust the tasks due date when the CTA due date is moved to an earlier date. Auto adjust them based on playbook settings for playbook tasks and other tasks with an exception that tasks due date cannot be prior to the modified date of CTA. This is our use case.

We kind of have this logic when CTA due date is extended.

Thanks for the use cases. We will evaluate this. We don’t have a timeframe for solving this yet.

Going to resurrect this idea as it would be a nice quality of life improvement for our end users to not have to update multiple task due dates prior to adjusting the overall due date.

As has been said, playbook settings and criteria would cover a good bulk of the data management & I think others (i.e. manual tasks) should be up to the admin to determine standards in our Cockpit administration settings. For example, set manual task dates to CTA end date if it’s moved up. 

This sounds like we should have a toggle (similar to the one below in Photoshop) that allows locking the due dates for tasks and overall CTA, so that changing one changes all the others. Ex: “CTA Inherits Due Date from max-date task”, “Task dates inherit CTA end date”, or something similar.