JIRA Integration does not read retrospectively from MR titles

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

Summary

When enabling the JIRA integration, only newly created or updated MRs auto link to the ticket.

Steps to reproduce

  1. Create a merge request on a new project without JIRA integration enabled where the title contains a JIRA ticket number.
  2. Enable JIRA integration for that project.
  3. Visit the merge request page.

What is the current bug behavior?

The title does not automatically link the JIRA ticket number to the JIRA ticket page. By editing the merge request and making any change (even a space at the end of the title) to the title, the link then appears.

What is the expected correct behavior?

Enabling the JIRA integration should automatically include the link to JIRA tickets from the title of a merge request without further intervention.

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:		Ubuntu 18.04
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.6.3p62
Gem Version:	2.7.9
Bundler Version:1.17.3
Rake Version:	12.3.2
Redis Version:	3.2.12
Git Version:	2.22.0
Sidekiq Version:5.2.7
Go Version:	unknown

GitLab information
Version:	12.3.3-ee
Revision:	47e969b011f
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	PostgreSQL
DB Version:	10.9
URL:		https://git.substrakthealth.com
HTTP Clone URL:	https://git.substrakthealth.com/some-group/some-project.git
SSH Clone URL:	git@git.substrakthealth.com:some-group/some-project.git
Elasticsearch:	yes
Geo:		no
Using LDAP:	no
Using Omniauth:	yes
Omniauth Providers: saml


GitLab Shell
Version:	10.0.0
Repository storage paths:
  • default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
Checking GitLab subtasks ...


Checking GitLab Shell ...


GitLab Shell: ... GitLab Shell version >= 10.0.0 ? ... OK (10.0.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK


gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Gitaly ...


Gitaly: ... default ... OK


Checking Gitaly ... Finished


Checking Sidekiq ...


Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1


Checking Sidekiq ... Finished


Checking Incoming Email ...


Incoming Email: ... Reply by email is disabled in config/gitlab.yml


Checking Incoming Email ... Finished


Checking LDAP ...


LDAP: ... LDAP is disabled in config/gitlab.yml


Checking LDAP ... Finished


Checking GitLab App ...


Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
7/1 ... yes
7/2 ... yes
7/3 ... yes
2/4 ... yes
2/6 ... yes
2/7 ... yes
7/8 ... yes
7/9 ... yes
2/10 ... yes
7/11 ... yes
7/12 ... yes
7/13 ... yes
7/14 ... yes
5/15 ... yes
7/16 ... yes
7/17 ... yes
8/18 ... yes
7/19 ... yes
7/20 ... yes
7/21 ... yes
7/23 ... yes
7/24 ... yes
7/25 ... yes
7/26 ... yes
7/27 ... yes
7/28 ... yes
7/29 ... yes
7/30 ... yes
7/31 ... yes
7/32 ... yes
7/33 ... yes
7/34 ... yes
7/35 ... yes
7/36 ... yes
7/37 ... yes
7/38 ... yes
7/39 ... yes
7/40 ... yes
7/41 ... yes
7/42 ... yes
7/43 ... yes
7/45 ... yes
23/46 ... yes
19/47 ... yes
23/48 ... yes
23/49 ... yes
7/50 ... yes
7/51 ... yes
19/52 ... yes
19/53 ... yes
7/54 ... yes
2/55 ... yes
7/56 ... yes
7/57 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.3)
Git version >= 2.22.0 ? ... yes (2.22.0)
Git user has default SSH configuration? ... yes
Active users: ... 12
Is authorized keys file accessible? ... yes
Elasticsearch version 5.6 - 6.x? ... yes (6.5.4)


Checking GitLab App ... Finished

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited by 🤖 GitLab Bot 🤖