GitLab does not create link to created Jira issue in vulnerability management

Summary

When creating a vulnerability, GitLab does not link Jira issues in the related issue section. This is intermittent.

I have checked and found a lot of customers experiencing this.

In Zendesk :

I have also checked the Kibana logs, and some customers (internal) are experiencing this.

Steps to reproduce

From the investigation, it seems the Jira rest API, after the issue is created, does not return a valid issue. Hence, GitLab is not able to create_external_issue_link

Stack trace:

"json.exception.backtrace": [
      "lib/gitlab/jira/http_client.rb:15:in `request'",
      "app/models/integrations/jira.rb:366:in `block in find_issue'",
      "app/models/integrations/jira.rb:726:in `jira_request'",
      "app/models/integrations/jira.rb:366:in `find_issue'",
      "ee/app/services/vulnerability_external_issue_links/create_service.rb:100:in `block in remove_links_for_nonexistent_external_issues'",
      "ee/app/services/vulnerability_external_issue_links/create_service.rb:99:in `remove_links_for_nonexistent_external_issues'",
      "ee/app/services/vulnerability_external_issue_links/create_service.rb:20:in `execute'",
      "ee/app/graphql/mutations/vulnerabilities/create_external_issue_link.rb:42:in `create_external_issue_link'",
      "ee/app/graphql/mutations/vulnerabilities/create_external_issue_link.rb:31:in `resolve'",
      "lib/gitlab/graphql/present/field_extension.rb:18:in `resolve'",
      "lib/gitlab/graphql/tracers/instrumentation_tracer.rb:23:in `execute_multiplex'",
      "app/graphql/gitlab_schema.rb:44:in `multiplex'",
      "app/controllers/graphql_controller.rb:269:in `execute_query'",
      "app/controllers/graphql_controller.rb:66:in `execute'",
      "app/controllers/application_controller.rb:493:in `set_current_admin'",
      "lib/gitlab/session.rb:11:in `with_session'",
      "app/controllers/application_controller.rb:484:in `set_session_storage'",
      "lib/gitlab/i18n.rb:116:in `with_locale'",
      "lib/gitlab/i18n.rb:122:in `with_user_locale'",
      "app/controllers/application_controller.rb:475:in `set_locale'",
      "app/controllers/application_controller.rb:464:in `set_current_context'",
      "lib/gitlab/ip_address_state.rb:11:in `with'",
      "app/controllers/application_controller.rb:470:in `set_current_ip_address'",
      "lib/gitlab/middleware/action_controller_static_context.rb:23:in `call'",
      "config/initializers/action_dispatch_journey_router.rb:52:in `block in find_routes'",
      "config/initializers/action_dispatch_journey_router.rb:25:in `map!'",
      "config/initializers/action_dispatch_journey_router.rb:25:in `find_routes'",
      "ee/lib/omni_auth/strategies/group_saml.rb:41:in `other_phase'",
      "lib/gitlab/metrics/elasticsearch_rack_middleware.rb:16:in `call'",
      "lib/gitlab/middleware/sidekiq_shard_awareness_validation.rb:20:in `block in call'",
      "lib/gitlab/sidekiq_sharding/validator.rb:42:in `enabled'",
      "lib/gitlab/middleware/sidekiq_shard_awareness_validation.rb:20:in `call'",
      "lib/gitlab/middleware/memory_report.rb:13:in `call'",
      "lib/gitlab/middleware/speedscope.rb:13:in `call'",
      "lib/gitlab/database/load_balancing/rack_middleware.rb:23:in `call'",
      "lib/gitlab/middleware/rails_queue_duration.rb:33:in `call'",
      "lib/gitlab/etag_caching/middleware.rb:21:in `call'",
      "lib/gitlab/metrics/rack_middleware.rb:16:in `block in call'",
      "lib/gitlab/metrics/web_transaction.rb:46:in `run'",
      "lib/gitlab/metrics/rack_middleware.rb:16:in `call'",
      "lib/gitlab/middleware/go.rb:21:in `call'",
      "lib/gitlab/middleware/query_analyzer.rb:11:in `block in call'",
      "lib/gitlab/database/query_analyzer.rb:83:in `within'",
      "lib/gitlab/middleware/query_analyzer.rb:11:in `call'",
      "lib/ci/job_token/middleware.rb:11:in `call'",
      "lib/gitlab/middleware/multipart.rb:173:in `call'",
      "lib/gitlab/middleware/read_only/controller.rb:50:in `call'",
      "lib/gitlab/middleware/read_only.rb:18:in `call'",
      "lib/gitlab/middleware/unauthenticated_session_expiry.rb:18:in `call'",
      "lib/gitlab/middleware/secure_headers.rb:11:in `call'",
      "lib/gitlab/middleware/same_site_cookies.rb:27:in `call'",
      "lib/gitlab/middleware/path_traversal_check.rb:40:in `call'",
      "lib/gitlab/middleware/handle_malformed_strings.rb:21:in `call'",
      "lib/gitlab/middleware/basic_health_check.rb:25:in `call'",
      "lib/gitlab/middleware/handle_ip_spoof_attack_error.rb:25:in `call'",
      "lib/gitlab/middleware/request_context.rb:15:in `call'",
      "lib/gitlab/middleware/webhook_recursion_detection.rb:15:in `call'",
      "config/initializers/fix_local_cache_middleware.rb:11:in `call'",
      "lib/gitlab/middleware/compressed_json.rb:44:in `call'",
      "lib/gitlab/middleware/rack_multipart_tempfile_factory.rb:19:in `call'",
      "lib/gitlab/metrics/requests_rack_middleware.rb:83:in `call'",
      "lib/gitlab/middleware/sidekiq_web_static.rb:20:in `call'",
      "lib/gitlab/middleware/release_env.rb:12:in `call'"
    ],
    "json.meta.feature_category.keyword": [
      "vulnerability_management"
    ],
    "json.integration_class": [
      "Integrations::Jira"
    ],
   
    "json.client_status.keyword": [
      "404"
    ],
 
    ],
    "json.severity": [
      "ERROR"
    ],
    "json.tier": [
      "sv"
    ],
    "ua_string_base": [
      ""
    ],
    "json.client_path": [
      "/rest/api/2/issue/246799"
    ],
   
    "@timestamp": [
      "2025-06-25T09:35:23.422Z"
    ],
    "json.exception.class": [
      "JIRA::HTTPError"
    ],
   
    "kubernetes.pod_name": [
      "gitlab-webservice-api-5565c8cfb7-pmlzq"
    ],
   
  
  }
}

Example Project

https://log.gprd.gitlab.net/app/r/s/80Kux

What is the current bug behavior?

GitLab does not link to the Jira issue even though it is created.

What is the expected correct behavior?

GitLab should create a link to the Jira issue.

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

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard 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 for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by 🤖 GitLab Bot 🤖