Info | ||
---|---|---|
| ||
Requirement Yogi 1.3 introduces additional features for the search, properties and a "RY Report" macro. |
Joe writes requirements. Joe wants to filter requirements per type, and...
...
Excerpt | ||||
---|---|---|---|---|
| ||||
How to use properties for requirements and what you can do with them. |
ℹ️ Related information: Search Syntax
If you want to learn how to get the perfect popup with properties, links and dependencies in less than 4 minutes, check out this tutorial:
https://youtu.be/-myl_nmpbGMUse properties to search for requirements
All columns of a table are |
...
saved as properties |
...
and you can search by this criteria. Let's take this example in the editor: |
...
The requirement will look like this: |
- The default title is the merge of all columns separated by " - ";
- Columns are saved by default as properties.
If the property name doesn't contain a space, the popup transforms them into a hyperlink, so they're searchable. Requirement Yogi automatically builds a small query to filter by this criteria. For example, if you click on "Category", it will build the query: @Category = "UI Changes"
.
| |
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: |
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: |
...
|
...
...
|
Create reports for those requirements
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.