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

Is Not Empty not Working in JQL After Clearing It

Scott Edwards_txqh5v

I am having an issue in JQL where I am searching for "ParagraphField" is not EMPTY and it works initially, only returning the tickets where this field is not empty. The issue is that if I then go and clear the text (select all, delete or using Jira Automation) it is still returned in the results- there doesn't seem to be a way to make the field empty again. Anyone have any ideas on how to resolve this?

Accepted answers

Scott Edwards_txqh5v

Turns out this is a known bug in their system. Here is the link to the ticket for voting and tracking

https://jira.atlassian.com/browse/JRACLOUD-74809

All comments

John Funk

Hi Scott,

Can you share an example of the JQL query along with the results where it is not returning correctly?

Scott Edwards_txqh5v

It is as simple as 'project = "project" AND "ParagraphField" is not EMPTY'. I can't really share the results as it will show our company info.

Run the query, nothing shows up. I add something to ParagraphField and rerun the query and it shows up as expected. I then clear the data in ParagraphField and rerun the query and the ticket is still there even though ParagraphField is now empty.

John Funk

No worries about not showing the data - that is expected.

I would try to do it with an automation rule, and after you clear the field, I would do a New Action, Re-fetch issue data.

Then hopefully when it runs, if it does not update the field you might get some hints in the Audit log for the rule.

Scott Edwards_txqh5v

I tried that but it didn't make any difference, it is still not seen as empty even though the Rule ran successfully.

Screenshot 2020-11-24 120740.jpg

Scott Edwards_txqh5v

I have queried the API and the field value is different on the field I have clear "customfield_11660": null vs the field on an issue that I have never edited "customfield_11660": "". I have tried setting the value to null using the API to no avail- the value doesn't go back to null even though the update call is successful (204). It would seem that empty is checking for null and not empty string in this instance and that is causing the issue and I can't see a way of getting this back to null.