Jira Integration: Deprecated API Returning 410 Gone

Atlassian has deprecated the /rest/api/2/search endpoint on Jira Cloud (CHANGE-2046), breaking several GitLab features.

We need to switch to the new /search/jql endpoint.

This seems to be causing 410 (Gone) errors for some customers when the Issue Finder attempts to retrieve issues from Jira. Other functions may stop working in the future as well.

Affected functionality

This issue only affects some of the functions of the Jira issues integration when using Jira Cloud:

• ✅ GitLab can still add web links and comments to Jira issues when a Jira issue ID is mentioned (this is the main function of the integration)
• ✅ GitLab will still cross link Jira issues
• ❌ You won't be able to view Jira issues in GitLab (this was the API endpoint that had to be changed for Jira Cloud)
• ✅ GitLab can still create Jira issues from vulnerabilities
• ❌ GitLab won't be able to show the Jira issue that was created from a GitLab vulnerability

Error and screenshots

User action	Error shown	Screenshot
Jira issues cannot be viewed in GitLab	Something went wrong while trying to fetch related Jira issues. Please check the Jira integration settings and try again.
Jira issues created from GitLab vulnerabilities won't appear in GitLab, even if they already exist	An error occurred while requesting data from Jira. Check your Jira integration configuration and try again.

Links

gitlab-com/request-for-help#3396