Jira issue regex settings do not link valid Jira issue IDs back to Jira
Summary
Reproduced on GitLab.com 16.1.0-pre 79841ad1f80
When configuring the Jira issue matching settings in the Jira issue integration and you set a valid regular expression in the Jira issue regex box, the regular expression doesn't actually work. Any Jira issue IDs that match the regular expression are not autolinked to the relevant issue in Jira.
Steps to reproduce
-
Enable the Jira integration in one of your projects.
- For the Jira issue matching regular expression, use
[PS]{2,}-\d+
. This should match up withPS-1
for example.
- For the Jira issue matching regular expression, use
-
Ensure that issue
PS-1
exists on the Jira end -
Open a GitLab issue and reference the Jira issue
PS-1
. You should observe that GitLab does not link back to the Jira issue. -
Remove the Jira issue matching setting and repeat the last test. You should observe that GitLab does link back to the Jira issue.
I should note I performed the same reproduction steps on a GitLab 16.0.1-ee
instance and the regex worked there so something has changed recently in the code on GitLab.com. This is a potential regression.
Example Project
anton-jira/413740-jira-regex-test#1
See the issue comments for the reproduction test results
What is the current bug behavior?
The Jira issue regex settings don't seem to work and don't add a link back to the respective Jira issue
What is the expected correct behavior?
The Jira issue regex settings should work and add a link back to the respective Jira issue
Relevant logs and/or screenshots
See example issue above
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)