...
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
...
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.It works the same way as the horizontal tables, mention a link on another requirement’s definition and it will be assigned as a dependency.
Vertical Requirements solve a lot of the hopes put in
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...