如何实现Upsource评论与GitLab讨论同步？

Hey there, let's work through this comment sync issue step by step—this is a common gotcha with Upsource-GitLab integrations, so we’ll start with the most likely fixes first:

1. Double-Check GitLab OAuth Scopes #

The #1 reason comments fail to sync back is insufficient OAuth permissions. Upsource needs write access to your GitLab merge requests to post comments. Here’s how to verify:

• Go to your GitLab instance → Settings → Applications
• Find the Upsource OAuth application you created
• Ensure the scope list includes write_merge_requests (or the broader api scope, if you don’t mind more permissive access)
• Save changes, then go back to Upsource’s VCS integration settings and re-authenticate to refresh the token

2. Enable Comment Sync in Upsource Repository Settings #

It’s easy to miss this toggle—Upsource doesn’t always enable two-way sync by default:

• Open your Upsource project → Project Settings → VCS Integration
• Select your linked GitLab repository
• Look for an option like "Send comments to VCS" or "Sync Upsource comments to GitLab merge requests" and make sure it’s toggled on
• Verify the setting applies to all comment types (not just code reviews, but general MR comments too)

3. Confirm Network Access Between Upsource and GitLab #

If your GitLab is self-hosted, Upsource’s server needs unrestricted access to GitLab’s API endpoint:

• On the Upsource server, run a test curl command to check connectivity:

  curl https://your-gitlab-url.com/api/v4/projects/[your-project-id]/merge_requests/[test-mr-id]/notes
  

• If you get a 403/404 error, check firewalls, proxy settings, or GitLab’s IP allowlist to ensure Upsource can reach it

4. Verify Merge Request Linking #

Upsource needs to correctly map its MRs to GitLab’s:

• Open an active MR in Upsource
• Check the top of the page for a direct link to the corresponding GitLab MR—click it to confirm it lands on the right page
• If the link is missing or incorrect, re-link the repository in Upsource’s VCS settings, or manually associate the MR using GitLab’s MR ID

5. Check Version Compatibility #

Older versions of Upsource might not support newer GitLab API endpoints for comment posting:

• Cross-reference your Upsource and GitLab versions against JetBrains’ official compatibility matrix (you can find this in Upsource’s documentation)
• If your versions are mismatched, consider upgrading Upsource to a release that explicitly supports your GitLab version

6. Dig Into Upsource Logs for Errors #

If all else fails, the logs will tell you exactly what’s breaking:

• Navigate to your Upsource installation directory → logs folder
• Look for files like upsource.log or vcs-integration.log
• Search for keywords like "GitLab", "comment sync", or "API error"—you’ll see specific issues like expired tokens, missing permissions, or invalid MR IDs

7. Re-Authenticate the Integration #

Sometimes OAuth tokens silently expire or become invalid:

• In Upsource’s VCS Integration settings, disconnect the GitLab link
• Re-authorize the integration using your GitLab credentials to generate a fresh token

Start with the OAuth scopes and Upsource sync toggle—those fix 80% of these issues. If you hit a specific error in the logs, feel free to share it and we can narrow it down further.

内容的提问来源于stack exchange，提问作者Vadim Salajan