feat(gitlab): add inbound/outbound assignment & comment support#105472
Merged
GabeVillalobos merged 2 commits intomasterfrom Jan 29, 2026
Merged
feat(gitlab): add inbound/outbound assignment & comment support#105472GabeVillalobos merged 2 commits intomasterfrom
GabeVillalobos merged 2 commits intomasterfrom
Conversation
github-actions
bot
added
the
Scope: Backend
iamrajjoshi
force-pushed
the
raj/gitlab-feat-par/assgn-comments
branch
from
6f88618 to
c3e315e
Compare
Comment on lines
+92
to
+98
| provider = EXTERNAL_PROVIDERS_REVERSE[ExternalProviderEnum(self.model.provider)].value | ||
| external_actor = ExternalActor.objects.filter( | ||
| provider=provider, | ||
| user_id=user.id, | ||
| integration_id=external_issue.integration_id, | ||
| organization=external_issue.organization, | ||
| ).first() |
Member
There was a problem hiding this comment.
This logic seems so common between our providers, that I'm wondering if we have a way to abstract this out further. Just a thought.
Collaborator
Author
There was a problem hiding this comment.
good call - i didn't do it originally since i hadn't run into multiple examples till now. we can def have separate utils for this which can be a followup.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
iamrajjoshi
force-pushed
the
raj/gitlab-feat-par/assgn-comments
branch
from
f34a022 to
2641751
Compare
iamrajjoshi
force-pushed
the
raj/gitlab-feat-par/assgn-comments
branch
from
2641751 to
06b22e3
Compare
iamrajjoshi
force-pushed
the
raj/gitlab-feat-par/assgn-comments
branch
from
06b22e3 to
b1f6462
Compare
iamrajjoshi
added
the
Trigger: getsentry tests
GabeVillalobos
approved these changes
Jan 26, 2026
iamrajjoshi
force-pushed
the
raj/gitlab-feat-par/assgn-comments
branch
from
b1f6462 to
837630d
Compare
iamrajjoshi
force-pushed
the
raj/gitlab-feat-par/assgn-comments
branch
from
837630d to
f08399f
Compare
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
iamrajjoshi
force-pushed
the
raj/gitlab-feat-par/assgn-comments
branch
from
f08399f to
a0c6b31
Compare
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 4 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
priscilawebdev
pushed a commit
that referenced
this pull request
Feb 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Take 2 because of #103877
This PR adds inbound/outbound assignment and comment synchronization support between Sentry and GitLab issues.
It is gated behind
organizations:integrations-gitlab-project-managementflag.Comment Syncing
gitlab-comments.mov
Outbound Assignment Sync
gitlab-outbound.mov
Inbound Assignment Sync
gitlab-inbound.mov
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.