In this case, you can just make a rest call to this endpoint, if you don't specify any JQL parameter here, it's the same as if you searched in the issue navigator in Jira and left the advanced search field empty; it returns all the issues that this user has access to.
Cloud example using curl
curl --request GET \
--url '/rest/api/3/search' \
--header 'Authorization: Bearer ' \
--header 'Accept: application/json'
Server example using curl
curl -D- -u username:password -X GET \
-H "Content-Type: application/json" \
For other users that come across this, I hope this helps.
Some Jira sites will not return all issues when you use a blank JQL query. But then again some will. It has become an administrator setting that can be helpful to improve overall performance. Instead of using that query, try to at least enter something in the JQL, such as 'Order by created'
Which should work on any Jira site regardless of that setting.
If you still get back 0 results, then either there are no issues there, or your account is not authenticated, or the account you have authenticated with cannot see any issues yet.
There is still a search endpoint you can use, even in Jira Cloud v3 of the REST API. I have linked to the reference guide in my original answer.
(for Cloud GET /rest/api/3/search)
This is still accurate for Jira Cloud today. Please let me know if you run into any problems with this.
I might have been unclear, sure there's a search, but what you get is a list of issueids, not the actual issues.
If we were to download all issues in a jira instance it would take hours to loop through every id and make an API-call.
Add to that making extra calls per issue to get all the fields for each issue.
Why isn't there a quicker get-all-issues feature? why have to loop through every single one "by hand".
Thanks for clarifying. The documentation of the search endpoint note that:
Note: All navigable fields are returned by default. This differs from GET issue where the default is all fields.
Have you tried to use the query parameters in that endpoint GET /rest/api/3/search such as fields=*all ? This will let you not only return the issues in the search, but all the fields of those issues as well. Perhaps this is the missing piece you are looking for.
So yes, you could use the GET issue endpoint and loop through it to get all the issues, but I think using an empty JQL search that returns all issues your account can view would probably be easier to accomplish in a single call. And you can get back all the fields if you pass it the right parameters. You might also want to use the expand=names in order to see the names of all those custom fields in the results.
I suspect here is not a get-all-issues type endpoint because the search endpoint can be made to perform this same function depending on the parameters passed to it.
Does that help more than the previous answers here? Please let me know,
I am executing issues api to get issues against a jql. Jira ui is showing issue count is 4890 but getting 4679 as unique records via rest api.
Can somebody please help me , why i am getting duplicate keys in jira rest response.
Is there any plugin creating a problem or cloning an issue is causing this delicacy.
Appreciate urgent help.
@Yuvam Jain There are a few different possible scenarios that can account for this here. But they vary depending on your platform for Jira (Server, Data Center, or Cloud).
The most common answer is that you're using a different account in REST API than you are in the web interface. JQL searches are user dependent. Meaning different users can run the same JQL and get back different results depending on which issues they have permissions to see (technically you need both permissions AND issue level security in order to see an issue).
If you're using the same account, then there are other possible causes here, such as the syntax of the JQL, or indications of an indexing problem in Jira, or even possibly stale replications between data center nodes (last one only applies to data center).
If you were in Server or Data Center, you could query the SQL database directly to find the issue count with a SQL query of:
select count(*) from jiraissue;
This returns the total number of issues regardless of your Jira permissions to see them.
If you're using Jira Cloud, then you might want to reach out to your site-admin to first figure out if there is a difference between your account and the one you're using for the REST API call here. If not, then perhaps your site-admin can create a support case with Atlassian in order to investigate the details of your Jira issue data here further.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events