First-Time Setup

Access the App form Apps → Asset Objects migration for JSM

Open

🔌 Managing Connections

Connections store authentication details for Jira Service Management instances you want to migrate assets between.

Adding a Connection

1. Navigate to Connections tab

2. Click "Add Connection" button

3. Fill in the form:

   • Configuration Name: Friendly name (e.g., "Production JSM")

   • Use current local site: Auto-fills your current Jira URL

   • Jira site URL: Base URL (e.g., https://your-site.atlassian.net)

   • Account Email: Your Atlassian account email

   • API Token: Generate from Atlassian Account Settings, to easily create, select the token API with default, or you can specify scope with these:
     

4. Open

   

   Click "Test Connection" to verify credentials

5. Click "Save" to store the connection

Testing a Connection

• Click "Test Connection" after filling credentials

• Success message shows connected user details

• Failed tests show specific error messages

Editing/Deleting Connections

• Use the action buttons (Edit/Delete) next to each connection

• Deleting a connection won't affect existing migrations using it

🔄 Migration Types

The app offers two migration modes to suit different needs:

🚀 Quick Action (Full Migration)

• Purpose: One-time, immediate asset transfer

• Best for: Initial setup, one-off migrations, testing

• Process: Runs immediately when started

• Monitoring: Real-time logs available during execution

🔄 Incremental Sync

• Purpose: Continuous synchronization

• Best for: Keeping dev/prod environments in sync, ongoing replication

• Schedule Options: Hourly, Daily, Weekly

• Features:

  • Automatic background execution

  • Manual "Run Now" option

  • Configurable sync frequency

  • Preserves mapping configuration

Open

🎯 Creating a Migration

Step 1: Select Migration Type

From the main dashboard, click "New Migration" and choose your migration type:

• Quick Action: For immediate, one-time migration ( Recommended)

• Incremental Sync: For ongoing synchronization

Step 2: Select Source and Target Sites

Choose your JSM instances:

• Source Site: Where assets will be copied FROM

• Target Site: Where assets will be copied TO

💡 Tip: Both sites must have Assets (formerly Insight) enabled.

Step 3: Define Asset Scope

Select Schemas

Choose one or more object schemas to migrate:

Target Schema Mapping

For each selected schema, define:

• Target Schema Name: Name in destination instance

• Target Schema Key: Unique identifier (uppercase letters/numbers)

⚠️ Validation: The app warns if names/keys already exist in target

Open

AQL Filtering

Use Asset Query Language to filter specific objects:

• Examples:

  • "Status" = "Active"

  • "Name" like "Server-*"

  • "Department" = "IT" AND "Location" = "NYC"

• Click "Test Query" to see matching object count

Sync Frequency (Incremental Only)

Choose how often automatic sync runs:

• Hourly

• Daily (default)

• Weekly

• Monthly

Step 4: Review & Start

Review your configuration:

• Migration type

• Source/target sites

• Selected schemas with mappings

• AQL filter (if any)

Click "Start Asset Migration" to begin.

📈 Monitoring & Logs

Migration Dashboard

The main dashboard shows all migrations with:

• ID: Unique identifier

• Schema: Migrated schema name

• Type: Quick Action or Incremental Sync

• Status: Color-coded (green=completed, red=failed, blue=in-progress)

• Progress: Visual progress bar with counts

• Started: Timestamp

• Actions: View logs, Run (sync), Edit, Delete

Open

Viewing Logs

Click "View Logs..." on any migration to see:

• Real-time operation updates

• Timestamped entries

• Success/failure indicators

• Object counts and details

• Error messages if any

Managing Migrations

For Quick Actions

• View logs only

• Delete completed/failed migrations

For Incremental Syncs

• Run: Manually trigger sync anytime

• Edit: Modify configuration

• Delete: Remove sync plan

Automatic Cleanup

• Completed/failed migrations older than 7 days auto-delete

• Maximum 50 migration records kept

• Configs capped at 100 entries

🎉 Getting the Most Out of Your Migrations

Use Case Examples

IT Asset Inventory

Migrate all active laptops to central inventory

Department Sync

Keep specific departments in sync across instances

Compliance Tracking

Identify outdated assets needing attention