Vendor Integration FAQ

Who can use this information?

  1. App vendors who want to allow their customers to move app configuration and data from one Jira instance to another.

  2. Jira customers who develop apps for internal usage and want to move the app configuration and data between Jira instances.

  3. Developers who want to integrate apps with Configuration Manager for Jira (CMJ) for app data and configuration migration purposes.

Find answers to frequently asked integration questions by vendors

Before you start your Jira app integration with CMJ through the Apps SPI platform, you may want to look at our answers to the most common questions.

  1. How long will the integration with Service Provider Interface (SPI) take?
    The timeline to complete your integration with SPI will vary based on the following factors:

    1. Your app’s availability across hosting types (Jira Server, Data Center, and Cloud). If your app exists both on-premises (Server and Data Center) and within Cloud, you will need to complete two different SPI implementations.

    2. The complexity of the app’s data being migrated. It determines the variety of integration endpoints for your app. For each Jira element your app modifies (i.e., custom fields, dashboards, workflows), you need to integrate using the corresponding SPI endpoints.

    3. Size of the integration team. If you have more developers to work on the integration, the work will go faster

  2. Why should I integrate with CMJ using SPI?

    1. See Why Integrate your Apps with CMJ to understand the importance and key benefits of this integration.

  3. Who should I contact for help during my integration?

    1. If you encounter any issues or questions during your integration, don’t hesitate to contact Appfire’s Support team.

  4. What steps should I follow to complete the integration?

    1. Find the full list of integration steps here. Note that we recommend a few phases of integration, including planning with key stakeholders, estimating the level of effort, scheduling tasks in an upcoming sprint, and notifying Appfire before and after so we can provide support as needed and help promote the integration once complete.