Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Database vendors

Criteria such as "jira", "page" or "properties" are readily supported in PostgreSQL and MySQL. If you use other vendors (Oracle, MS SQL...) and those criteria fail, please contact us and we'll fix them for you.

 

Requirement Yogi provides a search screen in every space.

By default, only active requirements of the current space are displayed. Use the URL to display deleted requirements or to search across spaces.

Examples

Note: All those examples require Requirement Yogi 1.3.

QueryResult
key = 'IG-1'The requirement with the exact key.
key ~ 'IG-%'All requirements starting with 'IG-'.
text ~ '% something'All requirements whose text ends with 'something'.
page = '467382'All requirements defined on the page with ID 467382.
page ~ '467382'All requirements defined or linked on the page.
jira = 'JRA-21'All requirements linked from the issue JRA-21.
jira@implements = 'JRA-21'All requirements linked from the issue JRA-21 with the relationship "Implements" (since version 1.5)
NOT (jira ~ '%')Requirements which are not linked to any JIRA issue.
@Category = 'Functional'All requirements where the property 'Category' = 'Functional'.

Keywords

KeywordFunction
AND, OR, NOTBoolean operators
= '...'Strict equality.
~ '...%...'Soft equality. Use % in the string as a wildcard.
@...Reference to a property of the requirement.

Fields

FieldDefinition
keyThe key of the requirement. Keys are unique per space.
spaceKeyThe space key of the requirement (case sensitive).
statusThe status of the requirement (ACTIVE, DELETED, MOVED).
textThe contents of the requirement (Does not include the properties).
pageThe ID of a page linked to the requirement.
jiraA JIRA issue linked to the requirement.
  • No labels