@stanhu we’re hoping to move all capable integrations to OAuth in the future (GitLab included), and once we do that it will become very easy to associate the Sentry user with the GitLab user.
The labels and user assignment might be pretty easy. Will definitely explore it. We had some issues with linking issues as GitLab doesn’t expose any search endpoints for them, and that possibly could be an issue with assignment but will give it a look.
The problem is its not overly useful to know when an issue is closed in an external tracker. We can’t really make assumptions about what that means, and often it simply means “I’ve committed the fix”. While “Resolved in Next Release” could work there, its not a guarantee, thus weve made the decision to avoid duct taping that until we have more accurate data.
I hope you’ll appreciate when I say we don’t follow what others do – after all, we’ve been the leader in this space long before other projects even existed. We also are very adamant about doing this correctly and we have an upcoming solution which doesn’t have the same issues I described above. I don’t know when it’ll be available publicly, but it’s part of a bigger push to add commit data into the system. Right no we’re prototyping it with GitHub, but GitLab had all the same hooks so I don’t foresee any issues there.
