Import from External Sources

In brief: Import plans from external systems into TestChimp markdown format, organize in folders, and sync to Git so agents and SmartTests inherit structured requirements.

TestChimp can import User Stories and Test Scenarios from external tools into your Test Planning workspace — from issue trackers (Jira, Linear) and from TestRail test cases.

Where to find it

In Test Planning, open the Import / Export menu and choose Import from… → Jira, Linear, or TestRail.

Jira + TestRail onboarding

Many teams keep user stories in Jira and test cases in TestRail. TestChimp supports that split:

1. Import stories from Jira — in the Jira wizard, leave Test scenario issue type blank if scenarios live in TestRail (stories-only import).
2. Import test cases from TestRail — each TestRail case becomes a TestChimp scenario.
3. Automatic story links — when a TestRail case has Jira references in its refs field (or per-step refs), TestChimp matches them to Jira-imported stories by ticket key or id and creates the many-to-many mappings. Cases whose refs do not match an imported story are still imported; only the link is skipped.

This mirrors how TestRail links cases to Jira tickets while TestChimp models stories ↔ scenarios as many-to-many.

How imports work (common behavior)

• What gets created
  • User stories are imported as TestChimp user stories.
  • Test scenarios are imported as TestChimp test scenarios (linked to their parent story when applicable).
• Credentials
  • Credentials are one-off for the import wizard and are not stored.
• Preview before import
  • The wizard shows a preview of how many stories/scenarios will be imported before you start the import.
• File & folder behavior
  • You can choose a file naming strategy (external ID, TestChimp entity ID, or AI deduce).
  • You can choose a folder structure strategy (group by a field/label, or AI deduce).
• Undo
  • After an import, you can use Import / Export → Revert recent import… to delete everything created by the most recent import.
• Progress for large imports
  • TestRail imports run as an async job with live progress in the wizard (case fetch counts and phase messages). Jira and Linear imports use the same pattern when volumes are large.
• Free trial limits
  • Jira / Linear: up to 25 imported user stories.
  • TestRail: up to 100 imported test cases (scenarios).

Jira

The Jira import is a 5-step wizard.

Step 1: Configure Jira

Provide:

• Jira URL (e.g. https://yourcompany.atlassian.net)
• Email
• Jira personal access token (Atlassian API token)
• Project Key (e.g. PROJ)
• JQL (optional) to further narrow what is imported

Then click Next: Select issue types.

Step 2: Issue types

Select the Jira issue type to treat as:

• User story issue type (required)
• Test scenario issue type (optional) — leave blank if test cases live in TestRail or another tool; only stories are imported

Then click Next: Labels to preview counts and continue.

Step 3: Labels (optional)

Choose which Jira fields should be imported as labels in TestChimp.

Step 4: File & folder

Choose:

• File naming
  • External ID (e.g. PROJ-123)
  • TestChimp entity ID (e.g. US-1, TS-1)
  • AI deduce
• Folder structure
  • Use a specific field (pick the Jira field to group into folders)
  • AI deduce

Step 5: Import

Click Start import and wait for the import to finish. When it completes, the wizard shows how many stories and scenarios were created.

TestRail

The TestRail import is a 5-step wizard. It imports test cases as scenarios only (not user stories). Use it after a Jira stories import when your team splits requirements and test cases across those tools — see Jira + TestRail onboarding above.

Step 1: Credentials

Provide:

• TestRail URL (e.g. https://yourcompany.testrail.io)
• Email (same login you use for TestRail)
• API key (from TestRail My Settings — not your account password)

API access must be enabled in TestRail under Admin → Site Settings → API. Generate the key under My Settings, then click Save Settings.

Then click Next: Select project.

Step 2: Project

Select the TestRail project to import from.

• For projects that use multiple test suites, also select the test suite.
• Title filter (optional) — narrow cases by title substring (e.g. login).

Then click Next: Preview.

Step 3: Preview

The wizard shows how many Jira-imported stories exist in the project (for linking) and lets you count test cases before import.

• If no Jira stories are present, scenarios import without story links (you can link later in Test Planning).
• Click Count test cases to see how many cases match your selection.

Then continue to Options when the count looks right.

Step 4: File & folder

Choose:

• File naming
  • External ID (e.g. C4075)
  • TestChimp entity ID (e.g. TS-1)
  • AI deduce
• Folder structure
  • Use TestRail section hierarchy
  • AI deduce

Step 5: Import

Click Start import. The job runs asynchronously; the wizard shows fetch progress and status messages. When it completes, you see how many scenarios were created or updated and how many story links were created from TestRail Jira refs.

Errors and free-trial skips (cases beyond the 100-case limit) are reported in the completion summary.

Linear

The Linear import is a 5-step wizard.

Step 1: Configure Linear

Provide:

• Linear API key (from Linear Settings → API)
• Team Key (e.g. ENG)
• Filter query (optional) to further narrow what is imported

Then click Next: Select labels.

Step 2: Labels (story/scenario)

Pick the Linear label that identifies:

• User story label
• Test scenario label

Important: Linear test scenarios must be sub-issues (child issues) of their parent story issues for linking to work correctly.

Step 3: Tag labels (optional)

Select additional Linear labels to import as tags in TestChimp.

Step 4: File & folder

Choose:

• File naming
  • External ID (e.g. ENG-123)
  • TestChimp entity ID (e.g. US-1, TS-1)
  • AI deduce
• Folder structure
  • Use a specific label (pick the Linear label to group into folders)
  • AI deduce

Step 5: Import

Click Start import and wait for the import to finish. When it completes, the wizard shows how many stories and scenarios were created.