Trying to fetch all Service desk issues using rest API endpoint search but this endpoint is not returning all the results. The total number of issues is way less. Is there a different endpoint for service desk or do we need different permissions on the project since the service account is a user in Service Desk project.
Hi @Madhav Dube ,
The results of the REST API are paginated. Standard you will only get 50 results back and the response will also tell you how many results there are. So you can use this to get the next 50 results.
See https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#expansion
* Updated the link
Thanks, @Rudy Holtkamp Yes I am aware of paginated results as I am pulling the same rest endpoint for extracting data for another project as well. The total I am referring to here is the total issues after dealing with pagination.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The account (and API key) you are using must have the appropriate permissions. You should check if it has the correct JSM license, the correct role to see all issues you are searching for. Perhaps there is a security level set?
You better run the search with the same account in the UI and see what issues you are missing. With the permission helper you might be able to figure out where it goes wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So we are using Service account and I might not have access to service desk. Can you help me with the permissions it needs to view everything and I'm curious why I can see just the subset of tickets? So if the user does not have permission then it should not return anything.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There are a lot of scenario's possible:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Madhav Dube
Please share the details of the actual call you are making to the API. What payload are you sending with the API call?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.