| Info | ||
|---|---|---|
| ||
The additional features for the search, properties and "RY Report" presented in this page were introduced in Requirement Yogi 1.3. |
See also: Search Syntax
Filter requirements by type
...
Use properties to search for requirements
All columns of a table are now saved as properties . Every column is a property and you can search by this criteria. Let's take this example in the editor:
...
Requirement Yogi helps you build the query for each property if the name is short (<80 letters) and without space. For example the property "Category" becomes hyperlinked in the popup, which leads to the search screen with the preset query: @Category = 'UI Changes'.
Build clean descriptions for your requirements: The "RY Property" macro
To achieve the configuration of the last section, we've added a small macro in the headers of the table. You can see it on the first screenshot, the name is "RY Properties". Here are the options:
...
- Anywhere on a requirement, you can define a property and its value.
- If it's in a column header, it applies to the whole column.
- You can "rename" the column for the purpose of the properties. Searchable columns can't contain a space.
- You can "ignore" the column, if the contents are irrelevant for the requirement.
- You can set which column contains the correct description of the requirement by ticking "Title".
Create reports for those requirements
Ok, it's the "RY Report" macro. Now that we have properties, could we display them as a column? Yes! In the example below, we don't only display all properties in a list below the description, we've also configured the property as a first-class column named "Category".
What's more? The "Resolves" only contains JIRA issues which have the relationship "Resolves".
...
- Go to Traceability matrix to create a report with those properties,
- Go to RY Reports to learn how to create a report on a page about requirements,
- Go to Search Syntax to learn how to search by property.