-
Bug
-
Resolution: Duplicate
-
High
-
None
-
64
-
Severity 2 - Major
-
540
-
Hi everyone,
As this request is a duplicate of https://jira.atlassian.com/browse/JRACLOUD-21372, I am cross-posting the update here for anyone who is watching this request.
I am pleased to inform you that JQL exact text search is now already enabled in Jira Cloud and we have completed the roll out.
Please refer to the other request linked above for more information.
Thank you for your patience.
Best,
Irene Ongkowidjaja
The same explanation as for https://jira.atlassian.com/browse/JRACLOUD-21372
I am sorry that I've mislead many of you with a previous comment on how fast we will be able to address this issue.
Unfortunately I've failed to properly estimate when we could have started investigating this issue due to other more urgent problems. Thus I am moving this issue back to 'Gathering impact' state till we will be able to properly prioritise the 'exact text' issue.
There is no clear estimate of when we can start working on this issue.
Summary
- JQL advanced searching using operators reference CONTAINS with "Exact Phrase" does not return expected result. Eg : using “\”new test\”” but it also returns issue that has “next new csv line Test”
Steps to Reproduce
- Create an issue with summary of "new test" then create another issue with summary of "next new csv line Test"
- Go to search issue and execute this JQL search
- summary ~ “\”new test\””
Expected Results
- Only issue with summary of "new test"
Actual Results
- returns issues that has “next new csv line Test”
Workaround
Workaround is being mentioned at this community post here: Solved: How to query Summary for EXACT match?. To elaborate, using this paid add-on: ScriptRunner for Jira would do the trick for now:
ScriptRunner Enhanced Search
issueFunction in issueFieldMatch("project = CSCRUM", "summary", "new test")
Jira Issue Navigator
Search for Multiple Strings in Scriptrunner using regex
issueFunction in issueFieldMatch("project = CSCRUM", "summary", "new.*|test.*")
Feel free to refer to this add-on documentation here for more information: ScriptRunner Enhanced Search
- duplicates
-
JRACLOUD-21372 Allow exact-text searching in JQL
- Closed
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
- Closed
-
CSMO-460 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
[JRACLOUD-69263] JQL Contains "Exact Phrase" does not return the result as expected
Just adding noise to this ticket. How is it possible that they haven't found a way to do an exact phrase search? ... in 4 years...
Piotr Święcicki, you closed this issue as a duplicate of JRACLOUD-21372.
But this issue is a bug because it used to work in previous Jira versions, while JRACLOUD-21372 is a suggestion. So, it is like Atlassian treats regressions now? Mark them as suggestions?
You guys broke existing functionality and now act like it never existed. Not cool.
Atlassian: Just curious about what happens to the 295 votes to fix this bug? I would hope that those votes would roll into JRACLOUD-21372 (which has 366 votes today).
While there may be overlap (a few people who voted for both), it looks like a LOT of votes will be essentially thrown away by closing this bug.
If you do not have a way to address this problem, then I'd suggest that your New Features Policy is broken.
The hundreds of us who voted for THIS issue would like to know if our votes matter or not.
Just to be clear the paid add-on is not a valid work-around either for many customers, it is UX based and not API.
Hi,
It's been nearly 4 years since this bug was issued. Still, the only workaround is to pay for an addon. It is very impactful for us as it may cause to miss incidents and this is a very basic feature we expect to have by default in Jira. Could you please speed up the correction of this bug?
Thanks, Théo
Dear "Unassigned", when will you decide you "gathered" enough "impact" to actually take action to resolve this travesty?
This issue really needs addressing. Searching for an exact phrase should be core functionality as with all other search engines. I can't believe this wasn't even considered during design. It's like driving a car with no headlights.
If I need to search for "notable_owners_lookup" in a stack trace how am I supposed to find what I'm searching for in hundreds or thousands of stemmed pointless results?
Every now and then I want to look for a specific phrase in Jira, but after one try I unfortunately realize AGAIN that this issue still persists... It's really frustrating that such very basic functionality seems so hard to get implemented...