<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/201672, we changed the way we fetch related Jira issues for vulnerabilities: ```diff --- a/ee/app/services/jira/jql_builder_service.rb +++ b/ee/app/services/jira/jql_builder_service.rb @@ -105,7 +105,7 @@ def by_vulnerability_ids return if vulnerability_ids.blank? vulnerability_ids - .map { |vulnerability_id| %(description ~ "/-/security/vulnerabilities/#{escape_quotes(vulnerability_id.to_s)}") } + .map { |vulnerability_id| %(description ~ "#{escape_quotes("\"Issue created from vulnerability #{vulnerability_id}\"")}") } .join(' OR ') .then { |query| "(#{query})" } end ``` Our documentation for [linking a vulnerability to existing Jira issues ](https://docs.gitlab.com/user/application_security/vulnerabilities/#link-a-vulnerability-to-existing-jira-issues) uses the older string that was changed in the MR above. We have users that automate the linking of their Jira issues outside of GitLab, so the MR has now broken that workflow. ### Steps to reproduce 1. Follow the [linking a vulnerability to existing Jira issues ](https://docs.gitlab.com/user/application_security/vulnerabilities/#link-a-vulnerability-to-existing-jira-issues) instructions 2. View the vulnerability in GitLab, it won't work ### Example Project N/A ### What is the current *bug* behavior? Using `/-/security/vulnerabilities/<vulnerability_id>` in a Jira issue doesn't link it to a GitLab vulnerability. ### What is the expected *correct* behavior? Using `/-/security/vulnerabilities/<vulnerability_id>` in a Jira issue should link it to a GitLab vulnerability. ### Relevant logs and/or screenshots <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> ### Output of checks <!-- If you are reporting a bug on GitLab.com, uncomment below --> <!-- This bug happens on GitLab.com --> <!-- and uncomment below if you have /label privileges --> <!-- /label ~"reproduced on GitLab.com" --> <!-- or follow up with an issue comment of `@gitlab-bot label ~"reproduced on GitLab.com"` if you do not --> #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (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`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (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) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. --> ### Patch release information for backports If the bug fix needs to be backported in a [patch release](https://handbook.gitlab.com/handbook/engineering/releases/patch-releases) to a version under [the maintenance policy](https://docs.gitlab.com/policy/maintenance/), please follow the steps on the [patch release runbook for GitLab engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/patch/engineers.md). Refer to the [internal "Release Information" dashboard](https://dashboards.gitlab.net/d/delivery-release_info/delivery3a-release-information?orgId=1) for information about the next patch release, including the targeted versions, expected release date, and current status. #### High-severity bug remediation To remediate high-severity issues requiring an [internal release](https://handbook.gitlab.com/handbook/engineering/releases/internal-releases/) for single-tenant SaaS instances, refer to the [internal release process for engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/internal-releases/engineers.md?ref_type=heads). <!-- If you don't have /label privileges, follow up with an issue comment of `@gitlab-bot label ~"type::bug"` -->