How to track dev and test first time right in JIRA?

Question

Is there any efficient way to track how many times a ticket has gone through dev and test before they are signed off? Some of the tickets in my project are going around between development and test due to poor code quality or sometimes increase of scope. What's the best way to report on this in JIRA, ideally in Scrum boards.

Subtasks seems like an accurate way to record estimated vs actual time spent on each sub task, e.g. dev. However, in the scenario whereby the developer has finished the coding, he would then mark that subtask as done. The tester then picks up the test subtask which of course would fail. So what's the best practice on recording the 2nd or 3rd temps of dev?

Should I keep creating subtasks? How can I then highlight in the report?

Any thoughts would be appreciated!

Gizem Gökçe (OBSS) · Answer

Hello @Wenyun Zhang ,

Welcome to the community!

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

Time in Status mainly has several types of time reports (showing how much time each issue spent on each status, assignee, or group) but the app also has Status Count and Transition Count reports. These reports show how many times each status and each transition was used by each issue.

STATUS COUNT REPORT:

TRANSITION COUNT REPORT:

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. 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 Jira, JSM and JPD 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. 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 reporting process. Enjoy a 30-day free trial to experience the full range of features.

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem

Valeriia_Havrylenko_SaaSJet · Answer

Hi @Wenyun Zhang  👋

I would like to recommend the Time in Status for Jira add-on by SaaSJet.
With this tool you do not need to create subtasks and you will get reports easily by choosing report that you need. 
This add-on allows you to view the entire duration of an issue, from the time it was opened until it was closed, with the Time in Status report.

You can also view the The Status Count report shows how many times an issue has been in each status.

For example, the task was in the To-Do status (1 time), then moved to the In Progress status, and after some time, the task returned to the To-Do status(+1 time). So, the status count for this task is 2 in the To-Do status.

Also Assignee time report shows the total time a particular assignee has been working on the issue. That’s why it’s especially useful for identifying who is responsible for the workflow delays.

Additionally, set User Groups and get all time spent on task.

This add-on comes with a 30-day free trial  version and is free for up to 10 users.
If you have any questions, please don't hesitate to ask.
I hope this helps 😊

Mehmet A _Bloompeak_ · Answer

Hi @Wenyun Zhang

Welcome to the Atlassian Community!

If you prefer using a marketplace app, you can try Status Time Reports 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, you can see it in action and try without installing the app. 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 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.

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

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

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

Hope it helps.