Jira Integrations: Use Parameter Sets in Timepiece REST API

With this week’s release of Timepiece - Time in Status for Jira Cloud, we are introducing the ability to use Parameter Sets while getting REST API reports.

Until this release, while using Timepiece REST API for integrations, you had to explicitly provide all report parameters to get a report. This was a little cumbersome. Customers frequently requested the option to reference a parameter set, instead of giving all parameters every time. After all, a parameter set already contains all the needed parameters. With this release, Timepiece now supports referencing parameter sets for REST API reports.

How Do Parameter Sets Work With the Timepiece REST API?

You can reference a parameter set simply by providing the parameter set ID as the “paramSetId” parameter.

When a parameter set is referenced, all the report parameters are taken from that parameter set. (Some REST endpoints might require additional parameters but the API response will warn you about that).

We took this one step further. You can both reference a parameter set for your report and explicitly provide some of the parameters. In that case, the explicitly provided parameters will override the parameters in the parameter set, others will be used from the parameter set.

Why Should You Use Parameter Sets for Jira Integrations?

This new feature makes some exciting use cases possible.

First of all, building integrations becomes easier since all you need to do is provide a tisjwt and a parameter set ID.

Second, you can change the behavior of your integration by simply changing the parameters saved in the parameter set. The integration code will start acting according to the new definition.

And third, you can use a single parameter set for multiple report integrations, by simply overriding some of the parameters. For example, you can use the same parameter to get a Status Duration report and an Assignee Durations report, by simply overriding the reportType parameter in each REST call. 

Managing Jira integrations usually means dealing with massive, repetitive API payloads. If your team maintains multiple data pipelines or custom business intelligence dashboards, hardcoding every single report parameter into your scripts quickly becomes a maintenance headache. By calling a saved parameter set via a single ID instead of rebuilding the query every time, you keep your codebase clean and drastically reduce the risk of syntax errors breaking your data imports.

Think about what happens when your management team changes their reporting requirements. Previously, a Jira administrator would have to coordinate with a developer to manually rewrite the integration code just to add a new project, swap a date range, or filter out a specific issue type. Now, you can simply update the parameter set directly within the Timepiece UI. The API automatically pulls the new configuration on the next run, completely bypassing the need for a code deployment and saving your engineering team valuable hours.

How Can You Get Started With Timepiece Parameter Sets in Jira Cloud?

Almost all REST API endpoints support this new option. Please see this documentation page for details about how to use it.

This new feature is currently available only for Timepiece Cloud and only for REST API reports. Jira DC support is in the works. We are also planning to make this possible on Timepiece dashboard gadgets.

To learn more about Historian and try it for 30 days for free, visit its Atlassian Marketplace page. You can also book an online demo meeting with our experts.