Skip to content

Backend: Create a table for sentry error related issues

Allison Browne requested to merge 37026-backend-create-a-table-for-sentry-error-related-issues into master

What does this MR do?

Overview

This MR adds the data model that will enable us to create a gitlab issue from a sentry issue and then be able to display a formatted sentry stack trace beneath the description, on issues that are created directly from a Sentry Issue(Error).

All of: #37026 (closed). Part of: &2210

Technical Details

Storing the id of the sentry issue that the gitlab issue was created from will allow us to keep track of which Sentry issue the gitlab issue was created from. This will enable us to add features like the ability to resolve an issue in sentry. The issue id is generated in sentry and is typically an int with 10 characters but I decided not to validate length since it looks like it is an auto-incrementing id. We can also use the issue id to query for the most recent stack trace.

A gitlab issue can have only one Sentry issue. Eventually, we will want to have Gitlab issues created in Gitlab as well as Gitlab issues created in Sentry stored within this table.

Naming

There is also a restriction against using _id at the end of columns that are not explicitly foreign keys. Hence the _identifier naming. Open to ideas here.

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • [-] Label as security and @ mention @gitlab-com/gl-security/appsec
  • [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by Allison Browne

Merge request reports