Create filter and dashboard
Asked by Mahmoud Yaseen:

I need to know how to create a filter and dashboard in Jira that shows how many tickets change from 'Testing' to 'In Development' and the developer who was working on these tickets.

This will help track the developer's effort and determine how many times tickets move from testing back to development, allowing us to evaluate the developer's performance.


Answers:
author: Sreenivasaraju P
body: Hi [@Mahmoud Yaseen](/t5/user/viewprofilepage/user-id/5532972) ,

You can create filter with below query and you can other parameters like project and issue types in the query.

status CHANGED from Testing to 'In Development'

after creating the filter, you add filter results gadget on the dashboard. while adding the gadget you can select the required columns(like status,developer..etc) to display


author: Valeriia_Havrylenko_SaaSJet
body: Hi [@Mahmoud Yaseen](/t5/user/viewprofilepage/user-id/5532972) ?  

Welcome to the Community!

Another way can be through gadget in add-on such as [Time in Status](https://marketplace.atlassian.com/apps/1219732/?utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_Create-filter-and-dashboard_20240701).  
You can display dashboard in Jira that shows tickets that change from 'Testing' to 'In Development' and the developer who was working on these tickets by **List View** or Chart View.

![?????? ?????? 2024-07-03 ? 11.42.04.png](https://community.atlassian.com/t5/image/serverpage/image-id/333216i126A56C71BD01C86/image-size/large?v=v2&px=999 "?????? ?????? 2024-07-03 ? 11.42.04.png")

<br />

Also you can display data in by **Chart View.** (here is average report)  

![?????? ?????? 2024-06-16 ? 16.03.43.png](https://community.atlassian.com/t5/image/serverpage/image-id/330067i4ABC4D7FC4E14E56/image-size/large?v=v2&px=999 "?????? ?????? 2024-06-16 ? 16.03.43.png")  
Here is the configuration menu, so you can configure your report precisely for your needs.  

![?????? ?????? 2024-06-16 ? 16.05.16.png](https://community.atlassian.com/t5/image/serverpage/image-id/330068i3352F910A68C9682/image-size/large?v=v2&px=999 "?????? ?????? 2024-06-16 ? 16.05.16.png")  
Add-on has a [**30-day** **free**](https://marketplace.atlassian.com/apps/1219732/?utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_Create-filter-and-dashboard_20240701) trial version and free up to 10 users.  
Hope it helps ?


author: Mehmet A _Bloompeak_
body: Hi [@Mahmoud Yaseen](/t5/user/viewprofilepage/user-id/5532972)

Jira doesn't have a built-in solution for the reports you mentioned. You can try [Status Time Reports](https://marketplace.atlassian.com/1221826) app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the [online demo link](http://status-time.bloompeak.io/demo), you can see it in action and try without installing the app.

1. To get a report of how many times the status of each issue is changed, you can have a look at [Status Count And Entry Dates](https://bloompeak.atlassian.net/plugins/servlet/ac/io.bloompeak.status-time/st-report?ac.reportid=1277) report. Entry date(see In Development, Ready for Testing, In Testing, In Development columns.) is status transition date and status count(see #In Development, #Ready for Testing, #In Testing, #In Development columns) is how many times an issue is entered to this status.

2. To get a report of how much time each assignee spent on issues, you can have a look at [Time in Assignee](https://bloompeak.atlassian.net/plugins/servlet/ac/io.bloompeak.status-time/st-report?ac.reportid=802) report.

++App Features:++

* 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, 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.

For further details, you can have a look at [Status Time Reports How to Videos.](https://www.youtube.com/playlist?list=PLVHoaAkoFPJnG9nLkzcxG0P00ndQgimDs)

If you are looking for a completely **free** solution, you can try the limited version [Status Time Reports Free](https://marketplace.atlassian.com/apps/1222051).

If you have any questions, feel free to [schedule a demo](https://bloompeak.io/schedule-a-call) with us.

Hope it helps.


author: Amay Purohit_RVS
body: Hi [@Mahmoud Yaseen](/t5/user/viewprofilepage/user-id/5532972)

Welcome to the community !!

You can use Jira API's to extract this data. Or as suggested by Stephen use a mktplace app for the same.

You can take a look at the add-on we have developed for the same use case.

[Time in Status Reports](https://marketplace.atlassian.com/apps/1226187/time-in-status-reports?hosting=cloud&tab=overview)

The status transition details report shows when the issue was transitioned to which status and on which date and by whom. The other report which can be helpful is the status transition count, ie how many times the issue went from which status to another. Also the app has 20+ reports to track your bottleneck Issues \& Processes. The data from this app can be easily extracted to a CSV file too. Do give it a try.

[More details here](https://community.atlassian.com/t5/App-Central/Time-in-Status-Reports/ba-p/2348133)

Disclaimer : I work for the vendor who built this app

![TIS - Status Transition Details.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/333164i5B9590EB4BDB5F7E/image-size/large?v=v2&px=999 "TIS - Status Transition Details.PNG")

![TIS - STatus Transition Count.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/333165i2857006DFA4F76A0/image-size/large?v=v2&px=999 "TIS - STatus Transition Count.PNG")


author: Stephen_Lugton
body: [@Mahmoud Yaseen](/t5/user/viewprofilepage/user-id/5532972) the JQL that [@Sreenivasaraju P](/t5/user/viewprofilepage/user-id/853354) will give you that information but it will pick up every time a ticket was changed from Testing to In Development, you can specify a time range or time period, e.g.

For changes in last 14 days:

Status CHANGED from Testing to "In Development" AFTER startofday(-14)

For changes since the start of last week:

Status CHANGED from Testing to "In Development" AFTER startofweek(-1)

For changes in a certain date range:

Status CHANGED from Testing to "In Development" DURING (2024-06-01, 2024-06-14)

comments: author: Mahmoud Yaseen
body: Yes I got this point! but the issue when you tried to create the Dashboard, what should I use to know (How many times ticket changed from In Testing to In Development example ticket X (4 times) Ticket Y ( 2 times)..etc and who was working on this tickets)


author: Stephen_Lugton
body: That is a bit more tricky and you will only be able to do that for status changes that happen from now rather than ones that have already happened.

There are apps on the marketplace that may be able to help you, but you can do it via automation as well.

If you want to use automation you will have to first create a new number custom field e.g. 'Rework numbers', then create automation:

* Trigger: Status change from In Testing to In Development
* If: Rework number is empty then Action: Rework number = 1
* Else: set Rework number to {{issue.Rework number.plus(1)}}

In your filter / dashboard you can then have Rework number as a column  

This assumes that the assignee for each ticket remains the same otherwise you'll have to create another custom field to store names.


Tags: cloud

jira-cloud

jira-service-management