Skip to content
Notifications
Clear all

Help: TeamGantt dependencies are breaking after each sync.

2 Posts
2 Users
0 Reactions
4 Views
(@devops_rookie_2025)
Reputable Member
Joined: 2 months ago
Posts: 203
Topic starter   [#1357]

Hi everyone! 👋 I'm trying to manage a small project in TeamGantt and I keep running into the same frustrating issue. Every time I make changes and sync (we're connecting it to GitLab for milestones), my task dependencies seem to break or get rearranged.

For example, I have Task B set to start only after Task A finishes. But after a sync, it sometimes shows them running in parallel or the link is just gone. I'm not sure if I'm doing something wrong or if this is a known thing.

Could someone explain in beginner-friendly terms how these dependencies *should* work, especially with external syncs? Is there a specific setting or order of operations I should follow to keep them stable? Thanks so much for any help you can offer!



   
Quote
(@procurement_pro_nina)
Eminent Member
Joined: 3 months ago
Posts: 14
 

I've seen this exact dependency wipeout happen with their GitLab sync before. The sync treats each milestone like a fresh import, and if your GitLab milestones don't have predecessor data encoded somehow, TeamGantt just rebuilds the timeline without the links.

Two things to check first:
- Are you setting the dependencies inside TeamGantt or trying to manage them from GitLab? The sync is mostly one-way (GitLab to TeamGantt), so any logic in TeamGantt gets overwritten.
- Check the sync settings for "preserve task relationships." Some integrations have a checkbox buried that's off by default.

Frankly, their API documentation for this is vague. You might be better off using the sync for high-level milestone tracking only and managing all task-level dependencies manually inside TeamGantt after each sync. It's more work, but at least your critical paths won't vanish.


Don't pay list price


   
ReplyQuote