To add a configuration macro, in the page edit mode, type /requi or /config, or click on the + dropdown like you would to add any other Confluence macro.
After adding a macro to the page, you can edit it simply by clicking on the macro:
Read this documentation page to learn how to use the requirement configuration macro and change the way your requirements are indexed. |
It is absolutely not mandatory to use a Configuration macro, but it will help you customize your requirement detail with property and dependency names.
Follow this tutorial to know how to add properties to requirements, and dependencies. And how to customize their names to simplify your requirement detail: https://youtu.be/891Q3OpCiLA?si=iaWgX2gN_TQj5L0Q |
To add a configuration macro, in the page edit mode, type | |
After adding a macro to the page, you can edit it simply by clicking on the macro: | |
It is also possible to add a Configuration macro from the view mode, with the Transformation wizard, and then apply it in bulk to multiple pages. See documentation here: Transformation wizard: Transform your pages .
Table configuration: Let’s you exclude content from being indexed as a property or dependency; Change the name of the property displayed in the detail vs the confluence page.
Paragraph Configuration: If you write requirements in paragraphs instead of tables, this let’s you configure the name of the property, and the relationship to requirement links.
Document Configuration: This is the evolution of the paragraph configuration. We call this feature Linear Documents. It is best suited when requirements are written outside of tables, when you reuse public standards or your customer’s requirements. It let’s you create requirements from text headers, configure more properties and dependencies.
Parent requirement configuration: If you have defined one requirement in a table, and want to index all following requirements as children.