Is there a way to count the number of "Reopened" tickets in a JIRA project?

We have a lot of resolved issues fail QA testing and the status changed to "Reopened". I would like to know how to count the number of Reopened tickets.

9 answers

1 accepted

6 votes
Accepted answer

Does anyone have any statistics showing average defect fix failure rates?

What I mean by "defect fix failure" is a JIRA issue that is resolved by software develops and subsequently fails QA testing (JIRA status is changed to "Resolved" by development and then changed to "Reopened" by QA)

I'm wondering what the industry average is, or what other people are experiencing? What is a good defect fix failure rate (2%, 5%, 10%, 20%, etc.)?

What, are you trying to revenge on developers ? Mine is below 2% mark. A large number of defects fix failure rate means that:

1) You do not have unit-tests OR

2) You do not have integration tests OR

3) You do not use continuous integration (see bamboo) OR

4) Your test coverage is below 30 % (see clover) OR

5) Your work env is so stressful (managers using get things done philosophy) that speed is more important than quality OR .....

-- insert lots of reasons like the above here ---

Hi Ron, 

I'm currently looking for this solution in Jira Cloud as well.

Please let me know if you find a way.


Thanks in advance!



Rebeca Luna

Rebeca - did you ever solve this for Jira Cloud?  I am also seeking a way to count haw many times a ticket is reopened.


-Dane Bigham

Hi Dane,

I created a new field called "Reopened" and setup it as auto increment (using post function) in the reopen part of the workflow. So everytime the task is reopened, the field increment in one.

Hi Rebeca


Can you detail which post function you have used to increment the value ?

Hi Jayanth,

I used this one: Increase value of field (JMWE add-on) - The value of the field will be increased by 1 unit.


Hope this helps!




thanks for reply, I am looking at the transition (from Resolved to Re-opened) to add this post function. Is this where it needs going in? or at the custom field level?

It's exactly in the transition.


You can use andvanced search and JIRA Query Language (JQL)

'status was reopened'

P.S. works for Jira v5.0 for sure

This doesn't account for the number of times one issue WAS reopened only that it had been reopened. Its better than nothing, but I've known times where an issue has been reopened several times.

This worked for me:

reporter = currentUser() AND status was Reopened order by created DESC

I need to know how many times reopened as well.

1 vote

Combine the above with WAS.

The above would only work depending on the version of JIRA. I think the WAS JQL feature was introduced in 4.3. Prior to that, you couldn't do an historical JQL search.

Sorry, I wasn't clear in my question.

What I meant was, I need a count of all issues which have been Reopened at some point in their life (not just those currently in Reopened status). Issues may currently be Fixed, Closed, etc., but were Reopened at some point.


I use an SQL query for this:

        DATE_FORMAT(max(cg.created),"%d-%m") reopened
        , CONCAT("QC-", issuenum) issue
        , it.pname "type"
        , SUBSTRING(summary,1,40) summary
        , IFNULL(assignee,"") assignee
        , ist.pname "current status"
        , IFNULL(DATE_FORMAT(resolutiondate,"%d-%m"),"") "resolved"
        , DATE_FORMAT(max(updated),"%d-%m") "updated"
      , IF(count(issuenum)>1,concat(count(issuenum),"x"),"") "count"
FROM changeitem ci
JOIN changegroup cg ON ci.groupid = cg.ID
JOIN jiraissue i ON = cg.issueid
JOIN issuetype it ON i.issuetype = it.ID
JOIN issuestatus ist ON i.issuestatus = ist.ID
GROUP BY issuenum
ORDER BY max(cg.created) DESC

 which results in something like:

| reopened | issue  | type      | summary                                  | assignee | current status | resolved | updated | count |
| 22-05    | QC-23  | Bug       | Lorem ipsum dolor sit amet               | peter    | Reopened       |          | 22-05   | 2x    |
| 22-05    | QC-89  | Bug       | Fusce luctus faucibus est, at consect    | amy      | Reopened       |          | 22-05   | 2x    |
| 22-05    | QC-134 | Bug       | Lorem ipsum dolor sit amet               | amy      | Reopened       |          | 22-05   |       |
| 22-05    | QC-132 | Bug       | Fusce luctus faucibus est, at consect    | amy      | Reopened       |          | 22-05   |       |
| 22-05    | QC-69  | Bug       | Sed dapibus in eros et pellentesque      | peter    | Reopened       |          | 22-05   | 2x    |
| 22-05    | QC-91  | Bug       | Lorem ipsum dolor sit amet               | amy      | Reopened       |          | 22-05   |       |
| 22-05    | QC-104 | Bug       | Fusce luctus faucibus est, at consect    | peter    | Closed         | 22-05    | 22-05   |       |

I don't know where input your SQL query?

Can you use andvanced search of JIRA Query Language (JQL) to show the reopened 1, 2 or 3 times bugs?

You mean using a filter like this ?

project = MYPRJ and status in ("Reopened" )

Page will show:

Displaying issues 1 to 3 of 3 matching issues

bla bla issues here ?

Just those in the Re-open state right now or those issues which have been re-opened at some point in it's life? WHat about multiple re-opens on one issue? Also, what version of Jira?

That does it!

Thanks much!

Thank you Yuriy Chepelyuk,

Your anwsers is so helpful to me.

I have to count number of reopened defects for measurement objective and your query help me save a lot effort for it.

where is that query please?

is this: ?

project = MYPRJ and status in ("Reopened" )


Where is the query ..??

Where is the query?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,946 views 19 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you