summaryrefslogtreecommitdiff
path: root/app/services/error_tracking/issue_details_service.rb
diff options
context:
space:
mode:
Diffstat (limited to 'app/services/error_tracking/issue_details_service.rb')
-rw-r--r--app/services/error_tracking/issue_details_service.rb26
1 files changed, 25 insertions, 1 deletions
diff --git a/app/services/error_tracking/issue_details_service.rb b/app/services/error_tracking/issue_details_service.rb
index 0068a9e9b6d..1614c597a8e 100644
--- a/app/services/error_tracking/issue_details_service.rb
+++ b/app/services/error_tracking/issue_details_service.rb
@@ -8,7 +8,7 @@ module ErrorTracking
private
def perform
- response = project_error_tracking_setting.issue_details(issue_id: params[:issue_id])
+ response = find_issue_details(params[:issue_id])
compose_response(response) do
# The gitlab_issue attribute can contain an absolute GitLab url from the Sentry Client
@@ -36,5 +36,29 @@ module ErrorTracking
def parse_response(response)
{ issue: response[:issue] }
end
+
+ def find_issue_details(issue_id)
+ # There are 2 types of the data source for the error tracking feature:
+ #
+ # * When integrated error tracking is enabled, we use the application database
+ # to read and save error tracking data.
+ #
+ # * When integrated error tracking is disabled we call
+ # project_error_tracking_setting method which works with Sentry API.
+ #
+ # Issue https://gitlab.com/gitlab-org/gitlab/-/issues/329596
+ #
+ if project_error_tracking_setting.integrated_client?
+ error = project.error_tracking_errors.find(issue_id)
+
+ # We use the same response format as project_error_tracking_setting
+ # method below for compatibility with existing code.
+ {
+ issue: error.to_sentry_detailed_error
+ }
+ else
+ project_error_tracking_setting.issue_details(issue_id: issue_id)
+ end
+ end
end
end