Project

General

Profile

Forums » Help »

Does anyone else have problems setting a due date on a task that has subtasks?

Added by Deoren Moor almost 11 years ago

Scenario:

  1. A parent ticket with two child tasks.
  2. Both child tasks are closed.
  3. No due date is set on any of the tasks, but all three have Start dates set (later tests seem to indicate this doesn't matter).
  4. I attempt to set a due date on the parent task and I am blocked from doing so.

Is this by design? I could see this mattering more if the child tasks were still open, but they're closed in this case. In the case of both child tasks still being open, I am still unable to set or modify a due date on the parent task.

We've found that you can set due dates on the child tasks and have the parent inherit the due date. In my test case I set one child task as due today and the other test child case as due tomorrow and tomorrow's date was used on the parent task.

What is the expected behavior here? From my point of view, I expect to be able to modify the parent task's due date.

Thanks for your help.


Replies (2)

RE: Does anyone else have problems setting a due date on a task that has subtasks? - Added by Mischa The Evil almost 11 years ago

Deoren Moor wrote:

Scenario:

4. I attempt to set a due date on the parent task and I am blocked from doing so.

Is this by design?

Yes, this is by design. See r3573 for #443.

I could see this mattering more if the child tasks were still open, but they're closed in this case. In the case of both child tasks still being open, I am still unable to set or modify a due date on the parent task.

This "blocking" of changing several properties of parent issues is not related to the fact of subtasks being open or closed (read: issue statuses are not related).
The only thing that matters in this context is the fact whether or not the issue is a leaf node in the nested set (i.e. it has no subtasks).

We've found that you can set due dates on the child tasks and have the parent inherit the due date. In my test case I set one child task as due today and the other test child case as due tomorrow and tomorrow's date was used on the parent task.

That is the expected behavior. Subtasks' priority, start/due dates, progress (%-done), estimated time and spent time roll-up to parent issues. This is also the (main) reason why these properties of parent issues are "blocked" from being edited manually.

What is the expected behavior here? From my point of view, I expect to be able to modify the parent task's due date.

The expected behavior is as it is now. Though, more users share your POV and have opened issue #5490.

RE: Does anyone else have problems setting a due date on a task that has subtasks? - Added by Deoren Moor almost 11 years ago

Thank you for taking the time to answer my questions.

I have to agree with the others that this behavior seems a bit odd. For whatever reason it seems "right" to have a parent task control the child tasks, not the other way around. I can't help but feel I'm overlooking something.

    (1-2/2)