Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

moving parent task doesn't move all sub-tasks #25

Closed
GoogleCodeExporter opened this issue Jun 28, 2015 · 10 comments
Closed

moving parent task doesn't move all sub-tasks #25

GoogleCodeExporter opened this issue Jun 28, 2015 · 10 comments

Comments

@GoogleCodeExporter
Copy link

Copied from the bug tracker on SourceForge:
http://sourceforge.net/tracker/index.php?func=detail&aid=2504529&group_id=72728&
atid=535427


Hello,

Moving a group of tasks needs as many operations as tasks (!)

Steps to reproduce:

1) create 4 tasks as following:
- "metatask"
- "task1" (child of metatask)
- "task2" (child of metatask)
- "task3" (child of metatask)

2) move metatask (with the mouse). Let's say we want to shift it for 1
week

3) result 1: task1 is moved, but taks2 and taks3 are not. By the way
metatask is now longer

4) repeat the move a second time: task2 is moved, but task3 is not

5) repeat the move a third time: all tasks are now moved.

This behaviour is a pity if you have lots of sub-tasks.

What user expects is that all sub-tasks are moved together when the parent
task is moved.

Is there a workaround ? Is it possible to correct this ?

thanks

NB: versions and environnement:
- linux Mandriva 2008.1
- java 1.6.0_06 (RPM from Mandriva)
- Gantt Project 2.0.9 (release still not present in SourceForge Tracker so
I put 2.0.8)

NB2: other bugs not directly relevant but close to:
-
https://sourceforge.net/tracker2/index.php?func=detail&aid=1315241&group_id
=72728&atid=535427
-
https://sourceforge.net/tracker2/index.php?func=detail&aid=1102023&group_id
=72728&atid=535427
-
https://sourceforge.net/tracker2/index.php?func=detail&aid=1404507&group_id
=72728&atid=535427
-
https://sourceforge.net/tracker2/index.php?func=detail&aid=1050283&group_id
=72728&atid=535430
-
https://sourceforge.net/tracker2/index.php?func=detail&aid=954528&group_id=
72728&atid=535430
-
https://sourceforge.net/tracker2/index.php?func=detail&aid=1255509&group_id
=72728&atid=535427
-
https://sourceforge.net/tracker2/?func=detail&aid=2477136&group_id=72728&at
id=535427

Original issue reported on code.google.com by dbarashev on 4 Apr 2009 at 12:51

@GoogleCodeExporter
Copy link
Author

Moving a supertask is not moving its subtasks, but it looks whether the 
subtasks 
still 
fit in the start-end dates of the supertask.
Unfortunately this is done in a non-atomic matter and after moving one subtask, 
the 
start-end dates are changed and all of the other task fit (and are not moved)

My suggestion it to reimplement the algorithm of moving (super)tasks by just 
moving 
the task and subtasks when they are not a supertask. This way all 
non-supertasks are 
moved, the internal mechanisms will update the supertasks and everything is 
moved!

I am willing to take a look at this, but I would like to receive comments 
whether 
this is a/the desired strategy not.

Original comment by maarten....@gmail.com on 20 May 2010 at 10:32

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

When I make adjustments to subtasks the parent headers do not adjust to fit the 
new start and end dates. Even after adjusting dates and using the drag feature 
to shift the end point. There seems to be a great deal of difficulty around 
readjusting start/end points.

See example mentioned above in the attached screen shot. Pro Box Parent would 
not shift end date to match the new milestone date. Even manual changes to date 
and using slide feature on the parent grouping did not work. It would always 
snap back to original date.

Original comment by Jinkhi...@gmail.com on 11 Feb 2012 at 3:30

Attachments:

@GoogleCodeExporter
Copy link
Author

Milestone "Pro Box Review".
Full File. Not sure if the milestone having a duration of 7 days might be part 
of the problem but I can't seem to make any change to that range.

Original comment by Jinkhi...@gmail.com on 11 Feb 2012 at 3:37

Attachments:

@GoogleCodeExporter
Copy link
Author

Nevermind. I kept messing with it and ofund that I have to actually go into the 
milestone edit datails - uncheck it as a milestone - adjust the duration (that 
was automatically greyed out) - then recheck it as a milestone. When I OK and 
return to the main screen the parent grouping (if that is actually what you 
call it) does snap automatically to fit the true start and end dates of the 
whole project. Either it should not gray out the option to to edit ranges in 
the milestone or it should automatically adjust to a 1 day duration since as a 
milestone. 

Original comment by Jinkhi...@gmail.com on 11 Feb 2012 at 3:48

@GoogleCodeExporter
Copy link
Author

Original comment by dbarashev on 2 Jun 2012 at 4:32

  • Added labels: __Target-Brno

@GoogleCodeExporter
Copy link
Author

If we link predecessor task to only main task, Sub Tasks under that main task 
will not align properly within main task.

a) Sub Tasks start before main task start.
b) Sub tasks do not start at the same time of main task start date.

Please see attached photo and project files for more detail.

If we link predecessor to all individual sub tasks, sub tasks move 
automatically correctly within main task.

Original comment by ka...@msn.com on 7 Aug 2012 at 3:50

Attachments:

@GoogleCodeExporter
Copy link
Author

This issue was updated by revision 54c5ef8970a3.

Original comment by dbarashev on 29 Oct 2012 at 4:49

@GoogleCodeExporter
Copy link
Author

Original comment by dbarashev on 22 Nov 2012 at 2:15

  • Changed state: FeelFreeToTest

@GoogleCodeExporter
Copy link
Author

Original comment by dbarashev on 22 Sep 2014 at 12:19

  • Changed state: Verified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant