Map Value: Workstreams and Work Items

Import Templates

Build out whole workstreams at once from a reusable Excel template: export a template, fill it in, preview the result, and import.

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.

Who can use this

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.

How templating works

  1. Export a template from a workstream to get a correctly formatted workbook that already mirrors your structure.
  2. Fill it in: adjust rows, or turn values into variables so the template is reusable.
  3. Import it under a target workstream. DevStride previews the result before creating anything.

Exporting a template

  1. In Map Value, open the ⋯ menu on the workstream's column and choose Export as Template (Excel).
  2. For assignees and boards, choose Fixed values to write the actual people and boards into the file, or switch to placeholders and give each one a Placeholder name so you fill them in at import time.
  3. Optionally set an Offset date (or tick Add date when importing and name the placeholder). Dates in the template are stored relative to it, so the same plan can be anchored to a new start date each time.
  4. Choose Export Template. The workbook downloads straight away, named after the workstream (for example 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.

Making a template reusable with variables

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.

Importing a template

  1. In Map Value, open the ⋯ menu on the workstream you want to import into and choose Import Template (Excel). Everything in the template is created beneath it.
  2. Confirm or change the Location.
  3. Click Upload Template (or drag the file in).
  4. If the template has variables, fill them in: Choose User, Select a Board, Select a Date.
  5. Review the preview, then confirm.

Referring to things by name

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.

Item types with several parents

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.

Bringing in real created and completed dates

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.

ColumnHeader in row 1What it records
VCreated DateThe day the item was really created.
WCompleted DateThe 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.

  • The headers must be there. DevStride reads these columns only when row 1 says 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.
  • You need the Backdate Item History permission. Workspace Owners always have it, and the Admin role has it too. An Owner or Admin turns it on for any other role in Configure Settings → Admin → Permissions (see Roles & Permissions). Without it, an import that uses either column is refused before anything is created.
  • The dates have to make sense. A date in the future is refused, and a Completed Date needs a Created Date on or before it. Like any other refused row, one bad date stops the whole import and nothing is created; fix the row and import again.
  • It is recorded quietly, as history. The item shows as created on its Created Date and, when it has a Completed Date, as moving into Done that day (an item created and finished on the same day finishes just after it was created). Nobody is notified and no automations run. Both entries carry the Backdated tag in the item's Activity.
  • Sub-items follow. When automatic statuses are on, a completed item's sub-items are completed with it.

To fix an item's dates after it has been imported, see Correcting an item's real history.

Where work can be imported

  • Into a workstream: always allowed, since workstreams hold any type.
  • Under a work item: only when the template's top-level items are a permitted child type of that item. A type with several permitted parents can go under any of them.

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.

Tracking imports

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.