Working with items
The day-to-day actions you'll use in every module — create, reuse, organize, edit, link, attach, lock, and export — done from the shared tree and item view.
Most of your work in TraceUnified happens on items — requirements, architecture elements, test cases, risks, SBOM components. Whatever the module, items behave the same way: they live in a tree on the left, they open into a record with fields, lifecycle, and history, and they share one set of actions. Learn these once and they carry across Requirements, Architecture, Tests, Risks, and SBOM.
Where the actions live
There are three places you’ll act on items, and most tasks use one of them:
- The tree — right-click any item, folder, or the project root for its context menu (create, reuse, move, rename, delete, change owner or status, send for review, lock, export). This menu is shared across modules.
- The toolbar — the + Add button above the tree creates items in the current module without right-clicking.
- The item view — open an item to edit its fields, manage its links, and add attachments.
How these guides are written
Each task below is a short procedure: what you need before you start, the numbered steps, and the result you should see. They look like this:
Before you start Have a project open and a module selected.
- Do the first thing.
- Do the next thing.
Result What you'll see when it worked.
In this guide
- Creating items, folders & sets — add items, child items, folders, and sets
- Reusing & duplicating items — reuse across the tree or across projects, and make independent copies
- Moving, renaming & deleting items — reorganize the tree and restore from the trash
- Editing, versioning & lifecycle — edit under change control, create versions, change owner and status, send for review
- Links & attachments — connect items on the thread and attach files
- Locking, exporting & bulk actions — lock records, export, save views, and act on many items at once
Note What appears on the menu depends on your permissions, the item's lifecycle state, and how your administrator configured the module — so you may see more or fewer actions than shown here.