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; } } }

How can I retrieve the raw data for status transition stamps from JSM?

Amy Chamberlain

I realize there are several apps on the market that do this and visualize cycle times for you. I've reviewed most (if not all) of them, and find they're too restrictive. I need to be able to calculate my own fields, values and metrics.

Is there a way, perhaps using ReST APIs, that I can retrieve this data from my portal (or service desk) into a visualization tool or other scheduled output so that I can monitor cycle times myself?

Thanks in advance!

EDIT: Please read the full post - I AM NOT INTERESTED in new gadgets, tools, or add-ons. This limits the functionality that I need, I'm looking for API counsel only. The answer accepted gave me the best input for this (thank you!) but I'd love to hear from non-Atlassian-Partners who have endured this same workaround.

Accepted answers

Danut M _StonikByte_

Hi @Amy Chamberlain,

Indeed, you can use the Jira REST API end-points to get the change log of the issues.

You could use this REST API end-point to get the changelogs for an issue:

https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-changelog-get

Also endpoints like these with is expand=changelog parameter:

https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-get

https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-search/#api-rest-api-2-search-jql-get

The result is in JSON format and you must use pagination.

But as you can see, this is not an easy task. It involves a lot of work and is very error-prone...

My recommendation is to look for an app on Atlassian Marketplace. It will save you a lot of time.

You reviewed some apps, but have you also look over the gadgets offered by our Great Gadgets app? It offers some re powerful gadgets for measuring cycle time and ti,e in status in many ways, being highly configurable.

Have a look over this article, especially on the examples with Control Chart gadget, Histogram Chart gadget, Cycle Time Trend gadget and Time in Status gadget. I'm pretty sure that they can accommodate your use case.

https://community.atlassian.com/forums/App-Central-articles/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369

The gadgets displays the cycle time in the diagram/chart, but also on their Data tab you will find the cycle time for individual issues, which can be exported in CSV.

If you have any questions and need help with the configuration of our gadgets, feel free to contact us directly at support@stonikbyte.com.

Danut.

All comments

Danut M _StonikByte_

Hi @Amy Chamberlain,

Indeed, you can use the Jira REST API end-points to get the change log of the issues.

You could use this REST API end-point to get the changelogs for an issue:

https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-changelog-get

Also endpoints like these with is expand=changelog parameter:

https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-get

https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-search/#api-rest-api-2-search-jql-get

The result is in JSON format and you must use pagination.

But as you can see, this is not an easy task. It involves a lot of work and is very error-prone...

My recommendation is to look for an app on Atlassian Marketplace. It will save you a lot of time.

https://community.atlassian.com/forums/App-Central-articles/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369

The gadgets displays the cycle time in the diagram/chart, but also on their Data tab you will find the cycle time for individual issues, which can be exported in CSV.

If you have any questions and need help with the configuration of our gadgets, feel free to contact us directly at support@stonikbyte.com.

Danut.

Ayça Erdem_OBSS_

Hello @Amy Chamberlain

Many apps offer cycle time tracking, but often with rigid definitions that don’t fit all use cases.

If you're looking for maximum flexibility to define what Cycle Time means for your team, I’d strongly recommend taking a look at Timepiece - Time in Status for Jira, developed by our team at OBSS.

Timepiece mainly allows you to see how much time each issue spent on each status or each assignee. You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

this image how you can create your own metric

Cycle Time 1.png

Cycle Time 2.png

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.

Timepiece reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts. And the app has a REST API so you can get the reports from Jira UI or via REST. Also you can export the reports in to various formats easily.

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process

Hope it helps

Ayça

Iryna Menzheha_SaaSJet

Hi and great question @Amy Chamberlain
The calculation of Cycle Time and Lead Time indeed requires flexibility to adapt to varying workflow designs, and simplistic assumptions often fail to capture the nuances of real-world processes.

For this need my team developed Time Metrics Tracker | Time Between Statuses

If your priority is to build your own metrics based on raw transition stamps and durations — Time Metrics Tracker is the go-to solution. Here's why:

Custom Time Metrics
Define exactly what you want to measure — for example, the time from “Waiting for Support” to “Resolved”, or even between custom internal statuses like “Design Review” to “QA Ready”.

Multiple Metrics in One Report
You can track Cycle Time, Lead Time, Time to Market, Wait Time, etc., side-by-side — all tailored to your workflow.
Export Raw Data
Export your metrics and status durations to CSV/Excel for further analysis, reporting, or integration with external tools like Power BI or Tableau.
Visualizations & Alerts
Quickly spot trends and bottlenecks with built-in charts, and get notified if certain thresholds are exceeded.

👨‍🔧 + REST API Not Required

While REST API is an option for extracting Jira changelogs, using this app means:

No need to maintain custom scripts
No manual data stitching
All your cycle time metrics in one place, fully customizable and exportable

App developed by my team, so we’re always happy to help 🚀

Hope this gives you more flexibility and control over your metrics!

Amy Chamberlain

Thanks for the API information. I don't know if you read my post but I am not interested in being sold add-ons or extensions, only in the raw changelog output.

That said I really appreciate the nudge in the right direction - thank you!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management