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

[clintonsteiner]

Jenkins and plugins versions report

Environment

Paste the output here

What Operating System are you using (both controller, and any agents involved in the problem)?

Jenkins LTS latest

Reproduction steps

Running Jira cloud latest - attempt jiraGetIssues Step

Expected Results

Return related jira ticket

Actual Results

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

Anything else?

#740

[rantoniuk]

This was already addressed in #647 and switching to v3 REST API is unrelated. Testing e.g. https://jenkins-jira-plugin.atlassian.net/rest/api/2/project/TESTME/versions on REST API v2 works perfectly fine, so there's something else going on your instance.

See official announcement from Atlassian

Please:

• update the bug report with the plugin versions report as shown in the issue template
• add the relevant logs/stacktrace
• add the pipeline definition code if this is CasC or DSL

[clintonsteiner]

Is there a way to use v3 REST API from the plugin? We are getting rejected on v2 calls

[clintonsteiner]

Find this notice https://community.atlassian.com/forums/Jira-questions/Status-on-the-deprication-of-quot-POST-rest-api-2-3-latest/qaq-p/3105224

[clintonsteiner]

Atlassian announced deprecation of the classic search endpoints (e.g., …/rest/api/2/search and …/rest/api/3/search) in favor of the new “Enhanced JQL” search APIs. As removal rolls out, some sites now return 410 Gone while others still accept the old calls.

You can use /rest/api/3/search/jql (GET or POST). These are the Atlassian-recommended replacements for the old /search endpoints.

[rantoniuk]

Please update the issue with the information I requested above for further investigation.

Is there a way to use v3 REST API from the plugin? We are getting rejected on v2 calls

Since you've marked that you have tested this change with your Jira Cloud instance and it fixed your issue, I'll assume that you've built the custom SNAPSHOT version of the plugin and it works for you. You can continue to use it until an official release is done with a fix (if needed).

If you did not test it, you can use the custom build - from your PR, just fetch the jira-3.20-rc1645.f7154090170e.hpi file and install it on your instance.

[clintonsteiner]

Thanks for the info @rantoniuk I wasn't aware I could do something like that to patch the version in.

Will report back with more information.

[rantoniuk]

Were you able to gather any logs and the plugin versions dump?

[rantoniuk]

From REST API docs

Version 2 and version 3 of the API offer the same collection of operations. However, version 3 provides support for the Atlassian Document Format (ADF)

Also see the community blogpost.

I'm closing it for now, as I don't see anyone else reporting this and no logs and version information was provided.