• 661
    • 89
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Status Update 30/01/2023

      Hi everyone,

      This is Irene from the Jira team. Great news – we have now completed this rollout of exact text search.

      Thank you again for your suggestion to allow exact text searching in JQL and for your patience.

      Best,

      Irene Ongkowidjaja

      Status Update 31/10/2022

      Hi everyone,

      This is Irene from the Jira team. Great news – we are now starting to rollout this feature. It's a progressive rollout, so some of you might see this update earlier than others. There will be two rollout milestones; we're currently rolling out Milestone 1, where we support phrase search on summary ~ and description ~. The Milestone 2 rollout will support more text fields – when it starts rolling out I’ll update you again.

      You can read more about this in our Community post. For future updates, you can also see our cloud documentation blog.

      Thanks again for your suggestion to allow exact text searching in JQL.

      Best,

      Irene Ongkowidjaja

      Status Update 15/09/2022

      Hi everyone,

      We’re excited to let you know that we’re starting work on this feature! While we don’t have a specific timeline on the delivery, we hope to roll it out soon and will update the status here when we have additional details.

      Best,

      Irene Ongkowidjaja

      Status Update 10/08/2022

      Hi everyone,

      We’re excited to let you know that we’re evaluating this feature. We’ll post more updates on this ticket.

      Best,

      Irene Ongkowidjaja

      Status Update 23/02/2022

      Dear users,

      We regret to inform you that after a technical evaluation, we have decided to move this issue to our long term backlog. We are also recategorizing the issue from “bug” to “suggestion” as it is a case of missing functionality.

      At the same time, we would like to acknowledge that this functionality is important and can be frustrating for you, and we are committed to fixing it.

      Our technical spike shows adding “exact phrase” to our current Jira Cloud JQL architecture will have a significant negative performance impact across Jira. We are continuing to explore alternate implementations to see if we can workaround this issue.

      Also, we are currently working on significantly improving JQL search architecture for performance and scale. If we are unable to find an alternate implementation with the current architecture, we will target a fix for this issue to this new architecture, which will remove the performance concern.

      Thank you for being patient.

      Jira Platform Product Management

       

      Currently there is no way to find an exact string using the text ~ or comment ~, etc, notations. Could we add another operator, something equivalent to 'contains exactly'?

      E.g. project = JIRA and text ~~ "this string of text" would return all JIRA project issues with "this string of text", with the individual words in that order.

       

       

            [JRACLOUD-21372] Allow exact-text searching in JQL

            Dear Atlassian, it's still 2023/06, and exact text search still doesn't work

            summary ~ "The single ticket with this simple summary as hell"

            Could you please fix this ASAP? thanks in advance!

            Note: I don't want to use backslashes for no reason, we are humans, not computers, thanks!

            Gábor Lovas added a comment - Dear Atlassian, it's still 2023/06 , and exact text search still doesn't work summary ~ "The single ticket with this simple summary as hell" Could you please fix this ASAP? thanks in advance! Note: I don't want to use backslashes for no reason, we are humans, not computers, thanks!

            There is a similar issue in https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/#Comment where an extra quoted quote has crept in to the fuzzy match example:

            • Find issues where a comment contains the words "My PC is quite old" (a fuzzy match):
              comment ~ "\"My PC is quite old"
            • Find issues where a comment contains the exact phrase "My PC is quite old":
              comment ~ "\"My PC is quite old\""

            I wanted to ask about something else which isn't quite clear: through a support request I've had it confirmed that any fuzzy search only searches in individual text fields and won't combine the results from separate text fields. So in the above example the first match (if correctly specified) would not find an issue with the words "My PC is" in one comment, and "quite old" in another. For that to work you have to AND results together, like comment ~ "My PC is" AND comment ~ "quite old"

            I discovered this because I was searching for a company name (typically used in a ticket summary) and a keyword which was only in a comment. The ticket, which I knew existed, wasn't returned. I found it through an indirect means, and did some testing.

            This seems counter-intuitive compared to normal web searches. They combine words across the page. I think it must be more clearly documented in those search articles. I also think that the basic search should combine multiple words using the AND syntax above.

            Hugh Gibson added a comment - There is a similar issue in https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/#Comment where an extra quoted quote has crept in to the fuzzy match example: Find issues where a comment contains the words "My PC is quite old" (a fuzzy match): comment ~ "\"My PC is quite old" Find issues where a comment contains the exact phrase "My PC is quite old": comment ~ "\"My PC is quite old\"" I wanted to ask about something else which isn't quite clear: through a support request I've had it confirmed that any fuzzy search only searches in individual text fields and won't combine the results from separate text fields. So in the above example the first match (if correctly specified) would not find an issue with the words "My PC is" in one comment, and "quite old" in another. For that to work you have to AND results together, like comment ~ "My PC is" AND comment ~ "quite old" I discovered this because I was searching for a company name (typically used in a ticket summary) and a keyword which was only in a comment. The ticket, which I knew existed, wasn't returned. I found it through an indirect means, and did some testing. This seems counter-intuitive compared to normal web searches. They combine words across the page. I think it must be more clearly documented in those search articles. I also think that the basic search should combine multiple words using the AND syntax above.

            Irene added a comment -

            006d0b71f2db  - Legend! Thank you for flagging that. We'll get that updated ASAP.

            Irene added a comment - 006d0b71f2db   - Legend! Thank you for flagging that. We'll get that updated ASAP.

            Dane Kantner added a comment - - edited

            The example given in the help doc at https://support.atlassian.com/jira-software-cloud/docs/search-syntax-for-text-fields/ is incorrect (the second variation is correct though)

             

            Under Advanced Search it says 

            text ~ "\"Jira Software"\"


            but the correct syntax is:

            text ~ "\"Jira Software\""


             

            ...easy enough to remember b/c it's really just that the \ is escaping quotes around the whole thing

            Dane Kantner added a comment - - edited The example given in the help doc at https://support.atlassian.com/jira-software-cloud/docs/search-syntax-for-text-fields/ is incorrect (the second variation is correct though)   Under Advanced Search it says  text ~ "\"Jira Software"\"
 but the correct syntax is: text ~ "\"Jira Software\""
   ...easy enough to remember b/c it's really just that the \ is escaping quotes around the whole thing

            Hi Irene,

            Thank you for the explanation and seems I like I can use it without the special characters for now. I have also gone ahead and voted for special characters addition and will wait for any update on it.

            Regards,

            Bharat Kalia added a comment - Hi Irene, Thank you for the explanation and seems I like I can use it without the special characters for now. I have also gone ahead and voted for special characters addition and will wait for any update on it. Regards,

            Irene added a comment - - edited

            Hi 7201df6d7075,

            Unfortunately, special characters in exact phrase searches are not yet supported.
            So if there are any special characters inside the exact phrase search, they will be ignored.
            This is also documented here.

            There is a separate request for supporting special characters. Please vote here https://jira.atlassian.com/browse/JRACLOUD-75866. It would be great if you are able to add more details on how or why special characters are important for your search. I'm also happy for us to chat more in person through Zoom if you find it easier to walk me through it. You can set up a time here: https://calendly.com/irenejira/feedback.

             

            Thanks,

            Irene

            Irene added a comment - - edited Hi 7201df6d7075 , Unfortunately, special characters in exact phrase searches are not yet supported. So if there are any special characters inside the exact phrase search, they will be ignored. This is also documented here. There is a separate request for supporting special characters. Please vote here https://jira.atlassian.com/browse/JRACLOUD-75866 . It would be great if you are able to add more details on how or why special characters are important for your search. I'm also happy for us to chat more in person through Zoom if you find it easier to walk me through it. You can set up a time here: https://calendly.com/irenejira/feedback .   Thanks, Irene

            Hi Irene,

             

            Thank you for the update and It seems to be working fine but one thing I have noticed is if we search an exact search match like the example below -

            Example :

            JQL for exact search match -

            description ~ "\"team = xyz\""

            Jira is looking for issues that contains " team  xyz" in the same order and it is skipping the "=". Can I not use "=" in string matching value? So If a description has "team xyz" it will return that issue as well. Is "=" reserved?

            Thanks,

            Bharat

            Bharat Kalia added a comment - Hi Irene,   Thank you for the update and It seems to be working fine but one thing I have noticed is if we search an exact search match like the example below - Example : JQL for exact search match - description ~ "\"team = xyz\"" Jira is looking for issues that contains " team  xyz" in the same order and it is skipping the "=". Can I not use "=" in string matching value? So If a description has "team xyz" it will return that issue as well. Is "=" reserved? Thanks, Bharat

            Very good. Thank you.

            Garrett Otto added a comment - Very good. Thank you.

            Confirmed, working for me. Thanks!

            Chris Geary added a comment - Confirmed, working for me. Thanks!

            Irene added a comment -

            Hi everyone,

            Great news, we have now completed this rollout of exact text search.

            Thank you again for your suggestion to allow exact text searching in JQL and for your patience.

            Cheers!

            Irene added a comment - Hi everyone, Great news, we have now completed this rollout of exact text search. Thank you again for your suggestion to allow exact text searching in JQL and for your patience. Cheers!

              iongkowidjaja Irene
              jsloat John Sloat (Inactive)
              Votes:
              621 Vote for this issue
              Watchers:
              335 Start watching this issue

                Created:
                Updated:
                Resolved: