Merge request don't understand Jira-ID and not hyperlinks Jira-ID in commit title

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Merge request don't understand Jira-ID and not hyperlinks Jira-ID in commit title

Steps to reproduce

  • Create a new MR with Jira-ID in MR title and commit title
  • Gitlab only understand Jira-ID in MR and hyperlinks Jira-ID in MR
  • Gitlab don't understand Jira-ID in commit tittle and not hyperlinks Jira-ID in commit tittle
  • When MR's merged, Jira doesn't mention this commit (Jira only mention MR)

What is the current bug behavior?

What is the expected correct behavior?

Gitlab need to understand Jira-ID and hyperlinks Jira-ID in commit tittle - So that, when MR's merged, commit will be in Jira

Relevant logs and/or screenshots

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)

Possible fixes

Edited by 🤖 GitLab Bot 🤖