Derived from CONFDEV-37031, if you search with the CQL query 'text ~ "search:"' you'll get a server error. This was a critical bug when the text field was being used by the Confluence Search screen UI but has been demoted now that it only affects the API.

      See for an example:
      https://pug.jira-dev.com/wiki/rest/api/content/search?cql=text~%22search:%22

      where the error message in the 500 response is:

      java.lang.IllegalArgumentException: INVALID_SYNTAX_CANNOT_PARSE: Syntax Error, cannot parse search::
      

      //cc slancashire

            [CONFSERVER-39548] CQL Text field with colon caused server error

            This issue is mentioned in commits included in the Confluence 6.0.0-OD-2016.01.1-0003 release being approved for production: CPU-180

            Deleted Account (Inactive) added a comment - This issue is mentioned in commits included in the Confluence 6.0.0-OD-2016.01.1-0003 release being approved for production: CPU-180

            This issue is mentioned in commits included in the Confluence 6.0.0-OD-2016.01.1-0002 release being approved for production: CPU-179

            Deleted Account (Inactive) added a comment - This issue is mentioned in commits included in the Confluence 6.0.0-OD-2016.01.1-0002 release being approved for production: CPU-179

            This issue is mentioned in release Confluence 6.0.0-OD-2015.52.1-0001 just promoted to jirastudio-prd-virtual

            Deleted Account (Inactive) added a comment - This issue is mentioned in release Confluence 6.0.0-OD-2015.52.1-0001 just promoted to jirastudio-prd-virtual

            This issue is mentioned in commits included in the Confluence 6.0.0-OD-2015.52.1-0001 release being approved for production: CPU-171

            Deleted Account (Inactive) added a comment - This issue is mentioned in commits included in the Confluence 6.0.0-OD-2015.52.1-0001 release being approved for production: CPU-171

            mtran@atlassian.com tested on the latest deployment on PUG, 5.9.1-OD-2015.43.0-0328. It's quite possibly broken for any version with CQL.

            David Taylor (Inactive) added a comment - mtran@atlassian.com tested on the latest deployment on PUG, 5.9.1-OD-2015.43.0-0328. It's quite possibly broken for any version with CQL.

              rading Ran
              dtaylor David Taylor (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: