Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How Do I Create a JQL Filter Comparing Against An Issue's Due Date?

I have a filter that compares against a specifc date at the moment.

status was not in (Open, In Progress, "Awaiting Approval") on "2018/02/27"

I would like to use the due date of a specific issue (i.e KEY-1234) so that if the due date of the issue changes the filter will use this updated date.

Is this possible?

I have ScriptRunner and JQL Tricks plugins to use as well.

1 answer

2 votes
Andy Heinzer Atlassian Team Mar 02, 2018

I cannot find a way to do this with Jira, Scriptrunner, and/or JQL Tricks.  I will try to explain why I think that is first. When you're using a WAS clause, this is looking into historical data on issues in Jira.  This behaves a little bit differently than standard issues and their current values.

In native Jira, when you use the WAS parameter, you can then use the other time parameters such as ON, BEFORE, or AFTER.  But the problem here is that these have to be a specific date/time.  They cannot be a variable such as DueDate, Updateddate, etc.

The addition of these two other plugins can't change this fact.  Scriptrunner, does have a dateCompare function.  But in order to use this, you have to do so within the issueFunction structure. This does not afford its use within a WAS statement of JQL.  And we would still need some other date variable to compare it against.

What I think you are looking for here is really something that I think could be accomplished with a SQL query.  Which is why I am more inclined to suggest the use of the SQL for Jira Driver plugin,  I believe this plugin would then allow you to use more of a SQL syntax formatting in order to create a hybrid JQL/SQL query that might permit you to find these issues based on those values.  I am not positive this will work, but I think this is currently the best avenue for success here.

Hi, many thanks for your investigation and great explanation. It makes a lot of sense and I'll have a look at the SQL plugin route.

Thanks again

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

222 views 2 1
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you