Jira Story ID Hyperlinks not returned with API results

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

Summary

When Jira is integrated with GitLab, hyperlinks are created in Issues, MR's, Commits, and Branches, that link these GitLab objects to the Jira story ID with a hyperlink. The hyperlink provides a fast convenient way to jump to the story in Jira. Customers wishing to leverage the APIs for those objects to retrieve the data from them, and use that data for reporting compliance needs, the hyperlinks are missing from the data retrieved.

Steps to reproduce

  1. Integrate Jira with GitLab
  2. Create a story in a board within Jira and capture the Story ID
  3. In GitLab create an Issue, MR, branch, commit and preface the title of those with the Jira Story ID.
  4. Using each of the APIs below, retrieve the data for each object, where the Jira Story ID is listed, but the hyperlinks are missing.
    • List Issues
    • List project issues
    • List group issues
    • Get single issue
    • List merge requests
    • List project merge requests
    • List group merge requests
    • Get single merge request
    • List repository branches
    • Get single repository branch
    • List repository commits
    • Get single repository commit

Example Project

I do have a project that I can link here, its not public, but would be happy to invite whomever to the project to look at it.

What is the current bug behavior?

Jira Story ID hyperlinks are not provided when retrieving the data for Issues, MR's branches and commits using the APIs listed above.

What is the expected correct behavior?

Jira Story ID hyperlinks are provided when retrieving the data for Issues, MR's branches and commits using the APIs listed above.

Relevant logs and/or screenshots

Here's a screenshot for getting a list of commits, where you can see in the "title", the LD-33 which is the Jira Story ID without its hyperlink.

Screenshot_2022-12-16_at_4.42.14_PM

Here's a screenshot of the same commit in the UI where the LD-33 is hyperlinked.

Screenshot_2022-12-16_at_4.44.36_PM

Output of checks

This is happening on gitlab.com and I assume will also happen on self-managed as they're the same APIs used for both.

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 🤖