Uploaded image for project: 'Atlassian Intelligence'
  1. Atlassian Intelligence
  2. AI-680

Allow contains operator ~ for space and space.key fields in the Search REST API to allow partial match

XMLWordPrintable

    • 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.

      Summary

      Allow partial match when searching for spaces using space or space.key fields

      Otherwise, we need to fetch all spaces from the paginated REST API and filter them in the frontend code.

      Expected Results

      E.g. a request with a query of "ex" would return a list of spaces like 

      ...
{"key": "external", "name": "external content"}, 
{"key":"example", "name":"example space"}, 
{"key":"xyz", "name":"extra space"}
...

      Note

      Although using contains operator with the space field is not supported based on the documentation, for some instances it does work.

      /wiki/rest/api/search?cql=space ~ "ex*" AND type = space

        1. contains_op_in_space_field.jpg
          contains_op_in_space_field.jpg
          298 kB

            [AI-680] Allow contains operator ~ for space and space.key fields in the Search REST API to allow partial match

            Matthew Hunter added a comment -
            Atlassian Update - September 9, 2022

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - September 9, 2022 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

              Unassigned Unassigned
              53106592bb6d Jon Bevan [Adaptavist]
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: