Currently, we have provided some example Item Types with the Sample Set. You can configure the types your company needs under the Organization settings -> Item types.
Creating an item type
Click the "+ New type" button and give a name to your item type
Create a unique identifier for your type, that will be used to form the item's IDs. It can be between 2-8 characters, like "REQ" for "Requirement" item type
Choose an icon, that will be used to display any item of that type in places such as Tree, Traces, or Table view
Add attributes for your new type by clicking on the "+" button and deciding where they will be displayed: document view or sidebar. If you want one of them to act as a header you can select it by enabling "Set as item header"
When creating attributes you can also give additional instructions about the content of the attribute, which the AI will use to generate content for that type.
Enable/disable quality checks for each attribute, if you want for example by default only descriptions are to be checked against our quality rules but not rationales or titles
Creating reusable drop-downs
Sometimes you want to be able to reuse the same dropdown, like a status or component, for multiple item types. You can create and manage such dropdowns under Organization settings -> Item types / Dropdowns.
You can either create a new one from here or when you create a new item type and select a dropdown attribute type.
In the creation modal, you can decide if you want it to be a single or multiple option, you can give colors to each option the user will select, for example, you can use traffic light colors to indicate a priority, and you can also create a dropdown based on existing one, without having to manually copy all those values.
Traceability rules
For every item type you can define a set of rules used for tracing. These rules apply to relationships between different item types—such as from item type A (the current item) to item type B.
For each A → B relationship, you can configure:
Type of trace: Define the direction of the trace—whether it’s a related link or a downstream dependency from type A to type B.
Required trace: Specify whether every item of type A must have at least one trace to an item of type B.
Suspect logic: Indicate whether changes to an item of type A should mark related items of type B as suspect—meaning they may need review and clearance after the change.
Here, you can also decide if you want to let users create traces outside of these rules.
These rules are reflected in each item’s sidebar, under the Traces section—where you can quickly check for missing traces, suspects and more.
