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

Version 1 Next »

Release 1.3

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...

Honestly, that's awesome. All columns of a table are now saved as properties. 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".

Cleaner descriptions for your requirements: The "RY Property" macro

To achieve the configuration of the last paragraph, we've added a small macro in the headers of the table. You can see it on the first screenshot, it is tiny in order to not disturb the layout. 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. It could be a good thing to do in order to have a simple name for the property.

 

 

 

 

  • No labels