The Deprecated JQL search endpoints for issue, will these be supported for any old JIRA version?

[genuser_service]

According to this article, https://developer.atlassian.com/changelog/#CHANGE-2046

the following APIs will be deprecated.

• GET /rest/api/2|3|latest/search 

• POST /rest/api/2|3|latest/search

• POST /rest/api/2|3|latest/search/id

• POST /rest/api/2|3|latest/expression/eval

I want to know whether these old APIs can be used by any old JIRA versions. Or will it be deprecated permanently for all versions of JIRA?

As we've been using the following GET API for issues.
GET /rest/api/2/search

If it is deprecated for all versions then we can completely discard this old API and add support for new API.
But if any old/legacy JIRA version still uses this API then we might have to keep supporting it.
So that is why I want clarity on it.

AS the article doesn't mention about JIRA versions support for old and new APIs.

[Evgenii · Accepted solution]

Hi, @genuser_service 

Welcome to Atlassian Community.

The deprecation notice you mentioned refers specifically to the Jira Cloud platform. As of now, the old endpoints are no longer functional in Jira Cloud.

However, this change does not affect on-premise Jira Server or Data Center instances. If your product also integrates with these versions, you must continue supporting the legacy search methods used by them.

In short: if your product works exclusively with Jira Cloud, you can stop supporting the old search methods. If it also supports Jira Server or Data Center, you should retain support for those methods — and implement logic to detect the environment type and use the appropriate API accordingly.

[genuser_service]

Okay, thanks for the quick response.
Yes my doubt was wrt Jira Cloud only.

So our JIRA cloud version is 1001.0.0-SNAPSHOT.
So no matter what version of JIRA Cloud we are using we don't need to support the old API, Am I right?

[Evgenii]

Exactly.

Suporting it doesn't have sense, because Atlassian "turns off" old endpoints.

[Sunny Ape · Accepted solution]

Hello @genuser_service 

You have tagged your question as relating to Jira Cloud

When you open CHANGE-2046,you will see at the top of the change notice the product tag:

That lets everyone know which product the change applies to... the Jira CLOUD platform

Also, when you click the 'More details' button, you'll see more tags that let you know what the change applies... the Jira CLOUD platform's REST API:

So, this can be taken to mean the change has nothing at all to do with the Jira DATA CENTER product, any version of that product, or what you have referred to as "any old/legacy JIRA version"