Gantt dependencies not moving

So I don't know if I'm just using it wrong or it just doesn't have this feature... When I link two tasks together (end to start) and the first one is moved or extended the second one does nothing, recalculating also does nothing. Reading the docs made me think the dependent task should move so it's not overlapping but I just can't get it to work that way.

1
5 comments
Official comment
Hi!
 
At the moment, it is considered by default that when you manually extend and move around the issue bars on the board, that means you need these values set in stone, and nothing should be changed when you hit Recalculate.
 
An implied scenario to have that button move the bars around to resolve dependency conflict as regards issue dates can be as follows:
  1. Create issues with their time estimations in a custom field;
  2. Create a Gantt Chart with that field set in the Estimation field;
  3. Add the issues to the sidebar;
  4. Hit Recalculate to have these issues show up on the chart;
  5. Make a dependency link;
  6. If that dependency link is red on the chart due to conflicting dates, hit Recalculate again—in this case, the bars will move as expected.
I hope the above helps to understand the logic currently implemented. You can also take a look at our documentation article for more details on timeline recalculation.
 
Your question highlights a possible usability issue that we will investigate. Feel free to subscribe to our public issue if you like. And if you have any follow-ups, fire away!

That feels really counter-intuitive, if I dependency link tasks then I want them to move together. I can't imagine a situation where I'd want a task to be locked automatically.

I can see the point of fixed-date tasks but I'd like that to be an option that I decide to apply and for it to be very clear visually that it is locked.

I manually placed every task in my Gantt because the order wasn't set and I like to do things visually so it came as a shock that all my dependencies were broken.

0

Hi,

Thank you for your thoughts. I have communicated this to our UX team. Your input will help us when looking for possible approaches here and when we evaluate the overall usability of this feature. 

dependencies were broken

I assume you mean that the issue bars didn’t move around on the board after being placed there manually? If there is something else I’m missing here, please let me know.

1

If I move an issue (by accident), but I wish it not be set in stone, is there something I can do to make it dynamic again with “recalculate”? Or would I have to create it all over again?

0

I'm afraid there is no way to make a “force recalculate” for now. Feel free to vote for the related public feature request: JT-79737.

0

Please sign in to leave a comment.