Fix Jira namespace subscription bug
What does this MR do and why?
It changes the feature flag check to use jira_connect_oauth
instead of jira_connect_oauth_self_managed
. I initially thought the API endpoint will only be used for the jira_connect_oauth_self_managed
feature, but it is already needed for jira_connect_oauth
which is already active on GitLab.com.
Screenshots or screen recordings
We found this bug in a pairing session: https://youtu.be/WRJ0t14zQls?t=972 (internal only)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Andy Schoenen