What endpoint from their JIRA Cloud REST API v2 would expose this data? Stitch API call

[daltonjaklitsch]

Context:

When an engineer marks there ticket to "done" via "Status Category", I believe jira creates an internal time stamp that surfaces when you query natively with in Jira. The head of our engineering team runs this query (attached) to see what tickets where created within a given timeframe. When the csv is exported an additional column "Status Category Changed" is next to "Status Category". We need to surface this column in our stitch integration to be able to automate/build this report in looker. 

Conversation with stitch:

What endpoint from their JIRA Cloud REST API v2 would expose this data so we can ensure it gets included with our requests. I looked through their API docs but its not clear to me if this data is even exposed by Jira for us to grab. So you'll want to confirm with them where it gets exposed in the API then we can see if we make API requests to get it. If we don't, then again its a feature request to call on it.

Let me know if you need any additional documentation. thank you for your support.

[Bill Sheboy]

Hi @daltonjaklitsch -- Welcome to the Atlassian Community!

I believe you are asking about this field: statuscategorychangedate

And I suspect most of the endpoints which return work items (formerly called "issues") can return that field.

Kind regards,
Bill

[Trudy Claspill]

Hello @daltonjaklitsch 

Welcome to the Atlassian community.

The JQL you show is searching for issues that had their Status changed to Done. The JQL is not specifically using Status Category in the criteria.

Every Status value is a member of a Status Category. There are three Status Categories, each with a color code that colors the Status lozenge for Status values in that category.

Name	Color
To Do	gray
In Progress	blue
Done	green

A Status value can have any name, regardless of the Status Category to which it belongs. It is coincidental that the Status used in the filter is named "Done" and that "Done" is also the name of a Status Category.

When an issue undergoes a change of Status, and the starting and ending Status values are members of different Status Categories, then the Status Category Changed timestamp will be updated. If the starting and ending status are in the same category the timestamp is not updated.

So, the Status Category Changed timestamp may not reflect when the issue Status was changed to Done if the Status changed to Done from another Status value that is also in the Done Status Category.

The Status Category Changed timestamp is part of the information that can be included in this API endpoint

https://<yourinstanceurl>/rest/api/2/issue/<issuekey>?expand=names

It will be in the "fields" section of the output:

 "fields": {
    "statuscategorychangedate": "2025-01-28T12:55:40.127-0800",