Extended REST API for Time in Status on Jira Server and Data Center

By Emre Toptanci on 06/08/24 11:09
Last updated on 6/12/26 12:47 PM

<span id="hs_cos_wrapper_name" class="hs_cos_wrapper hs_cos_wrapper_meta_field hs_cos_wrapper_type_text" style="" data-hs-cos-general-type="meta_field" data-hs-cos-type="text" >Extended REST API for Time in Status on Jira Server and Data Center</span>

In the past, extracting your workflow data from Time in Status via the REST API was restricted to basic file exports. While useful, this approach offered limited flexibility for teams trying to build custom integrations or feed data into external business intelligence dashboards. With the release of Time in Status version 4.9.0 for Jira Server and Data Center, we are introducing a fully extended REST API. This update fundamentally changes how you can extract and utilize your Jira time-tracking metrics.

What is a REST API? 

A REST API (Representational State Transfer Application Programming Interface) is a standard architecture that allows different software applications to communicate over the internet. For Jira administrators and developers, it means you can programmatically request specific time-in-status data from our app and pull it directly into your own custom applications, databases, or third-party reporting tools without any manual export processes.

What’s New in the Extended API?

This release introduces several new endpoints designed to give developers total control over how they extract reporting data:


JSON and CSV Support

Instead of relying solely on static file exports, the new endpoints allow you to retrieve your Jira data natively in JSON or CSV formats. This makes the data immediately ready for parsing and integration into your existing systems. 

Access to Core Report Types

You are no longer limited in what you can extract. The new API fully supports retrieving raw data for List, Average, and Sum reports, allowing you to replicate your Time in Status dashboards externally.

Async Exports for Large Datasets

Pulling massive amounts of historical Jira data can cause server timeouts. To solve this, we added Asynchronous Export endpoints. These are specifically designed to handle long-running data exports reliably, ensuring your heavy queries complete without failing.

If you are ready to update your reporting infrastructure, you can find the complete technical specifications, authorization methods, and endpoint details in our official REST API documentation.

If you have any questions, please reach out to the OBSS Service Desk.

To learn more about Timepiece - Time in Status for Jira, visit its Atlassian Marketplace page.

 

Topics: Time in Status

No Comments Yet

Let us know what you think