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

Advanced JQL queries doesn't work as expected

Slawek Dobrzanski

I'm trying to set up some custom filters, and I'm really struggling to understand why certain advanced JQL doesn't work for me.

Example 1, below will return a considerable number of issues

status changed after -5w before -2w and project = xxx

Example 2, will not provide any, although I'm using the same format as in other JQL queries:

status changed to Done after -5w before -2w and project = xxx

Accepted answers

Slawek Dobrzanski

The problem is related to how status is interpreted in certain configurations.

In this case, apparently "Done" is not properly translated into the state used and stored internally.

To check the actual value, use REST API endpoint, and update the JQL:

status changed to 12316 after -5w before -2w and project = xxx

I would assume that this is a bug in JIRA.

All comments

Hello @Slawek Dobrzanski

Your query is correct!

Are you sure the filter isn't just supposed to return no results? (=there are no issues that satisfy the condition)

Slawek Dobrzanski

That is exactly the issue - I think .

I can simplify the query to:

status changed to Done and project = xxx

For such query, I'm sure that some issues should be returned, but again - nothing.

The problem might be in the status "Done", but this is what I see if I remove the "changed to" part, or when I try to use status in (Done)

Side note: this is next gen project

Slawek Dobrzanski

The problem is related to how status is interpreted in certain configurations.

In this case, apparently "Done" is not properly translated into the state used and stored internally.

To check the actual value, use REST API endpoint, and update the JQL:

status changed to 12316 after -5w before -2w and project = xxx

I would assume that this is a bug in JIRA.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud