Bidirectional sync via webhooks. GitLab issues create Huly issues. Merge requests link to related Huly items. Commits reference Huly issues. Everything stays current automatically.
Your developers work in GitLab but project managers track work in Huly. Issues, merge requests, and commits happen in GitLab but the status in Huly is always stale.
Bidirectional sync via webhooks. GitLab issues create Huly issues. Merge requests link to related Huly items. Commits reference Huly issues. Everything stays current automatically.
Configure GitLab webhooks to point to the sync service
Issues created/updated in GitLab sync to Huly projects
Merge requests and commits reference Huly issues via branch names
Priority and status mapping keeps both systems consistent
Here's what it looks like in action:
Issues flow both ways. Create in GitLab, see it in Huly. Update in either, both stay current.
Merge requests automatically link to related Huly issues based on branch name patterns.
GitLab comments appear in Huly and vice versa. One conversation, two platforms.
Real-time via webhooks, plus periodic full sync to catch anything webhooks missed.
Full source code, Dockerfile, docker-compose.yml, README, email support
⚠️ Requirements: Huly (any current version), GitLab instance with API access
Both. Any GitLab instance with API access.
No. One-time purchase.
Questions? Email [email protected] · 14-day money-back guarantee