Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JIRA JQL query: assignee or comment not changing for 'X' days

Andrés Trujillo February 20, 2019

I'm trying to check if the assignee of a ticket hasn't changed for a specific amount of time (e.g. 3 days). As an alternative I could search for comments not being updated (which might be the better way).

As our sprints are a week long I can't go with "updated" it seems, as a ticket is updated when I finish last weeks sprint and start the new one. 

 

This is my idea (which didn't work):

project = RS AND status in ("Warte auf Umsetzung", "In Arbeit", "Überarbeitung erforderlich", "Wieder geöffnet") AND updated <= -1d AND assignee in (EMPTY) AND Sprint in (futureSprints(), openSprints())

 

Best regards,

Andrés

2 answers

1 accepted

1 vote
Answer accepted
Andrés Trujillo February 25, 2019

project = RS AND assignee in (Reuter) AND assignee changed to (Reuter) before -2d AND Sprint in (futureSprints(), openSprints()) AND NOT status = Geschlossen

1 vote
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 20, 2019

Hello, 

You can right a JQL query like this to check if the assignee was not changed for 3 days:

not assignee changed after 3d

But you can not do the same for the comment field out of the box.

Andrés Trujillo February 20, 2019

Hello,

it works better now, but still I don't see all tickets that have had their assignee changed (to empty).

I'm guessing that the problem comes from the fact that I am not assigning a specific user, but setting it to 'empty'.

When checking  all activities I actually don't see the assignee being change to empty either.

 

Query looks like this now: "project = RS AND status in ("Warte auf Umsetzung", "In Arbeit", "Überarbeitung erforderlich", "Wieder geöffnet") AND assignee in (EMPTY) AND NOT assignee changed after 1d AND Sprint in (futureSprints(), openSprints())"

Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 20, 2019

Try like this:

not assignee changed after -3d

Andrés Trujillo February 22, 2019

It's still not working. The query also shows me tickets that have been changed and hour ago. :(

I again changed the query a bit to make sure that tickets, that have been assigned to "Reuter" for at least a day (at least that was my intention):

project = RS AND assignee in (Reuter) AND assignee changed to (Reuter) after -3d AND assignee changed to (Reuter) before 1d AND Sprint in (futureSprints(), openSprints()) AND NOT status = Geschlossen

But that doesn't works either. Not sure what I'm still making wrong.

I would have thought that this was a more common query to check wether a ticket is in someones possesion for longer than a specific amount of time. 

Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 22, 2019

I did not notice the NOT keyword before the assignee field in your query. That is why you get these results

Andrés Trujillo February 22, 2019

There isn't a NOT keyword in my latest iteration, but you have me thinking there tbh.

The goal is to identify all tickets that have been assigned to Reuter for more than 2 days, but I can't figure out how the JQL should look like.

Andrés Trujillo February 25, 2019

This seems to do the trick:

project = RS AND assignee in (Reuter) AND assignee changed to (Reuter) before -2d AND Sprint in (futureSprints(), openSprints()) AND NOT status = Geschlossen

Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 25, 2019

It is good, if it works for you!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events