TestApp.io provides a set of powerful features shared across the JIRA and Linear integrations that give you granular control over how your tasks and issues are managed. Whether you need to temporarily pause syncing, bulk-import issues, migrate local tasks, or audit sync activity, these tools help you stay in control.

This guide covers the key power features available for both the JIRA and Linear integrations.

1. Enable and Disable Your Integration

Sometimes you need to pause an integration without fully disconnecting it — for example, during a major reorganization or when troubleshooting an issue.

TestApp.io lets you toggle your JIRA or Linear integration on and off:

  1. Go to Team Settings → Integrations and select your integration (JIRA or Linear).
  2. Use the Enable/Disable toggle to turn the integration on or off.

What happens when you disable:

  • All syncing pauses immediately. No changes will flow between TestApp.io and the connected tool.
  • Your configuration is fully preserved — field mappings, project/team selection, and all linked tasks remain intact.
  • No data is lost. When you re-enable, syncing resumes with your existing settings.

What happens when you re-enable:

  • Real-time syncing resumes immediately.
  • Any changes made while the integration was disabled will sync on the next update to the affected task.
Tip: Disabling is different from disconnecting. Disconnecting removes the OAuth authorization entirely and requires you to go through the setup process again. Disabling simply pauses sync while keeping everything configured.

2. Pull Tasks: On-Demand Import

The Pull Tasks feature lets you import existing issues from JIRA or Linear into TestApp.io on demand. This is useful when you want to bring over issues that were created before the integration was set up, or when new issues are added to a specific project or team that you want to track in TestApp.io.

How to pull tasks:

  1. Navigate to Team Settings → Integrations and select your integration.
  2. Click the “Pull Tasks” button.
  3. Browse the available issues from your connected JIRA project or Linear team.
  4. Select the issues you want to import.
  5. Click “Import Selected”.

Imported issues become TestApp.io tasks and are automatically linked to their source issues in JIRA or Linear. Once linked, they participate in real-time bidirectional sync — any future changes in either platform will be reflected in the other.

3. Migrate Tasks: Move Local Tasks to JIRA or Linear

If your team has been creating tasks locally in TestApp.io and now wants to move them into JIRA or Linear, the Migrate Tasks feature handles this seamlessly.

How to migrate tasks:

  1. Go to Team Settings → Integrations and select your integration.
  2. Click the “Migrate Tasks” button.
  3. Select the local TestApp.io tasks you want to migrate.
  4. Map your TestApp.io statuses to the corresponding statuses in the target tool:
    • For JIRA: e.g., “Open” → “To Do”, “In Progress” → “In Progress”, “Resolved” → “Done”
    • For Linear: e.g., “Open” → “Todo”, “In Progress” → “In Progress”, “Resolved” → “Done”
  5. Review the mapping summary to confirm everything looks correct.
  6. Click “Confirm Migration”.

What happens during migration:

  • A new issue is created in JIRA or Linear for each selected TestApp.io task.
  • The task’s status and priority are mapped according to your field mapping configuration.
  • The TestApp.io task is linked to the newly created issue.
  • From this point forward, the task participates in real-time 2-way sync.
Note: Migration does not delete the original TestApp.io task. It creates a linked counterpart in your external tool.

4. Sync History: Complete Audit Trail

Every sync event between TestApp.io and your connected JIRA or Linear instance is logged in the Sync History. This gives you full visibility into what is happening with your integration at all times.

How to access sync history:

  1. Go to Team Settings → Integrations and select your integration.
  2. Click on “Sync History”.

What you will see:

Each sync event entry includes:

  • Direction: Whether the sync was inbound (JIRA/Linear → TestApp.io) or outbound (TestApp.io → JIRA/Linear).
  • Status: Whether the sync succeeded or failed.
  • Timestamp: The exact date and time the sync event occurred.
  • Error details: For failed syncs, a description of what went wrong.

Retrying failed syncs:

If a sync event has failed, you can retry it with one click:

  1. Find the failed event in the sync history.
  2. Review the error details to understand the cause.
  3. Click the “Retry” button.
  4. TestApp.io will re-attempt the sync.

Common causes of failed syncs include temporary network issues, permission changes in the connected tool, or field mapping mismatches. Reviewing error details usually points you directly to the fix.

5. Field Mapping: Customize at Any Time

Field mapping controls how statuses and priorities translate between TestApp.io and your connected tool. You can update these mappings at any time without disconnecting or disrupting your integration.

How to update field mappings:

  1. Go to Team Settings → Integrations and select your integration.
  2. Open the Field Mapping section.
  3. Adjust the status and priority mappings as needed.
  4. Click “Save Mappings”.

Updated mappings take effect immediately for all future sync events. Previously synced tasks are not retroactively updated — they will pick up the new mappings on their next change.

When to update mappings:

  • When you add new statuses or priorities in JIRA or Linear.
  • When you restructure your workflow in TestApp.io.
  • When synced tasks are landing in incorrect statuses.

For detailed setup instructions specific to each integration, see:

Need help? Contact us and we’ll get back to you shortly.