nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

requestStatus = CLOSED_REQUESTS

Hello,

I’m trying to retrieve all Jira Service Management tickets that have the “Completed” status in Jira using the JSM Request API.

I’m currently calling:

/rest/servicedeskapi/request

with:

params = {
    "serviceDeskId": 7,
    "requestStatus": "CLOSED_REQUESTS",
    "requestOwnership": "ALL_REQUESTS"
}

However, not all Jira tickets with status Completed are returned - some appear in the response, while others do not.

Could you please clarify:

Whether CLOSED_REQUESTS is the correct requestStatus to retrieve Jira Completed tickets
Or if there is a different recommended way to fetch all Completed Jira tickets via the JSM API

Thank you,
Eusebiu

Accepted answers

Hi @Eusebiu Gancea ,

you could also use the Jira API to search for your JSM work items via JQL:

The Jira Cloud platform REST API

This will also work for JSM work items.

Best regards

Nico

All comments

Fabio Racobaldo _Catworkx_

Hi @Eusebiu Gancea ,

please could check if tickets in Completed status that don't appear on the response have a correct resolution field and resolved date set?

I'm my opinion CLOSED_REQUESTS are ticket that are resolved on jira backend side.

Please let me know,

Fabio

Hi @Eusebiu Gancea ,

you could also use the Jira API to search for your JSM work items via JQL:

The Jira Cloud platform REST API

This will also work for JSM work items.

Best regards

Nico

But as @Fabio Racobaldo _Catworkx_ mentioned.

You should also check if your work items have a resolution set. Otherwise they wont appear in the request status "CLOSED_REQUESTS".

Thanks

Thanks mate. I used the wrong API call, now is solved

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management