Use case is retrieve all request endpoint data trough REST-API. (Endpoint GET /rest/servicedeskapi/request documentation below). Problem is that endpoint will not expose all data because of calling user identity. Documentation say” Returns all customer requests for the user that is executing the query. That is, the customer requests where the user is the creator of the customer request or has participated in the customer request.”
What are my options to retrieve all data or is this possible at all?
Hello @petteri_saarikko ,
Welcome to the Atlassian Community!
This question has been opened against Jira Service Management Cloud, while the documentation you are pointing to is for Jira Service Management Server. Can you kindly clarify whether you are on Server or Cloud?
Also, I am not sure what kind of data you expect to get running the REST API call. Can you provide more details?
Finally, please find below the REST API documentation for Jira Cloud (Core, Service Management and Software):
Used environment is cloud based and my original reference point of documentation was wrong.
Anyhow result is still same even http request parameter slightly different. https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-get. Link guide told. “Response limitations: For customers, the list returned will include request they created (or were created on their behalf) or are participating in only.” Test queries are made based on basic authentication (private api key) if this has anything to do with this.
Original question remains. What are my options to retrieve all data from this endpoint or is this possible at all? Endpoint will provide data what we are looking for. Problem just is to get all of it.
Hello @petteri_saarikko ,
I am still not 100% sure I understand what you mean with "all data" but, if you mean all the customers requests from a service desk project, ten you can try one of the 2 possible approaches:
I believe that using the Search for issues using JQL (GET) endpoint is the easier approach since you can easily get all the issues in a specific project (service desk or anything else) by running something like in below example (assuming that SD is the project key for the desired Service Desk project):
I hope this helps.
Hi Everyone, In this tutorial, we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached. SLA Threshold Trigger The SLA t...
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