New release loaded with features for Time in Status for Jira Server and DataCenter

This week’s Time in Status release for Jira Server and Data Center (v4.26.0) is a release that we’ve been working on for quite some time and it is loaded with features.

Multiple FROM and TO status selection for Duration Between Statuses report

Some customers have complex workflows that follow alternating routes and end on separate statuses. Having to select a single status to start a DBS metric and another single status to end the DBS metric was too limiting for them. So we are now introducing the option to select more than one status for both FROM and TO status selections of DBS metrics. This will sure make it more flexible.

Filter and Sort support for Status Count reports

Filter and Sort operations were not available for Status Count reports. Many customers asked for this as they what to sort/filter issues based on things like customer wait counts or reopen counts. Now it is available.

Date and DateFormat selections for export window

It was possible to define custom date and datetime formats while getting a TiS report through REST API but file exports started from the UI always used the formats defined in Time in Status settings pages. And those pages were only available to Jira Admin. Now any end user can customize the formats while starting a new file export, through the file export dialog.

EmptyValueToken customization 

Time in Status was indicating EMPTY values with “-” in the report. This was making the data hard to consume for certain spreadsheet apps. Now you can customize how empty values are represented in the report output. You can use “-“, “null”, “”, “0”, etc.

This is also available through file export dialog and also via REST API.

REST API for Status Duration Expanded report

Until this release, Status Duration Expanded report was only available through TiS UI. Due to overwhelming customer demand, the report is now also available through REST API, as both JSON and CSV. (The json format contains more information though)

Setting admin limits through config file

The final feature set is for the admins that want to limit the load on their Jira instances created by Time in Status.

Time in Status operations are highly optimized so it creates the minimum possible load on your server. Even so, if you have a lot of issues, a lot of concurrent TiS users, a server running close to its capacity, etc. you might want to put limits of TiS use as well. The new config keys that are available for Jira admins can be used to limit the number of concurrent file exports, concurrent aggregate calculations as well as the max number of issues that can be included in a report.

The documentation for the new version can be found here.

If you have any questions or suggestions about anything, you can always reach our friendly support team here.