On this page

An item is a unit of work. An item type says what level of your hierarchy it sits at and which types may nest beneath it. DevStride enforces the hierarchy everywhere: in the Map, the item drawer, imports, forms, and AI item creation. Reports roll up by it.

This is the most consequential step in the guide, and it comes before populating workstreams for a reason: once items exist as a type, moving that type around the hierarchy means converting those items. Spend ten minutes on the design now.

Item hierarchy in Map Value

Designing the hierarchy#

Ask what you call the big things, the middle things, and the small things, and what you want to report on. Some examples:

Kind of work Hierarchy
Product engineering Module → Capability → Epic → Story and Defect
Scaled agile Epic → Feature → Story and Defect (the starter set)
Simple projects Objective → Task (also in the starter set)
Marketing Client (or Initiative) → Campaign → Objective → Task

Rules of thumb:

  • One hierarchy per kind of work is fine; a marketing tree and a product tree can coexist. Different workstreams simply use different trees.
  • Three or four levels cover most organizations.
  • Add a level you might want later now. You can add types at any time, but existing items do not move into a new middle level by themselves.
  • A type can have more than one parent type: allow Story under both Feature and Epic so small work can sit directly on an Epic.

A new organization starts with a default type Item (which cannot be deleted or given a parent), plus Epic → Feature → Story / Defect and Objective → Task. Rename, re-parent, or delete these to fit your design.

Multiple hierarchies

Teams whose work looks nothing alike should not share a hierarchy. This example shows three side by side: marketing, organizational initiatives, and product engineering.

Several item type hierarchies in Manage Item Types

Create your item types#

Open Configure Settings → Data Model → Item Types. The Manage Item Types tree shows every type under each of its parents.

Manage Item Types with New Item Type

  1. Click New Item Type.
  2. Enter a Label (at least three characters), for example Module.
  3. Leave Parent Item Types empty, shown as None (top level), for the top of a hierarchy.
  4. Pick a Badge Color and click Create.

New Item Type dialog for a top-level type

  1. Repeat for the next level down, this time choosing the parent in Parent Item Types, for example Capability under Module.

New Item Type dialog with a parent selected

Forgot the parent? Click the pencil on the type and set Parent Item Types there.

Edit Item Type showing Parent Item Types

Several parents. Pick more than one type in Parent Item Types and the type is allowed under each; the tree draws it under every parent and edits apply to all copies. The first parent is the primary one, used where only one place can be shown; change it with Make primary. You can add a parent at any time, but removing one is refused while items of that type still sit under items of that parent type. See Choosing parent item types.

Changing the hierarchy later#

  • Adding a type or an extra parent is always safe; nothing existing changes.
  • Deleting a type is only possible while no items (including archived ones) use it. Its child types move up to its parents.
  • Changing one item's type is done from the item itself; converting a parent and all its children at once is done with Item Type in the bulk-edit menu, which checks that every item still fits before committing. See Changing an item's type.

Inserting a middle level after items exist is a migration

If you later need a new level between two existing ones, create the type, then use the bulk type change to convert existing trees into the new shape. It works, but it is a project. Putting a placeholder level in now is cheaper. Contact DevStride Support if you want help.

Time can be logged at any level

Time entries are allowed on items of any type and roll up to parents. An administrator can restrict entries to bottom-level types with Allow Parent Item Time Entries, on by default.

Next: Populating and Managing Workstreams to create items of these types, then come back for Custom Fields.

Powered by DevStride