Table Configuration

If your requirements are in tables, it is absolutely not mandatory. The Requirement Yogi configuration macro is useful to change the way your requirements are indexed and override column titles, or choose to put the 3rd column as the description instead of the 2nd.

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 dependencies in the following columns.

It also works for vertical tables: rows will be identified as columns. (Ex: 1st row in your vertical table will be mapped as the 1st column in the Configuration macro, 2nd row to the 2nd column, and so on.).

This table:	Gets indexed as:

This table:	Gets indexed as:

Here is the default configuration for requirements in tables:

With the configuration macro, you can:

Rename properties.
Change the column type.

Here, I changed the column of "Author" in "Original Author".
The "Dependencies" column was indexed both as a dependency and as a property, so we added a 4th column to the configuration macro and unchecked the indexing as a property, and set it to Dependency
We ticked “Apply to all the following tables in the document", if this is unticked, the configuration will only apply to the following table. This configuration is not global, you need to add the macro to every Confluence page with requirements.

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.

Requirement Yogi (Cloud)

Table Configuration

Analytics

Related content