Forums

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

JQL inconsistencies

Edgars Pavlovskis
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 20, 2018

Good day.

Recently I am experiencing issues in extracting data from JIRA with a help of JQL. Here is an example:

Task: To see, how many employees declined our offer since the beginning of the year.

First filter in use: filter = "Junior devs" and status changed to "Job offer" after "2018/01/01" and status in ("backlog","rejected","employed","declined offer","Not part of company","potential hire")

- "filter = "Junior devs"" links to proper board, issue type and all Epic Links that are considered Junior Developers

-  "status in" limits filter to only finalized applications

This filter gives me all people whom we employed this year, and among this list I see, lets say, 3 people who declined our job offer. All 3 actions were done during this year (checked manually)

Second filter in use: filter = "Junior devs" and status changed to "declined offer" after "2018/01/01" and status in ("backlog","rejected","employed","declined offer","Not part of company","potential hire")

- nothing has changed except status in "status changed to".

This filter should give me only those who declined our offer (3, as we know from previous list), but we get only 2 results.

Does anyone has idea why such inconsistencies exist and how to overcome them? Problem is that it's not the only situation where I see such issues, and if in this case outcome can be counted manually, than in other cases its almost impossible.

1 answer

0 votes
Michael Wohlgemuth
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.
August 20, 2018

What happens if you search only this, without anything else?

status changed to "declined offer" after 2018-01-01

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events