Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Search API works in one Jira Cloud instance but not in another

sarvesh September 15, 2025

 

We have two Jira Cloud instances. In one instance, the following API works properly:

 

/rest/api/2/search?jql=project={project}&maxResults=100&fields=*all,-comment,-worklog,-issuelinks,-subtasks,-attachment

However, in the second instance the same API does not work. Could you please clarify why there is a difference in behavior between the two Jira Cloud instances?

2 answers

2 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 15, 2025

Hi @sarvesh 

This API endpoint is deprecated and is actively being removed from instances by Atlassian.

See; https://developer.atlassian.com/changelog/#CHANGE-2046 

New API endpoint is: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-get 

2 votes
Mathias Richter
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 15, 2025

Hi @sarvesh - as already discussed in one of your earlier posts, the Search endpoints are deprecated. See: https://developer.atlassian.com/changelog/#CHANGE-2046 - Your instance admin (or you) also got an email about this, also clarifying about the deprecation date, etc.

Not all Jira instances always have the same feature status. Most features and changes are rolled-out in waves. Therefore you might see the endpoint still working in one environment, but this will soon stop working as well. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events