Skip to end of metadata
Go to start of metadata

In version 2.1.2, we've made it possible to define requirements in vertical tables.

Vertical tables

The first section of this page represents a requirement defined in a vertical table:

Rows of the table are mapped to properties:

To define requirements in a vertical table

Important: Use the "Heading" button to set the first column gray. Don't just paint the background in gray and don't just make the text bold.

  • 2 columns exactly,
  • At least 3 rows,
  • The first column must be a header (the <th> element, or one must have used the "Heading column" icon in the toolbar),
  • The second column must be white cells (the <td> element).
  • No cell must be merged,
  • A requirement definition must be present.

Features

  • It is possible to use dependencies, properties and the RY Property macros, like for normal table,
  • Child requirements on the page are linked using the relationship "parent".

Dependencies

All requirements defined in the page after the vertical table, will be linked to the requirement defined in the vertical table, with the relationship "parent".

As such, in the example above, HFGE-123 has a dependency to the parent BRW-455:

However, the reversed dependencies displayed in the parent requirement might be too big to display. If there are more than 25 dependencies from a parent to its children, we limit the list to 15 and display the total count instead.

Vertical Requirements solve a lot of the hopes put in  RY-107 - Getting issue details... STATUS , so please try them and give us some feedback after using them.


  • No labels