Skip to content

[Bug][Jira] Integration fails due to deprecated /api/2/search endpoint (HTTP 410) #8544

@tc-jason-gregory

Description

@tc-jason-gregory

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

The DevLake Jira data collection is failing because it's using the deprecated /api/2/search API endpoint that Atlassian has removed.

Error Details:

  • HTTP Status: 410 Gone
  • Error Message: "The requested API has been removed. Please use the newer, enhanced search-based API instead"
  • Affected Operation: subtask collectEpics failing after 3 retries

Sample Error Log:
subtask collectEpics ended unexpectedly Wraps: (2) | Retry exceeded 3 times calling api/2/search. The last error was: Http DoAsync error calling [method:GET path:api/2/search query:map]. Response: {"errorMessages":["The requested API has been removed. Please use the newer, enhanced search-based API instead. Deprecation details are available at [https://developer.atlassian.com/changelog/#CHANGE-2046."],"errors":{](https://developer.atlassian.com/changelog/#CHANGE-2046.%22%5D,%22errors%22:%7B)}} (410)

What do you expect to happen

Jira data collection should complete successfully and retrieve issue data without API errors. The system should use the current supported Jira REST API endpoints for searching issues.

How to reproduce

  1. Configure DevLake with a Jira data source
  2. Run data collection that includes epic collection (collectEpics subtask)
  3. Observe the collection fails with HTTP 410 errors
  4. Check logs for /api/2/search endpoint calls
  5. Error occurs consistently on any Jira instance due to deprecated API usage

Environment where reproduced:

  • Any Jira Cloud
  • DevLake attempting to collect Jira data
  • Issue occurs during epic collection phase

Anything else

Root Cause: DevLake is calling the deprecated /api/2/search endpoint instead of the current Jira REST API search endpoint.

Impact:

  • High severity - Complete failure of Jira data collection
  • Affects all Jira integrations using this endpoint

References:

Suggested Fix:
Update the Jira plugin to use the current search API endpoint and ensure JQL queries and authentication methods are compatible.

Version

v1.0.3-beta1@2ef56cf

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

Labels

component/pluginsThis issue or PR relates to pluginsseverity/p0This bug blocks key user journey and functiontype/bugThis issue is a bug

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions