Improvement Suggestion - Automatic Definition of the Due Date for the Main Task

Description of the improvement

Implement the option for the user to automatically set the due date for the main task based on the highest due date among its subtasks.

When this option is enabled, the system must identify the subtask with the most distant due date and assign it as the due date of the parent task.

Operating example

Structure Expiration Date

Task 1 04/30/2025

└ Subtask 1 04/15/2025

└ Subtask 2 15/04/2025

└ Subtask 3 04/30/2025

In this scenario, since Subtask 3 has the most recent due date, the system must consider 30/04/2025 as the due date for Task 1.

Rules of behavior

The calculation must consider all subtasks related to the main task.

Whenever a subtask is:

created,

edited,

excluded,

or have your due date changed,

the system should automatically reassess the due date of the parent task.

The chain must work for all levels of the structure, encompassing tasks, subtasks, and nested subtasks.

The functionality must be optional and can be enabled or disabled by the user.

Benefits

It ensures greater consistency between the deadline of the main task and its subtasks.

It reduces manual adjustments and risks of date inconsistency.

It makes it easy to keep track of deadlines in complex task structures.