Community moderators have prevented the ability to post new answers.
You can get all issues that do not contain the word 'Apple' by following these steps:
After that, you'll get the list of issues that do not contain the word 'Apple'.
Thank you so much for writing this comment it has helped me end my search for the answer!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Saving filter for each search keyword is not a practical solution, there has to be a better way.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The real answer here is to put better data in - this is a clumsy search, and is nowhere near as flexible as you would like, but I would ask why you are trying to do searches like this?
The answer is probably "we didn't put the right data in the issues that would enable us to do sensible searches"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
issuetype = Bug AND summary !~ "*On Production*"
Try with 'text' instead of summary, as I can't test now if it works as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, but no. Text does not accept != as an operator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dave, !~ is different from !=
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks! !~ works perfectly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I cannot get the !~ to work with the text field. It works in summary, but does not appear as an option for text searches. If you force it, it doesn't work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why is this the accepted answer? 'text' and 'summary' are different fields in JIRA. The OP is asking about the 'text' field which does not support the !~ operator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Agree. This answer is completely wrong and should be un-accepted. You cannot use "!~" on text.
How can I negate a match on text?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This answer does not work for 'text'... should not be marked correct
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have just stumbled upon this old answer and felt the necessity to correct it, as suggested.
However, for consistency with the dates of previous comments, I'll post the correct answer within this comment instead of editing the original answer:
You can get all issues that do not contain the word 'Apple' by following these steps:
- Execute the following JQL: text ~ Apple
- Save your search as a filter, ie named "With Apple".
- Finally, execute this new JQL: filter not in ("With Apple")
After that, you'll get the list of issues that do not contain the word 'Apple'.
My original answer stated I didn't test it, so I was probably answerring posting from my mobile phone...
My main point was that '!~' should be used instead of '!=' with text fields.
As text function is sometimes used as a lazy way to avoid having to write longer JQLs which actually would target Summary and Description fields, some people might have found the correct syntax of DOESN'T CONTAIN '!~' a useful answer every now and then.
But, of course, the correct answer is the one I've just included into this comment.
Sorry for not having noticed this mistake before!
Best regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can confirm Ignacio Pulgar [Tecnofor]'s comment, this is an acceptable solution for searching "Does not contain this text". I do not know why, but it seems that the !~ operator does not work for text.
As a note to this solution, you will likely have to include the majority of your search in the second query, see below example as an explanation.
You run a bakery and track your recipe creations in JIRA. The project is MyBakery, your epics are a custom issuetype called Recipe, and you want to find all of your recipes that do not contain Apples.
This will return all of your project specific recipes that include the word apples.
project = MyBakery AND issuetype = Recipe AND text ~ Apples
Save this as a filter, for this example, the filter name is 100.
In a new query, you can write...
filter != 100
This will return EVERYTHING in JIRA that is not in that filter. So to have it specific to your search you would rewrite the first half of your first search.
project = MyBakery AND issuetype = Recipe AND filter != 100
This will return all of the appropriate items that are not including the text Apples.
Additionally, you can add multiple text options to mask out. If you had a customer who was allergic to Apples and Bananas, you could put in the first query
project = MyBakery AND issuetype = Recipe AND text ~ "Apples OR Bananas"
Your JIRA version will dictate the correct syntax, see https://community.atlassian.com/t5/Answers-Developer-Questions/How-can-i-use-the-like-operator-with-the-List-of-values-in-Jira/qaq-p/545519 for reference.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That was interesting. But I got it to work. For clarification.
I enter "QA PreTested" into the Test Notes for any bug that QA pre tested to ensure that the bug fails in QA or can be reproduced by QA.
I created the filter Filter not in ("QA PreTested")
project in (ItemLogic, TestWiz, enCASE) AND type = bug AND status = "Ready for Development" AND updated >= endOfWeek(-2) AND "Testing Notes" ~ "QA PreTested" ORDER BY updated DESC
Then added that to the filter I wanted which now excludes any bugs I have pre-tested.
project in (ItemLogic, TestWiz, enCASE) AND type = bug AND status = "Ready for Development" AND updated >= endOfWeek(-2) and Filter not in ("QA PreTested") ORDER BY updated DESC
I'm surprised that ZQL has to make you go through this but anyway.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ps: I tried to post that as an answer but the submit button just depresses and nothing happens.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"The operator '!~' is not supported by the 'text' field."
This is just silly.
Having to make a subquery just to negate a string? WTF?
WE chose Jira because it was supposed to be easier to retrieve information with JQL and handier to use than TRAC. Just to find out the hard way that instead of a backtick for code you have to type half a sentence, that it doesn't work inline (also not the double curly braces explained somwhere) and that to make a simple negation of a string you need to write half a page of Javascript or hire a consultant while in TRAC you can just use plain SQL to search for anything you may wish for.
So, where does that leave us? A fancy GUI ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Edited:
The NOT keyword doesn't work with text:
NOT text ~ apple
Neither this other equivalent syntax:
!text ~ apple
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For me, either of those syntaxes always makes the search just return zero results -- even though the non-negated version of the search shows that only about 100 of our 10,000+ issues contain the string I'm trying to include.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have just tried this query both in Cloud and Server 8.6.1 and the NOT and ! syntax do not work with text. Should have tried it before posting this answer.
Have just unaccepted this answer.
Please, refer to the new answer marked as accepted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use the "Power JQL" app - https://marketplace.atlassian.com/apps/1216891/power-jql-extended-search-functions?hosting=server&tab=overview
Which provides the ability to search by text fields using regex.
A few examples:
issue in powerIssue("project = SD", "summary,description", "^ABC-.*")
issue in powerIssue("project = SD", "text", ".*(bug|test).*") - for search by summary, description, comments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can confirm Ignacio Pulgar [Tecnofor]'s comment, this is an acceptable solution for searching "Does not contain this text". I do not know why, but it seems that the !~ operator does not work for text.
As a note to this solution, you will likely have to include the majority of your search in the second query, see below example as an explanation.
You run a bakery and track your recipe creations in JIRA. The project is MyBakery, your epics are a custom issuetype called Recipe, and you want to find all of your recipes that do not contain Apples.
This will return all of your project specific recipes that include the word apples.
project = MyBakery AND issuetype = Recipe AND text ~ Apples
Save this as a filter, for this example, the filter name is 100.
In a new query, you can write...
filter != 100
This will return EVERYTHING in JIRA that is not in that filter. So to have it specific to your search you would rewrite the first half of your first search.
project = MyBakery AND issuetype = Recipe AND filter != 100
This will return all of the appropriate items that are not including the text Apples.
Additionally, you can add multiple text options to mask out. If you had a customer who was allergic to Apples and Bananas, you could put in the first query
project = MyBakery AND issuetype = Recipe AND text ~ "Apples OR Bananas"
Your JIRA version will dictate the correct syntax, see https://community.atlassian.com/t5/Answers-Developer-Questions/How-can-i-use-the-like-operator-with-the-List-of-values-in-Jira/qaq-p/545519 for reference.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
?? Opposite of my need. Using ~ would result in what issues I do not want to see.
If I have 100 cake recipes, of many various kinds, but hate Apples and don't want to see any of the recipes that include the use of Apple.
examples:
~ Apple = show me recipes (issues) with Apple in them
!~ Apple = do not show me recipes (issues) with Apple in them
I want a JQL for the latter of these examples.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think many attempts here are correct.
However for me there was an important detail missing (-> the wildcards):
issuetype = Bug AND text !~ Apple
did not work for me; however:
issuetype = Bug AND text !~ '*Apple*'
did work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you want to match the exact text ? If not then you can use the contains (~) and in your case can be does not contain (!~)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
what is the JQL i have to user if i need exact text? Using ~ symbol it returns all issues that has the particular search string. But i need only those issues that are exactly match to the search string.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.