Integrations, Apps, and Data Migration
What to know
Integrations include REST APIs, webhooks, and marketplace apps. Apps can add fields, workflows, and automation; they are managed by administrators and may require licensing. The REST API supports authentication via API tokens or OAuth; webhooks push events to external systems. Data migration covers importing from CSV or another tracker, mapping fields, preserving users, and validating after import. Understand the difference between a project import and a full instance migration.
Traps
Questions often test that API tokens are used with basic auth for scripts, while OAuth is for apps. Webhooks fire on events but do not retry indefinitely. App changes can affect shared schemes, so test in a staging project. During migration, unmapped fields lose data; user accounts must exist or be created. Also, CSV import cannot preserve workflow history.
Rule of thumb
Plan integrations around the API and webhooks, test apps in a non-production project, and always map fields and users before a migration. Validate counts and spot-check issues after import.
Worked example
Migrating from another tracker via CSV: export issues, map columns to Jira fields, ensure users exist, import into a staging project, then verify statuses, attachments, and comments. Only after validation import into the target project.