Wrong predecessor referenced when multiple tasks have the same name
Bug #820765 reported by
Andreas Almroth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| planner |
Fix Released
|
Medium
|
|||
| planner (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Say we have a WBS with a task with several subtasks, one is named "Install OS", another subtask is referencing this, and it is fine.
Then, later in the plan we have another task (unrelated to the first task/subtasks as such. We again have a subtask called "Install OS", and another subtask is should use this as predecessor. In the GUI, selecting the correct predecessor does not give the expected result, but in the Gantt chart, the very first "Install OS" in the list is referenced instead, leading to the project dependences becomes incorrect.
The obvious workaround is not to have two tasks/subtasks named the same. This works, but not neat.
Proposal: Reference on WBS number instead of name.
Kind regards,
Andreas
| Changed in planner: | |
| importance: | Unknown → Medium |
| status: | Unknown → New |
| Changed in planner: | |
| status: | New → Confirmed |
| Changed in planner: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
