Date: Fri, 29 Mar 2024 08:33:55 +0000 (UTC) Message-ID: <823584997.11567.1711701235832@catch-kbase-p> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11566_489028175.1711701235831" ------=_Part_11566_489028175.1711701235831 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
By default Expressions are evaluated from Left to Right (left associativ= ity), so the following query:
Entity= Type =3D Requirement OR EntityType =3D Incident AND Type =3D Bug
Would be interpreted as:
(Entit= yType =3D Requirement OR EntityType =3D Incident) AND Type =3D Bug
But in the case above, our intention may be to include all requirements,= but only those incidents which are of type bug - to force evaluation to oc= cur in the correct order, you can surround parts of the expressions in roun= d brackets (parentheses):
Entity= Type =3D Requirement OR (EntityType =3D Incident AND Type =3D Bug)
When using the pre-fix operator Not It= 's recommended that you should use groups to make the intention of the quer= y clear.
So for example this expression:
Not En= tityType =3D Requirement OR EntityType =3D Script AND Project =3D 'Project = X'
Will be interpreted as:
(Not (= EntityType =3D Requirement OR EntityType =3D Script)) AND Project =3D 'Proj= ect X'
This may not be your intention, or at least might be surprising. The way= to resolve this is to surround the Not and the values it should operate on= within a group e.g.
(Not (= EntityType =3D Requirement)) OR EntityType =3D Script AND Project =3D 'Proj= ect X'