Epics how long in development?

[Wojciech Cora]

Hi! does anybody know if there`s a way to find epics which are in development more than certain time? ex. more than 4 weeks? 

thanks

Wojciech 

[Wojciech Cora · Accepted solution]

OK thank you guys! so Jira is not able to use its own, embedded functions? I have to pay for extra features? 

Thanks

W. 

[Yuliia_Borivets__SaaSJet_]

Hi @Wojciech Cora 

You can try some other solutions to get the time in status data for Jira issues:

• Built-in Jira feature Days in Column (!Available only for classic boards). You can learn how to enable this feature here. But if you instead need to remember time measurement over time, by status (e.g., how long was I in status <X>), you would need to explore other options.
• Use custom fields and automation rules to measure the time in status.
• Try one of the Atlassian Marketplace add-ons as Time in status for Jira Cloud.

[Wojciech Cora]

Thanks @Yuliia_Borivets__SaaSJet_  for food for thought :)

[Dave Bosman [Realdolmen]]

Hi @Wojciech Cora ,

When youy transition the issue to in development you should fill in a date field with current date. 

And you could use a query like 

issuetype = epic and status = "In Progress" and "Waiting since" <= endOfDay(-28) 

Regards

Dave

[Wojciech Cora]

Thanks Dave I see you understand my point. I was trying to use filter:

project = [name] and issuetype = epic AND Sprint = [number] and [number] and status != done

it is showing me some data but I see they are true`ish... true to some extent... 

meh.. 

[Rahul_RVS_Support]

Hi @Wojciech Cora 

You can also try out our plugin,

Agile Tools : Epic Tree & Time in Status 

The add-on provides the time spent in each status for the entire lifecycle of the issue. You can also extract the transitions history of the issue. Along with various Issue stats reports, you get additional features like Epic Hierarchy, Links Hierarchy & Worklogs Report to track the project's progress. The main features are as below

• More than 8 types of Time in Status Reports. Excel Export available for all status reports.
  
  • Time in Status
  • Time with Assignee
  • Time in Status with Assignee
  • Time with Assignee per Status
  • Status/Assignee Count
  • Multiple Transition Reports
  • Avg Time reports
• Epic Hierarchy / Sum Up (Standard Jira Hierarchy Epic -> Story -> SubTask)
• Link Hierarchy / Sum Up (Hierarchy based on your issue link, upto 10 level deep)
• Worklogs Report

[Emre Toptancı _OBSS_]

Hello @Wojciech Cora ,

Our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud, and Data Center.

Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee. For your case, you can select your issues and see how much time each one spent in each status.

Time in Status also allows you to filter issues based on these status durations so you can easily find the ones that spent more than a threshold value in a status.

You can also combine statuses into consolidated columns to see metrics like Ticket Age, Resolution Time, Cycle Time, or Lead Time. You can calculate averages and sums of those durations grouped by the issue fields you select. (For example, see the total InProgress time per Epic or average Resolution Time per issue type). 

  

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.

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.

Using Time in Status you can:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

https://marketplace.atlassian.com/1211756

EmreT

[Bloompeak Support]

Hi @Wojciech Cora ,

As an alternative, you can try Status Time app developed by our team. It provides reports on how much time passed in each status as well as status entry dates and status transition count.

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. It has various other reports like assignee time, status entry dates, average/sum reports by any field(eg. average in progress time by project, average cycle time by issue creation month). And all these are available as gadgets on the dashboard too.

For you specific case, you can export the report into excel and sort results by "In development" status duration.

Here is the online demo link, you can see it in action and try.

If you are looking for a free solution, you can try the limited version Status Time Free. Hope it helps.

[Bill Sheboy]

Hi @Wojciech Cora 

How about using JQL, such as:

project = myProject
 AND issuetype = Epic
 AND statusCategory = "In Progress"
 AND NOT status CHANGED AFTER -4w

Please look here for more information on advanced JQL:

https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/#Advancedsearchingoperatorsreference-CHANGEDCHANGED

Best regards,
Bill

[Suvradip Paul]

Hi @Wojciech Cora ,

Thanks for posting in community.

I am not sure of how your workflow is configured.

1.  What are the status for WIP items in your board?
2. Are you using EPIC STATUSES in your epics? 
3. Are you using roadmap? Check this out as you can see your EPIC Movement - https://support.atlassian.com/jira-software-cloud/docs/see-the-progress-of-an-epic-on-the-roadmap/

It would be great if you could respond to the above to answer your query.

Cheers

Suvradip

[Wojciech Cora]

Thanks, no worries. I will manage :)

W

[Suvradip Paul]

Ok No worries @Wojciech Cora .

But the criteria of the JQL would depend on answers to these(because writing a JQL doesn't help us to find the solution until we know how these projects are configured e.g. - EPIC STAUSES one of the field used). More Over, Road maps would be the better option if enabled instead of using writing JQL because the roadmap was created to check the EPICs completion.