-
Notifications
You must be signed in to change notification settings - Fork 300
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
indenting sub-project groups works not for all sup-project groups #1169
Comments
Anything went wrong with the images upload? |
I attached the two files – same name Von: Dmitry Barashev [mailto:notifications@github.com] Anything went wrong with the images upload? — |
I don't see any images here. I suspect that GitHub doesn't support email attachments. Please attach the images in the web UI. |
Can you attach or send the project file itself? And did you really mean to close this issue? |
Sorry, wrong button. |
Von: Dmitry Barashev [mailto:notifications@github.com] Can you attach or send the project file itself? And did you really mean to close this issue? — |
I don't see any .gan file here. |
Dragging the denied project group was possible. It looks like, that one dependency between a task and a group was causing a circular dependency. "Drag and drop" action deleted the dependency without any information. |
Yes, circular dependencies is one of the likely reasons. I can't say anything certain until I see the file, though. Unless you believe that the issue is resolved now, please send the file by email. You can find our contact email on http://ganttproject.biz/about |
For the record: the issue was the dependency between tasks, and it is expected that indent is not possible in this case. However, drag'n'drop violates the rule and removes the dependency. I submitted issue #1170 for that. |
I want to indent a project group into a the group above
and it would work. If I try the same on the next grope it will not allow me to indent into the grou above.
ubfortunate I do not get a hint of the case of the issue.
The text was updated successfully, but these errors were encountered: