Every run of an import template is a background job, and Import History is where you check on it: whether it is still running, whether it finished, and exactly which rows failed when it did not.
Configure Settings → Other → Import History. The page needs the Manage import history permission, which the default Owner and Admin roles hold; grant it to a custom role on its own if someone who runs imports should be able to check on them without the rest of Settings.
Each row is one import job, newest first:
| Column | Shows |
|---|---|
| Import ID | The first eight characters of the job's id. Hover to see the full id; quote it to support if you need help with a run. |
| Dates | When the job was queued and when it last changed. |
| Status | Pending, Running, Finished or Failed. |
| Errors | For a failed run, the number of errors and each failing row's message. |
A completed import has created everything the preview promised; the new branch is in the Map at the workstream you imported into. A failed import names each row that could not be created and why — a name that resolved to nothing, a type the target cannot hold, a parent that is missing or archived, a date in the wrong shape. An import is all or nothing: DevStride checks every row before it writes anything, so a failed import has created nothing and left nothing half-built. Fix the workbook and import again; the page keeps every run, so you can compare attempts.
Teams
Create teams, add and remove members, set a team's business hours for Service Desk, and archive teams you no longer use.
Formatting Rules
Make items in chosen statuses stand out everywhere: a red, struck-through title and an X on the item icon, so cancelled work reads as cancelled on every screen.