GitLab Issues Link Broken for JIRA Integration
Summary
With JIRA integration enabled, clicking the "Issues" navigation link now goes to a "Project Does Not Exist" on JIRA, instead of the Issues page.
Steps to reproduce
- Enable JIRA integration (https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc//project_services/jira.md) for a project.
- Click on "Issues" navigation link on that project.
- Redirects to https://project.atlassian.net/browse/:id and displays "Project Does Not Exist"
Expected behavior
Should go to the issues URL (ex: https://project.atlassian.net/browse/PROJECT)
Output of checks
Results of GitLab Application Check
Checking GitLab Shell ...
GitLab Shell version >= 3.4.0 ? ... OK (3.4.0)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by gitlab:gitlab?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
2/1 ... ok
4/2 ... ok
3/3 ... ok
3/4 ... ok
3/5 ... ok
3/6 ... ok
2/8 ... ok
14/9 ... repository is empty
20/11 ... ok
30/12 ... ok
14/13 ... ok
14/14 ... ok
14/15 ... ok
14/16 ... ok
19/17 ... ok
21/18 ... ok
15/19 ... ok
2/20 ... ok
14/21 ... ok
14/22 ... ok
24/23 ... ok
23/24 ... ok
38/25 ... ok
14/26 ... ok
2/27 ... ok
27/28 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... 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: ...
2/1 ... yes
4/2 ... yes
3/3 ... yes
3/4 ... yes
3/5 ... yes
3/6 ... yes
2/8 ... yes
14/9 ... yes
20/11 ... yes
30/12 ... yes
14/13 ... yes
14/14 ... yes
14/15 ... yes
14/16 ... yes
19/17 ... yes
21/18 ... yes
15/19 ... yes
2/20 ... yes
14/21 ... yes
14/22 ... yes
24/23 ... yes
23/24 ... yes
38/25 ... yes
14/26 ... yes
2/27 ... yes
27/28 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.1)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.7.4)
Active users: 27
Checking GitLab ... Finished
Results of GitLab Environment Info
System information
System: Ubuntu 14.04
Current User: gitlab
Using RVM: no
Ruby Version: 2.3.1p112
Gem Version: 2.6.6
Bundler Version:2.3.0
Rake Version: 10.5.0
Sidekiq Version:4.1.4
GitLab information
Version: 8.11.0
Revision: 346e677
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://gitlab.ruvilla.com
HTTP Clone URL: https://gitlab.ruvilla.com/some-group/some-project.git
SSH Clone URL: gitlab@gitlab.ruvilla.com:some-group/some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 3.4.0
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks/
Git: /opt/gitlab/embedded/bin/git
Possible fixes
Looks like its not correctly expanding :id