Requirements, Use Cases, and User Stories can be nested, for example a requirement can own multiple child requirements. You can use nesting to help organize your project, for example you can break up summary use cases or epic stories into smaller more manageable chunks, or create a hierarchy of requirements where the parent serves as a general category and the children are specific measurable requirements within the category.
To create a new nested item: right click on an existing item in the main list or the project browser and select Add Child.
To change an existing top-level item into a child of another item: drag the item that you wish to make a child and drop it onto its new parent. Alternatively, use the green right-arrow button shown above the project browser to make the selected item a child of the item shown above it.
To change a child item back into a top-level item (unnest): drag the child item and drop it on the package which it should belong in. Or use the green left-arrow button shown above the project browser.
- When you nest an item, it's ID will change to use hierarchical numbering based on the owner, e.g. children of REQ-2 will be REQ-2.1, REQ-2.2, etc. Likewise, when you un-nest a requirement, the hierarchical ID numbering will be removed.
- You may nest items as many levels deep as desired.
- When using drag/drop to change ownership, you may use either the main list view or the project browser.