GNOME Bugzilla – Bug 576275
predecessor drop down seems to rely on unique task names and not use the unique task-id
Last modified: 2009-11-18 12:04:59 UTC
Please describe the problem: on a large project with multiple phases several tasks may have the same name e.g. test . I have a project with a number of summary tasks below which I have the same sub-tasks (by name). Obviously in the xml file they all have unique task IDs. if I add a new task and select one of these sub-tasks as predecessor then the first entry with this name is used regardless of the entry (with this name ) selected. I need to edit the xml file to correct this behaviour, Steps to reproduce: 1. create a project with 2 summary tasks One and Two 2. add 2 subtasks to each summary task , test and test2 3. make test a predecessor (FS) of test2 for subtasks in One (select first entry called test in the drop-down list) 4. make test a predecessor (FS) of test2 for subtasks in Two (select 2nd test in the drop-down list ie below summary task Two) Actual results: test in summary task One becomes predecessor of test2 in summary task Two as well as predecessor for test2 in summary task One Expected results: test in summary task Two becomes predecessor of test2 in summary task Two and test in summary task One becomes predecessor of test2 in summary task One Does this happen every time? yes Other information:
*** This bug has been marked as a duplicate of 342320 ***