-
Notifications
You must be signed in to change notification settings - Fork 105
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
Dependency Tracking - date not change #27
Comments
You can't automatically move the end date before the start date, which is what I think you are suggesting. It would not make a lot of sense. Can you perhaps provide some screen shots? |
Can you provide a screenshot of the Dependencies tab for the parent and child tasks? |
You haven't set any dependencies so it won't change anything. In the Dependencies tab you will see to the left the list of tasks you can depend upon and on the right the list that are dependencies. You can move items from one window to the other by clicking on the name and using the two buttons |
Ok I know this solution, but for this solution : we most see in 00-01-01 in the dependencies page tasks 00-01-02. But we don't see therfore we can't add. |
Sorry my english, Ok I know this solution, but for this solution : we must see in 00-01-02 in the dependencies page left side of tasks 00-01-01. But we don't see therfore we can't add. |
If you want to try yourself on our server we will send link and user name and password. |
First, you need to turn on dependency tracking - otherwise nothing happens. Then you probably are looking to set the parent task to "Dynamic Task", then it will change based upon its children - dependencies are setting up a relation outside of parent/child. |
Thanks a lot. It's solved. |
When we are update subtask new date (for example 1 week after) the main task start date automatically chaning. But if we will update subtask old date (for example change date 2 weeks ago) the main task date not chaning.
How we can fix this ?
Can you help us ?
Thanks.
The text was updated successfully, but these errors were encountered: