Teams and workspaces · Taskending editorial team
How to evaluate an import preview
A preview helps catch mapping and scope errors before writing data. A successful preview alone does not prove complete contextual accuracy.
Updated: · 1 min read
How to apply it
Prepare a small representative package in Taskending’s supported JSON format. Inspect records to be created, matched or rejected. Correct identity, status and project mappings before a broad import. Verify an independent backup beforehand.
A concrete example
Include a child issue, a support record with comments, a closed-sprint issue and an attachment reference. Testing only simple title-and-description records hides the difficult parts.
What to watch for
Data can change between preview and application. Version the source package and mapping decisions. Loading more records will not repair a duplicate key or incorrect user match.
How to check the outcome
Compare source and target examples after rehearsal. Verify repeat-run behavior and that intended users can reach the imported context.
Try it in your own workflow.
Create a company workspace and your first issue. Taskending is currently free.
Start for free