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

Status values not presented and CHANGED FROM ignored when building JQL query

Rob van Eerd

Hi,

Our locally installed Jira is migrated to the Cloud version last week.
I've not been involved in the migration process but now I'm asked to investigate a specific issue regarding the filters.

Previously, we could add the following piece of code: "NOT Status CHANGED FROM Concept TO Cancelled" to a JQL query.

Now, this does not seem to work anymore since we migrated to the Cloud version. It looks like that whole section is ignored.

In the past (so I was told) the status values would pop up after typing the FROM and TO keywords but that is not the case anymore.

Biggest problem is not the lack of status value pop-ups but the fact that this whole addition (to the full JQL query) seems to be completely ignored resulting in to many records returned.

Any one any thoughts on where to look for a solution?

Regards,
Rob van Eerd

Accepted answers

All comments

Ste Wright

Hi @Rob van Eerd

You're correct that when using the history operators - like CHANGED - in JQL, during query creation it doesn't show available statuses as the query is written.

I couldn't find a bug for this - please feel free to report it via: https://jira.atlassian.com/secure/Dashboard.jspa

In terms of the query working though, it works fine for me.

This might mean it's related to the migration - or perhaps this query has no results in Cloud?

Can you provide an example? Provide a screenshot of an Issue's history which should be in the search, the search query itself, and the results?

Ste

rvaneerd

Thanks for your reply @Ste Wright

I already created a ticket with Atlassian support.

As for the examples etc.

Here's a screenshot of the query and the results (be aware we're trying to exclude the status changes from concept to cancelled):

20220329-Jira-JQL-Query with results.png

And here is a screenshot of the history of one of the tickets that should be EXCLUDED.

20220329-Jira-JQL-Query with results - filtered (out) status change.png

We already experimented with the case-sensitivity of the statusses being checked in the "changed from" part of the JQL-Query.

Ste Wright

Hi @rvaneerd

What did Atlassian Support say?

As far as I can see, the JQL looks accurate. Are there any other exceptions like QCP-2961?

Ste

rvaneerd

Hey @Ste Wright,

Atlassian is still looking into the issue.

Once I get their proper response / solution, I'll report back.

Regards,
Rob

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jql