[JIRA Development Panel] Jira unable to detect new branch created by terminal if branch name does not start with Jira issue

Summary

If we create a new branch locally that does not start with Jira issue, example: feature_TEST-1-jira it will not be detected in the Jira issue. Creating a new branch in the UI with the same name works.

Issue report by Customer via Internal ticket

Steps to reproduce

1. Clone repository locally
2. Create a new branch that does not start with Jira issue, example: feature_TEST-1-jira
3. Push new branch
4. Refresh Jira issue
5. Observer no new branches show up in the Development Panel
6. Repeat steps but create branch with the same name via GitLab UI.
7. The new branch should show up.

What is the current bug behavior?

The branch mentioning the Jira issue does not appear in the Jira issue.

What is the expected correct behavior?

The branch should be shown in the issue regardless if the branch is create in terminal or UI.

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

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)

Possible fixes