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 17 Next »

ℹ︎ Related information: Search Syntax

Use 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:

  • Each column is both included in the title and in the properties,
  • In the current situation, we've defined that the first column was the title.
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





  • No labels