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

[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):

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

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

[rvaneerd]

Hi @Ste Wright ,

Atlassian Support referred me to an existing ticket in which this is assumed to be a bug dating back to 2019.

However, I think I've figured out what is causing the mallfunction in our environment.

After investigating some tickets referred to in Atlassian's response I started to dig into the contents of the ChangeLog through Atlassian's REST API.

I examined the ChangeLog of two different Jira tickets, and I realized that the ID's of the Statusses have changed during the migration.

For a ticket that was changed from Concept to Cancelled, before our migration, I got the following response:

"created": "2022-03-15T10:15:43.837+0100",
"items": [
 {
  "field": "status",
  "fieldtype": "jira",
  "fieldId": "status",
  "from": "10508",
  "fromString": "Concept",
  "to": "10506",
  "toString": "Cancelled"
 }
]

For a ticket that was changed from Concept to Cancelled, after our migration, I got the following response:

"created": "2022-03-30T16:42:06.783+0200",
"items": [
 {
  "field": "status",
  "fieldtype": "jira",
  "fieldId": "status",
  "from": "10056",
  "fromString": "Concept",
  "to": "10040",
  "toString": "Cancelled"
 }
]

I could retrieve the current status IDs from our system and they match as shown in the last code block.

The first code block has different values and hence the JQL does NOT exclude them.
Unfortunately, we cannot use the old values any longer.

I asked Atlassian Support whether these old Status IDs from the ChangeLog could be changed afterwards.

Regards,
Rob

[Ste Wright]

Hi @rvaneerd 

Thanks for updating this, this is great insight!

Whilst you await a response from Support, are these IDs all within your Cloud instance?

You can use JQL with Status IDs, rather than names - so you could try a query such as...

NOT (status CHANGED FROM 10508 TO 10506 OR status CHANGED FROM 10056 TO 10040)

...and see if this works?

Ste

[rvaneerd]

Hi @Ste Wright ,

Thanks for sticking with me ;-)

I already tried that but unfortunately our system does not recognize the old IDs and hence I cannot finish the JQL or have it accepted.

Atlassian Support recognized my situation and they're now escalating to more senior resources to assyst.

Regards,
Rob.

[Ste Wright]

Hi @rvaneerd 

I think Atlassian Support is best placed to assist here, as it probably involves the underlying database - something only they can access in Cloud!

Please keep us updated on your progress though :)

Ste

[rvaneerd]

Hi @Ste Wright ,

This is to inform you (and the others following this issue) that our issue with the status has been resolved by Atlassian Support.

They corrected the old values in our Cloud database.

Regards,
Rob.

[Ste Wright]

Great news Rob, glad to hear you got this resolved!

Ste