nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Time spent for QA

Gui Ávila

Hi,

I'm thinking of a way to automatically calculate the time spent by the QA team to approve or reject an issue.

So I thought about the following:

- Create a custom field

- When the issue is transitioned from status X to status Y, a post function is triggered.

- The post function automatically updates the custom field with the amount of time the issue spent on status X.

Please, what's the best way to do this?

Gui.

Accepted answers

Jack Brickey

keep in mind that "time in status" may not give you what you really want. if you are interested in seeing how much time went into testing an issue that might be a fraction of the actual time in status. The issue could sit in the QA status for hours or days before someone gets to it. So you might want to consider a two step QA status: Ready for Test and Testing. Then you could use the aforementioned Time in Status addon or you could use Automation and custom fields to capture the transition times.

All comments

Danyal Iqbal

You can try this plugin: https://marketplace.atlassian.com/apps/1211756/time-in-status?hosting=cloud&tab=overview

Jack Brickey

Gui Ávila

Hi @Jack Brickey

Thanks for your help. Yes, that's exactly what I did. There's a "Testing" status, and the QA team only moves to that status when the the testing process beggins.

I don't know about aforementioned . I'll search, thanks.

About using automations, do you have a suggestion on how to do it?

Gui Ávila

Thanks @Danyal Iqbal

Jack Brickey

Sure...

you could create a new date custom field (entered test) to capture the date an issue transition into “Testing” status. Also create a custom field for “time in testing”. Then for automation create two rules something like this...

trigger - issue transitioned from <blank> To <testing>

condition - optional as need to qualify the action below

action - edit the issue and record the date into the first custom field

next rule...

trigger - issue transitioned from testing to <blank>

Action - use the automation date calculation “diff” to insert the value of now - entered test into the time in testing field

Mariana_Pryshliak_Saasjet_qysy8m

Hello @Gui Ávila

As an alternative, you can try a Time in Status for Jira Cloud add-on.

It generates Time in Status report and Status Entrance Date report (which shows the date when an issue has entered each status). So you'll get both the date of entrance and duration in status.

I hope it helps.

Best regards, Mariana.

Mehmet A _Bloompeak_

Hi @Gui Ávila ,

I agree that you should distinguish "Ready for testing" and "In testing". We use the below workflow to track actual development and testing times.

Screen Shot 2021-03-04 at 23.21.57.png

To get the time spent on each status, you can try Status Time app. 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(eg. average in progress time per project).

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

Emre Toptancı [OBSS]

Hello @Gui Ávila ,

We also connected with you through our support channel but for those other who come by this question in the future, I would like to leave an answer.

For a ready built solution that offers great fexibility and details, 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. You can combine statuses into consolidated columns to see metrics like Resolution Time, Cycle Time or Lead Time. Since these consolidated columns are custom defined, you can add the statuses you like and exclude the one you don't.

You can also calculate averages and sums of those durations grouped by issue fields you select. (For example see the average Cycle Time time per project or per issuetype).

Even better, you can have all this data visualized in various chart types.

The app calculates its reports using already existing Jira issue histories so when you install the app, you can get reports on your past issues as well.

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 issuetype.)
Export your data as XLS, XLSX or CSV.
Access data via REST API.
Use one of various chart types.

Timepiece - Time in Status for Jira

Emre

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud