Page Comparison

...

Keyword	Function
AND, OR, NOT	Boolean operators
= '...' == '...'	Strict equality.
~ '...%...'	Soft equality. Use % in the string as a wildcard.
@...	Reference to a property of the requirement (if you've defined requirements in columns).

...

Field	Definition
key = ...	The key of the requirement. Keys are unique per space.
spaceKey = ...	The space key of the requirement (case sensitive).
baseline = ...	The baseline name or number , between quotes . All statuses are implicitly included. Quotes were required before version 2.4: baseline = '1'
status = ...	The status of the requirement (ACTIVE, DELETED, MOVED). Default: ACTIVE. There is generally no reason to use it, since those statuses are internal details about requirements. You would rather define your own property named "Status", and search them using @status = 'Approved' for example. Do not confuse "status" (our internal implementation detail) and "@status" (any user-defined property).
text = ...	The contents of the requirement (Does not include the properties).
page = ...	The ID of a page linked to the requirement.
jira = ...	A JIRA issue linked to the requirement.
jira@relationship = ...	A JIRA issue linked with a specific relationship
@aproperty = ...	A property with name "aproperty"
to@arelationship = ... from@arelationship = ...	A dependency with the relationship "arelationship".
excel = ...	The ID of the attachment were those requirements are defined.

Formatting, lists of properties, etc.

Since Release 2.4 - Improvements to the search, we support emoticons such as etc. ! We also support lists! How does it work?

Thanks to this, you can search with:

@property = '(/)' → Searches for the emoticon
@property = 'item1' → Searches for a property which has the item "item1" in the list. Note that the list may also have "item2", "item3", etc.
@property = user('admin') → Searches for the mention of the user 'admin' or the user key 'admin' (the second one will be stable over time, even if the username changes).