Skip to main content
Question

SCC Enterprise – SyncSCCJiraTickets job failing with HTTP 410 (REST API v2 /search removed)

  • March 31, 2026
  • 0 replies
  • 2 views

Forum|alt.badge.img+1

Integration version: SCCEnterprise_V18.0
Platform: Google SecOps SOAR (Siemplify)
Jira: Atlassian Cloud

Problem

The SCC Enterprise - SyncSCCJiraTickets job fails on every execution with an HTTP 410 error when attempting to search for Jira issues:

JiraError HTTP 410

url: https://<tenant>.atlassian.net/rest/api/2/search?jql=...

text: The requested API has been removed. Please migrate to the /rest/api/3/search/jql API.

 

Atlassian has permanently removed the /rest/api/2/search endpoint on Cloud tenants. The integration is hardcoded to use API v2 and does not fall back to v3.

Steps to reproduce

1. Install SCC Enterprise V18.0 on Google SecOps SOAR
2. Configure the SyncSCCJiraTickets job against an Atlassian Cloud Jira instance
3. Run the job, it fails immediately after fetching create issue metadata

Expected behavior

The job should query Jira using the current /rest/api/3/search/jql endpoint.

Question

Is there a newer version of the SCC Enterprise integration that has been updated to use Jira REST API v3? If not, is there a workaround or a planned fix? Thanks.