Last updated Jul 27, 2021

Rate this page:

Testing your migration in dev mode

Do not use dev mode in production as pre-flight checks are important for product consistency.

Dev mode allows developers to bypass certain checks and requirements and also update user interface interactions in order to speed up the development progress.

This page provides information on how to use dev mode for app migration to:

  • disable pre-flight checks or validation.
  • disable app assessment requirements.
  • update progress reporting to 1 minute intervals.

Preflight checks and validations

Pre-flight checks or validations ensure that your Jira/Confluence customers have the best experience possible while performing a migration. However, you do not need a cloud app installed in order to test a local change to your server app, and having to perform pre-flight checks or validations can get in the way of your testing. The App migration platform allows you to temporarily disable validations/pre-flight checks when you test changes to your server app.

App assessment requirements

App assessment requires you to select each server app you are testing in order for it to be included in app migration. Using dev mode removes this requirement, so the App migration platform will call every server app that has a listener implemented.

Progress reporting intervals

During normal app migration progress reporting in the Cloud Migration Assistant is updated every 10 minutes. Dev mode updates this to 1 minute intervals so updates from your cloud app can be tested more quickly.

Dev mode configuration

  1. Navigate to the Dark Feature page for your product:
    • Use the following link to enable the Confluence dark features: <Confluence_URL>/admin/darkfeatures.action
    • Use the following link to enable the Jira dark features: <Jira_URL>/secure/SiteDarkFeatures!default.jspa
  2. Add migration-assistant.app-migration.dev-mode in the text box.
  3. Click add or submit

Rate this page: