Properties and RY Report

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

Joe wants 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.
  • 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".

And Joe wants to make nice reports with those requirements...

Ok, it's the "RY Report" macro. But wait...

Now that we have properties, could we display them in 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? We can also filter JIRA issues by type of relationship. In the screenshot above, it only displays linked issues with the relationship "Resolves" in the 3rd column.

Search...