I’ve done some testing, and it appears that relative due dates in templates are messing up project due dates when converting tasks into projects with rules.
Ideally, in a project pipeline where work starts as a task and gets eventually converted into a project, the due date of the task carries over to the project.
This appears to be the case for when there is no template being used.
But if there is a template being used, it gets confusing.
I tested with a template that has:
- a task 2 days before project date
- a task on project date
- a task 2 days after project date
I found the following scenario’s:
- A: template is planned relative to project start date, and task has no start date:
– project due date is determined by task due date
– project start date is determined by task 1 - B: template is planned relative to project start date, task has start and due date
– project start date is determined by task start date
– project due date is determined by task 3, regardless of task due date - C: template is planned relative to project due date:
– project due date is determined by task due date
– project start date is deterimined by task 1, regardless of task start date
See here my tests:
I can understand scenario A, although I would lean towards assuming project start date is project end date. But my opinion isn’t strong on this.
But, when a task has both a start and a due date, I feel the project should always inherit these dates.
Contexts I’ve come across this are:
- Planning media campaigns
- Managing reservations
This would allow a more fully automated project pipeline that starts with a Form, without needing to correct the project dates after project creation.
@ambforumleader @pforumleader Any of you find a workaround for this by any chance?
Related feature requests, that help move toward a more fully automated project pipeline: