...
Defining key patterns: As a project is gaining maturity, key patterns for requirements are established. Administrators can define which are the main keys, and even lock down the keys that can be inserted in spaces,
Validations: Administrators can define properties and dependencies which are required for a type of requirement.
Templates: When users insert such keys in an empty table, it will setup the table with all the properties, by default.
How to define key patterns?
Each time you create a new requirement, the key will be entered to the key suggestions list. If you want a key suggestion to become a requirement type, simply edit the suggestion and give it a name.
...
Only space administrators can configure requirement types. Users have access to this screen in read-only mode, the only action they can perform is reset the sequences.
...
...
How to edit requirement types?
Properties are described as a horizontal table, so it looks like the final page.
Tip: The only difference between a simple “key suggestion” and a requirement type is having a name. When you add a name, it gives you access to all of the options. (See docs for Key Suggestions)
...