With your item types defined, go back to Map Value and build the map: workstreams first, then items inside them. A workstream has no dates; it is where work lives. Two levels of workstream is the rule of thumb; the item hierarchy carries the depth and drives reporting.
Example. A product engineering group has a core workstream Product Development with nested workstreams Product A, Product B, Product C. Inside each product, items follow the hierarchy Module → Capability → Task.


Click a workstream's name to rename it in place. Right-click for other actions (permissions, export, import template, archive), and drag the grab bar to reorder.






Every Task rolls up to its Capability, Module, and workstream, so the Product A column shows progress, estimates, time, and defects for the whole product.

Plans change. Drag an item's grab bar (1) to a new parent (2) and everything beneath it moves too, with all its data. Here the Welcome Message Capability and its Tasks move from the Login module to Dashboard.



Bulk edits, filters, selection, and the column menus are covered in Using the Map.
Next: back to Setting up Custom Fields, or if you have done that, the Item Workspace Tour.
Admin Onboarding - Create Custom Status Collections
Step 8b of admin onboarding — create statuses, group them into a collection with optional WIP limits, and assign the collection when you create a board.
Import Templates
Orientation for new admins: build an entire branch of workstreams and items from an Excel template — the fastest way to bring an existing plan or a large body of work into DevStride.