Hola comunidad, Necesito contar los dias que estuvo abierto un bug, Se puede?

[Ariel Perez]

Hola comunidad, Necesito contar los dias que estuvo abierto un bug, Se puede? Osea independientemente de los estados que transito. Osea el numero total de dias que estuvo abierto, y desúes quiero analisar el tiempo en cada uno de los diferentes estados que tuvo, saludos!

[Lucy Warner_SaaSJet]

Hello @Ariel Perez 

It's a very common case in the community and I guess I know how you can solve it.

You can try Time in Status for Jira Cloud developed by my SaaSJet team and use its Time in Status report. It shows how long an issue has been spent in each workflow statuses. 

The Total column shows the total time spent in all statuses.

Then you can export report to CSV or XLSX files if necessary. You can try a free 30-day trial version and enjpy the resu;ts.

I hope it helps.

[Emre Toptancı _OBSS_]

Hello @Ariel Perez ,

Sory I can't respond in Spanish but I believe I have the perfect solution for you.

For a ready-to-use report, the use of a marketplace app is needed.

If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center.  

Time in Status mainly allows you to see how much time each issue spent on each status.

 

Time in Status has Consolidated Columns,  which allow you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer (organization) or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

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.

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.

  

Timepiece - Time in Status for Jira

EmreT

[Fernando Eugênio da Silva]

@Ariel Perez 

De forma nativa en Jira, no hay forma de obtener todos estos resultados. Necesitas usar alguna aplicación para obtener esta información.
El más utilizado es EazyBI. Puede ver un poco más al respecto aquí > https://marketplace.atlassian.com/apps/1211051/eazybi-reports-and-charts-for-jira?hosting=cloud&tab=overview

Espero que esto ayude de alguna manera

Saludos

Fernando

[Martins Vanags -eazyBI-]

Hi,

You can check this public demo account with few report examples:

https://eazybi.com/accounts/1000/dashboards/7513-age-lead-and-cycle-time

with eazyBI you can calculate the average time in days issues spend in Jira statuses.

Martins / eazyBI