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; } } }

How to find in Jira tickets that reach a specific lane and then go back?

silversonicaxel

Hello, I need a quick way to visualise tickets that go from DOING to DONE and go back to DOING. My goal is to understand which are the tickets and the problems related to tickets that are supposed to be done, but actually they are not.

Is it possible? Thanks.

Alessandro

Accepted answers

Mirek

@silversonicaxel, there are couple of ways of achieving it. It depends on your workflow that you currently have. You did not share this information but only mentioned:

quick way to visualise tickets that go from DOING to DONE and go back to DOING

In order to be SURE that ticket was in DOING status was changed to DONE and get back from DONE to DOING you can execute this query:

(status = DOING) and (status CHANGED from DOING to DONE) and (status CHANGED from DONE to DOING)

Wy that? There might be other transitions that go to DONE, so by doing that you are sure that someone executed exactly that path..

If you have simple waterfall workflow where DOING is before DONE and nothing else can be executed (expect doing back to DOING) then it is simple as that:

status was DONE

or to be more specific (if you have more complex workflow and do not care about which path ticket took to get back to DOING e.g from DONE to REOPENED and then from REOPENED to DOING)

status = DOING and status was DONE

and if you set resolution no your workflow when going to DONE from DOING you can find tickets also by executing this

status = DOING and resolution CHANGED

thanks to that you also find tickets that was ever resolved (useful if you have more that one status where you can set resolution)

All comments

Kimberly Deal _Columbus ACE_

I am not sure this is the best or most efficient way, but for a quick study of whats going on. I would set up a post fuction on the done to doing transition to fire a custom event, which I would set to send a notification on the event. It would show if this was much of an issue. I suppose it could alao flood your inbox if this is happening to a lot of issues.

Maybe there are some other folks who could chime in.

Alexey Matveev

Hello,

You can write a JQL like this:

status = DOING and status changed from DONE to DOING

unknown

+1 @Alexey Matveev

Mirek

@silversonicaxel, there are couple of ways of achieving it. It depends on your workflow that you currently have. You did not share this information but only mentioned:

quick way to visualise tickets that go from DOING to DONE and go back to DOING

In order to be SURE that ticket was in DOING status was changed to DONE and get back from DONE to DOING you can execute this query:

(status = DOING) and (status CHANGED from DOING to DONE) and (status CHANGED from DONE to DOING)

Wy that? There might be other transitions that go to DONE, so by doing that you are sure that someone executed exactly that path..

If you have simple waterfall workflow where DOING is before DONE and nothing else can be executed (expect doing back to DOING) then it is simple as that:

status was DONE

or to be more specific (if you have more complex workflow and do not care about which path ticket took to get back to DOING e.g from DONE to REOPENED and then from REOPENED to DOING)

status = DOING and status was DONE

and if you set resolution no your workflow when going to DONE from DOING you can find tickets also by executing this

status = DOING and resolution CHANGED

thanks to that you also find tickets that was ever resolved (useful if you have more that one status where you can set resolution)

unknown

Learnt something new, thanks @Mirek

Kimberly Deal _Columbus ACE_

This answer is fantastic. I am going to add it to my JQL notes. Which I very much need to keep studying. Thank you @Mirek!

silversonicaxel

This is great, thanks a lot It works like a charm

Welcome!

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

Quick Links

Find more posts tagged with

issue

jira

status