All columns of a table are now saved as properties. Every column is a property and you can search by this criteria.
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
Honestly, that's awesome. 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:
The requirement will look like this:
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'.
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:
Ok, it's the "RY Report" macro. But wait...
Now that we have properties, could we display them as a column? Yes! On 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".
We've improved the search syntax. You can search by page, by JIRA issue or by property.
|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.|
|jira = 'JRA-21'||All requirements linked from the issue JRA-21.|
|@Category = 'Functional'||The user-defined property Category must be "Functional".|
See Search Syntax for more information.