Excel templates create a whole branch of work (workstreams, their items and sub-items, and the structure connecting them) in one import instead of item by item. You export a template from existing work, fill it in or reuse it as a blueprint, and import it under any workstream you choose.
Because the template is a spreadsheet, it is also the fastest way to bring a large body of existing work into DevStride, even from a tool with different column names and no notion of a workstream. The exported workbook gives you the columns and parent-child layout DevStride expects; you map your rows into it and DevStride rebuilds the hierarchy on import.
Export as Template (Excel) and Import Template (Excel) need the Manage import history permission. It is bundled in the Manage org settings template, so by default Admins and Owners have it and Members do not; a custom role can be granted it. Importing also needs edit access to the target workstream, the same access that lets you add items there. See Workstream & Item Permissions and Roles & Permissions. An import that fills in the Created Date or Completed Date columns also needs Backdate Item History (see Bringing in real created and completed dates).
Both entries live in Map Value, on the ellipsis (⋯) menu at the top of a nested workstream column (never the root Core Workstreams column), and Export as Template (Excel) is also on a workstream's right-click menu.
Product_template.xlsx). It comes from DevStride's own address, so networks that block outside file-storage links still let it through.The workbook captures the workstream and everything beneath it: items and sub-items with their types, dates, estimates, priorities, tags, custom fields, assignees, teams and boards, each on its own sheet. Multi-value cells use a delimiter, | by default.
A variable is a named placeholder (a user, a board or a date) that you fill in at import time instead of hard-coding. One onboarding template can then be imported for a different new hire, pointed at a different board, or anchored to a different start date. Every variable a sheet uses must be declared on the variables sheet, or the import stops with Variable … is not defined in the variables sheet.
You do not need internal IDs. Refer to parent items by number or title, item types by name, assignees by username, teams by name, and member roles by role name on the Users sheet. Spell them as they appear in your organization so everything resolves.
On the Settings-WorkTypes sheet, column C lists each type's permitted parent types. A type that can sit under several parents lists them all in that cell separated by the delimiter, for example Feature / <id>|Epic / <id>; the first is the type's primary parent. An exported template fills this in for you.
When you migrate work that already has a history, the WorkItems sheet can carry when each item was really created and finished, so cycle time, burndown and completed dates in DevStride follow those real dates instead of the day you ran the import.
| Column | Header in row 1 | What it records |
|---|---|---|
| V | Created Date | The day the item was really created. |
| W | Completed Date | The day the item was really finished. It is moved into Done on that day. |
Both columns are optional. Enter dates as YYYY-MM-DD or as real spreadsheet dates.
Created Date and Completed Date (capitals and spacing don't matter). A template you export now includes both headers, with the cells empty. A template exported before October 12, 2026 has no such headers, so dates typed into those columns are ignored: add the two headers, or export a fresh template.To fix an item's dates after it has been imported, see Correcting an item's real history.
An incompatible location is refused with: Cannot import here. The template contains root-level items of type "…" which cannot be children of "…". Please select a compatible parent item type or a workstream. The check runs in the preview and again if you change the location.
Every run is recorded. Open Configure Settings and choose Import History (visible with the Manage import history permission). Each run lists its Import ID, Started, Finished, Ran By and Status (pending, running, finished or failed). A failed run shows the details, including per-row problems such as a parent that could not be found, so you can fix the row and import again. An import is all or nothing: every row is checked before anything is written, so a run that refuses any row creates nothing at all, and there is nothing to clean up before you try again. See Import History.
Workstream & Item Permissions
Control who can view, comment on, edit, or manage your workstreams and work items at the user, team, and organization level.
Finding Your Way Around
How the DevStride interface is laid out after the 2026-10-18 refresh: the sidebar and its areas, each area's colour on the page, dialogs that glow while the page dims, the item drawer, the Help section, and the signed-out screens.