...
| Table of Contents | ||
|---|---|---|
|
Tables and lists
We don’t flatten lists and tables anymore.
Bug scenario: None expected, this one will only make the users happier 🎉
Only the second column is used for the description
We only use the first cell as the body of the requirement. All the other cells are stored as properties, and the text of properties is not repeated in the cells.
...
Rationale: Users didn’t understand why the same text was repeated in the description and properties. In most cases, the description of the requirement is indeed in the 2nd column, and in other situations, the RY Property macro can be used.
Links
We store the entire URL.
Bug scenario: If the URL of your Confluence changes, then links will point to the old URL.
...
Rationale: When we are not using the entire URL, requirements displayed in Jira wouldn’t link to the correct page.
Images
Vertical tables at the top of requirement pages
Scaffolding
Please report any difference that is affecting your business.
...