Project

General

Profile

Actions
Copy link

Feature #37568

closed

It should be possible to set a due date on a subtask without affecting the parent task

Added by Stefan Mark over 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid

Description

When setting a due date on a subtask, the parent tasks due date is set to same date and cant be changed later.

I could understand the other way round, but just because a tasks subtask should be done tomorrow, it should not means that the parent task has to be done tomorrow. The other way round maybe.

Note: this might also be Bug, but i am not sure.

Redmine 5, ruby 2.7, mariadb 10 (mysql)

Thanks :)

Actions
Copy link
 #1

Updated by Mischa The Evil over 2 years ago

  • Status changed from New to Needs feedback
  • Resolution set to Invalid

Starting with Redmine 3.1.0 there is a dedicated setting that provides the administrator the ability to configure this behavior (i.e. let parent issues have start- and due dates that are independent of their subtasks) at the instance level (see #5490#note-91).
It can be found as:
"Administration" > "Settings" > "Issue tracking" > "Parent tasks attributes" > "Start date / Due date"

Actions
Copy link
 #2

Updated by Stefan Mark over 2 years ago

Oh no. So sorry! You are totally right. I had some bad communication, extracted the wrong information from that and failed to do a final check on my own. I usually do. Should have this time too.

Again, sorry for wasting anyones time. I will try to protract my next stupid stance as much as possible :)

Actions
Copy link
 #3

Updated by Holger Just over 2 years ago

  • Status changed from Needs feedback to Closed

Don't be too harsh to yourself. I'm glad we could resolve this :)

Actions
Copy link
 #4

Updated by David L over 1 year ago

I was also interested in this feature. The OP touched on a better idea than the current version, which only offers a partial solution.

Problems:
1. When dates are "independent", a subtask's due date can be set after the due date. That doesn't make sense.
2. The % done is either a sum of the subtasks or arbitrary. That makes the parent issue a container, rather than an issue.

Fix:
In addition to "independent", there should be:
1. A setting that keeps child end-dates within the parent scope. That may or may not also limit start dates.
2. A setting that calculates the % done as subtasks + parent task.

As a simple example:

Issue: Drive my car to my house
Subtask: Fill car with petrol
Subtask: Replace punctured tyre

With Fix 2, the % Done can be a sum of three issues.

If the parent issue is not allowed to be part of the equation, then I don't see how we can structure dependencies.

  • Issue: Drive my car to my house
    • Subtask: Prepare car to drive
      • Subtask: Fill car with petrol
      • Subtask: Replace punctured tyre

In this second example, "Prepare" is dependent on two subtasks, which is good. However, once "Prepare" is complete, so is "Drive".

I can add another subtask to represent the actual driving:

  • Issue: Drive my car to my house
    • Subtask: Drive my car
    • Subtask: Prepare car to drive
      • Subtask: Fill car with petrol
      • Subtask: Replace punctured tyre

But that means breaks the dependency. I can set "Drive" to complete, even before "Prepare".

Actions
Copy link
 #5

Updated by David L over 1 year ago

Should I open a new request for this?

Actions
Copy link

Also available in: Atom PDF