When I have a project, which as a whole has a due date, shouldn’t each action implicitly have the same due date (unless otherwise specified)?
Otherwise, I would assume any action which does not show a due date has none, which is kind of misleading if the project is due tomorrow.
Definitely can imagine cases where due date inheritance would be beneficial. I wonder if that’s always the case.
+1 to this question/request (sorry for bumping a necro thread).
I see a project deadlines as a deadline for everything related to this project so all tasks within it appearing as “no due date” seems very misleading to me.
In other apps I used before, the date is usually inherited from its project by default, but can then be overwritten on a per-task level if there’s a more appropriate date.
I think it’s a good idea. It just requires some thought around the edge cases to not make due dates more confusing. I created a ticket, but don’t have a timeline.
1 Like