Option to set issue creator in GitLab integration

[Fabien4941]

Hello Sentry team,

Problem statement

Currently, when issues are created in GitLab via Sentry, they are always created under the administrator's username who set up the integration. This leads to confusion in issue tracking and incorrect notifications, as the real creators of the issues are not correctly assigned.

Solution brainstorm

Provide an option to set the issue creator in the GitLab integration settings. Ideally, the issues should be created by the user who initiated the issue creation in Sentry, or at least allow for a bot user to be assigned as the creator.

Product area

Settings - Integrations

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-settings-integrations for triage ⏲️

[Dhrumil-Sentry]

Thanks for this feedback, Adding this to our backlog but we don't expect we'll work on this soon

[Fabien4941]

Dear Sentry Team,

I wanted to follow up on this issue as it continues to significantly impact our workflows.

Since we initially reported this problem, we have found no viable workaround. The suggested solution of reinstalling the integration under a different user is not feasible for us because it would sever all existing links between Sentry events and GitLab issues. This loss of historical data is unacceptable and would disrupt our issue tracking processes.

The inability to set the issue creator in the GitLab integration means that all issues created via Sentry are attributed to the administrator who set up the integration.

This misattribution leads to several problems:

• Confusion in Issue Tracking: Team members cannot identify the actual reporters of issues, leading to delays and inefficiencies in addressing them.
• Incorrect Notifications: The administrator receives all notifications for issues they did not create, while the actual creators may miss important updates.
• Inaccurate Reporting: Our metrics and analytics on issue creation and resolution are skewed due to incorrect attribution.
  Impact on Our Operations:

This issue has been ongoing for over six months and continues to hinder our team's productivity. Proper attribution of issues is crucial for efficient collaboration and accurate reporting.

We understand that the development team has other priorities, but we kindly ask if there has been any progress on this issue or if it could be reconsidered for prioritization. The resolution of this problem would greatly enhance our use of Sentry in conjunction with GitLab and benefit other users facing similar challenges.

If there are any interim solutions or if there's any way we can assist in testing potential fixes, we would be happy to help.

Thank you for your attention to this matter, and we look forward to any updates you can provide.