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

Jump to bottom

Nested task is excluded from its supertask duration under some conditions #532

Open
GoogleCodeExporter opened this issue Jun 28, 2015 · 4 comments
Open

Nested task is excluded from its supertask duration under some conditions #532

GoogleCodeExporter opened this issue Jun 28, 2015 · 4 comments
Labels
auto-migrated Tasks Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1. Open the testcase .gan file attached with v2.5.2
2. See that the task "t" length is not taken in account for the linked tasks.
3. Resize the "t" task then press F5 multiple times to see the bad behaviour.

What is the expected output? What do you see instead?
Fix the refresh bug so that it takes in account all tasks dependancies.


What version of the product are you using? On what operating system?
2.5.2 Win & Linux same issue.


Please provide any additional information below.

Thanks very much for doing Ganttproject.

Best regards.
Stéphane.

Original issue reported on code.google.com by stephane...@gmail.com on 9 Jun 2012 at 11:34

Attachments:
@GoogleCodeExporter
Copy link
Author 

Interesting. Thanks for the report and for the sample project.

More detailed problem description, for the record: 
* after touching task "t" its supertask "l" is extended, so that it ends when 
"t" ends (07.02.13). That's expected
* each F5 makes "l" smaller, and eventually its end is set to 19.12.12, and it 
also affects its successors

Original comment by dbarashev on 21 Jun 2012 at 4:19

  • Changed title: Nested task is excluded from its supertask duration under some conditions
  • Changed state: Accepted
  • Added labels: Tasks

@GoogleCodeExporter
Copy link
Author 

Dear Dmitry,

Thanks for taking the defect.
Is it a difficult issue or not? How long do you think it will take you to fix 
it?

I am also interested in the new Milestone design without duration.

I have an other bug in my bag but I didn't check if it is already filled: 
Sometimes when playing with the "Move task up" and "Move task down" buttons 
makes the output PDF gantt drawing crazy (bad links, bad arrows for the moved 
tasks). I work around by creating new tasks directly where they should be and 
not moving them after.

Best regards.
Stéphane.

Original comment by stephane...@gmail.com on 29 Jun 2012 at 8:52

@GoogleCodeExporter
Copy link
Author 

At the moment I have no idea about the reasons and difficulty.

If you have a reproducible scenario for PDF problem, feel free to submit a new 
issue.

Original comment by dbarashev on 29 Jun 2012 at 2:57

@GoogleCodeExporter
Copy link
Author 

Dear Dmitry,

Thanks for the feedback. I hope it will be an easy one.
I will check if I can do a testcase for the PDF problem.

Best regards.
Stéphane.

Original comment by stephane...@gmail.com on 29 Jun 2012 at 3:48

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Tasks Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter