...
When you define requirements in table, by default, the requirement key will be in the first column, with a description in the second column, and properties and depencies in the following columns.
This table: | Gets indexed as: |
---|---|
Here is the default configuration for requirements in tables: With the configuration macro, you can:
| |
| |
After inserting the macro and publishing the edited Confluence page, my requirement is now indexed with the changed properties as: |
You can quickly "unindex" the requirements in a page by adding a configuration macro at the top of the document and uncheck the requirements column. It can be useful when you have duplicated requirement definitions.
Paragraph Configuration
When you define requirements in paragraph or headings, by default, the description of the requirement is the following text. Requirement keys in paragraphs: |
Here are my requirements: | ||
...
When requirements are in headings
You can ignore the numbered headings by passing a regular expression specifying the numbering format. My headings: | |
will get saved as: |
Here are a few common ways to number headings and their regexes:
...