Aglet

How to triage an import mapping error for a clear scope

Import confusion is often a contract problem: people cannot tell what they may provide, what will change, or what remains after an error. Triage the actual workflow under review and its supported boundary. Do not assume a provider connection, live import, or automatic recovery exists because an interface mentions source data.

Establish what is happening

  1. Capture the proposed input

    Record the synthetic file or source shape, field names, row count, mapping choices, and visible instructions. Note whether the flow accepts the input at all and which route owns it. Remove personal data and credentials before saving a fixture or screenshot.

  2. Exercise result variants

    Use a valid small fixture, a missing field, an invalid value, a duplicate row, an empty input, and an interrupted submission where the workflow supports them. Compare preview, validation, saved records, and final message. Keep unsupported variants explicitly out of scope.

  3. Name the user decision

    Mark whether the person is choosing a mapping, confirming a partial save, retrying a rejected input, or merely reading help. Record unclear terms and the next action offered. Separate copy ambiguity from data correctness and persistence evidence.

What to carry forward

Triage is complete when the import boundary, expected input, user decision, outcome, and saved-state evidence are recorded for a synthetic case. If no supported import path exists, document the confusion as a discoverability or expectation issue without promising a new importer.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow