Gitlab issue link in Error Tracking details does not support global Sentry integration
Summary
There are two GitLab integrations in Sentry. One is the per-project integration, and the other is the global integration. It is possible to create links to GitLab issues via both integration types.
Our Error Details page only supports the per-project integration.
Note: The per-project integration is marked as deprecated in Sentry v10.
Steps to reproduce
- Set up the global GitLab integration in Sentry.
- Link a Sentry error to a GitLab issue.
- Set up the Sentry integration in GitLab.
- Navigate to the Error tracking page.
- Open the GitLab details page for the Sentry error in (2.)
Example Project
TBD
What is the current bug behavior?
The GitLab issue link is displayed.
What is the expected correct behavior?
No GitLab issue link is displayed.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
This is related to the mention here - support for both plugin types is being added to another feature. - #37307 (comment 273507289).
To fix this we need to add support for both GitLab integrations in Sentry (or at minimum, the global integration). This will require backend changes - to allow for both plugin setups / data structures.