Defining Raw data in 'Time in Status' field

[jriccardo]

I am building reports from Jira using ODBC connectivity and would like to know the metadata definition of the  'Time in Status' field.   

I want to be able to align the status with the time spent by breaking this string down.

1_*:*_1_*:*_27411727_*|*_5_*:*_1_*:*_0_*|*_10000_*:*_1_*:*_13451032_*|*_10300_*:*_2_*:*_58356728

Any help is appreciated

[Valeriia_Havrylenko_SaaSJet]

Hi @jriccardo 👋

The string you provided seems to be a custom representation of this data, likely encoded in a specific format for storage or transmission.

To the best of what I know," this field stores status data for an issue. The status data is separated by "_*|*_". Within each set of status data, there are 3 fields: status ID, the number of times the issue entered that status, and the time in seconds spent in that status. So, for the input below: 1_*:*_1_*:*_27411727_*|*_5_*:*_1_*:*_0_*|*_10000_*:*_1_*:*_13451032 It means the issue has been in: - Status with ID 1, 1 time for 27411727 seconds - Status with ID 5, 1 time for 0 seconds - Status with ID 10000, 1 time for 13451032 seconds

I want to recommend you to try easier way to get reports - Time in Status. Also we have 7 types of status time reports such as Time in Status, Assignee Time, Average Time. All the reports you can display as Pie, Bar or Area Charts.



Also you can get cycle and lead time to uncover bottlenecks and delays

And last, but not least - we have Sprint Performance Report Sprint Performance Report where we have all the metrics for easy reporting.

Add-on has a 30-day free trial version and free up to 10 users. 
Hope it helps 😌

[Gizem Gökçe _OBSS_]

Hello @jriccardo ,

Sometimes it can be difficult, confusing and time consuming to use features implemented directly in Jira. For specific needs like yours, it is better to use out-of-the-box solutions. 

If you are open to using an application specifically tailored to your needs, Timepiece - Time in Status for Jira which is developed by my team at OBSS, is the tool I would highly recommend. It is available for both Jira Cloud, and Data Center. 

Time in Status 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 Response Time, Resolution Time, Issue Age, Cycle Time, Lead Time etc. (Please see the screenshot below)

For all numeric report types, you can also calculate averages and sums of those durations grouped by the issue fields you select. 

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. It supports both Company Managed and Team Managed projects for Jira Cloud.

Time in Status 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. Enjoy a 30-day free trial to experience the full range of features.

Hope it helps,

Gizem

[jriccardo]

We currently subscribe to Time in Status for OBSS.  I need to use in outside of Jira using an ODBC or PBI connection.

Thanks

[Gizem Gökçe _OBSS_]

Have you tried using our REST API? You can use the Timepiece - Time in Status for Jira REST API to programmatically retrieve data and build your own integrations. We don't have a built-in integration, but most of our customers choose to build their own integrations using our REST API to connect to tools like PowerBI, easyBI etc.

Please see the document below to get detailed information on how to use our REST API

https://dev.obss.com.tr/confluence/display/MD/TiS+Cloud+-+REST+Reporting 

Hope it helps!

[Mehmet A _Bloompeak_]

Hi @jriccardo

To my knowledge, this field stores all the status data of an issue. Status data are separated by "_*|*_". Inside each status data, there are 3 fields: status id, how many times the issue entered to that status, time in seconds in that status.

So, the input below means:

1_*:*_1_*:*_27411727_*|*_5_*:*_1_*:*_0_*|*_10000_*:*_1_*:*_13451032

Issue has been in:

• status with id 1, 1 time for 27411727 seconds
• status with id 5, 1 time for 0 seconds
• status with id 10000, 1 time for 13451032 seconds

Built-in Jira reports and gadgets offer limited flexibility for time in status. If you prefer using a marketplace app, you can try Status Time Reports app developed by our team which is available for Data Center/Cloud. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app. For your case, you can have a look at Time in Status for Each Issue report.

For further details, you can have a look at Status Time Reports How to Videos.

• This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, resolution time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

• You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
• Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
• You can set different duration formats.
• You can export reports in CSV file format and open them in MS Excel.
• You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
• You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely free solution, you can try the limited version Status Time Reports Free.

Hope it helps.

[jriccardo]

Thanks,

In addition to being able to present this info within Jira, I would absolutely need it with reports/Dashboard I am building in Crystal Rpts and PBI for external client SLA's.   Would these fields become part of the database/table?   If not, the product will not work for us.

Again, 

Thanks for responding.

[Mehmet A _Bloompeak_]

Hi @jriccardo ,

Due to secure design of our app, we do not store/process any data on our servers and we do not modify your issue data. One side effect of this secure design is lack of ODBC/PBI connection. The only option is using the Export button in the UI of the app.