Are you a developer or app vendor wanting to create or market an extension for Project Configurator — the market-leading app for Jira migrations and configuration management? Our Integration Toolkit enables developers to easily build Project Configurator extensions for workflows, dashboard gadgets, and custom entities, allowing your customers that use Project Configurator for their migration needs to move your app configurations and data between their Jira instances.

Integration Toolkit Developer Guide

Our developer guide to creating an extension with javadoc contains everything you need to get started, including detailed examples and links to the javadoc files.

Please see the Developer Guide PDF to learn more.

Developer Guide PDF

All the extensions are Java code to be deployed in Jira as a P2 Jira plugin(or app).

Benefits of creating an extension

For the app vendor

Your current customers, who are using Project Configurator in their Jira instance, will save time and reduce errors and manual work by being able to move your app configurations and data between their Jira instances. If your customers are moving from one Jira instance to another, e.g. moving from Server to Data Center, to reduce the migration effort, they are likely to review which of their installed apps they want to keep or remove. If your app’s data is easily portable, it increases the chance of them retaining and using your app in the new instance. Co-marketing opportunity - Adaptavist is keen to work with third-party app vendors to discuss any potential co-marketing opportunities that we collaborate on to promote the new extensions to each user base.

For the end user

Jira Administrators are the end users of PC. They want a convenient method of moving configurations and data between different Jira instances that does not require endless hours of error-prone manual work. Because apps are a large and integral part of most Jira installations, it would be extremely useful if Jira Administrators could enjoy the same benefits that PC offers for built-in objects when they are moving configurations or data that belong to the main apps they use in Jira. For example:

  • They might configure an app in a staging environment and then automatically move those changes to production.

  • They could have a group of projects which heavily depend on an app in a departmental Jira and then consolidate those projects transparently into a corporate instance of Jira.

  • They could find out which projects, workflows, or custom fields are using specific configuration items defined by the app.

All this can be achieved if a PC extension is created to support the app. These features are especially appreciated by large organizations with corporate Jira instances (often Data Center). These organizations are very careful in how they manage their IT systems, so they are usually reluctant to experiment with configuration changes directly in production. They would rather test them first in a testing/staging instance. These customers are very often involved in mergers, acquisitions, or simply changes in corporate structure, which trigger consolidations, splits, or redistribution of projects among Jira instances. All these operations ultimately mean moving projects between different instances.

Making your app easy to migrate, both its configuration and data, is certain to make it more attractive to the most valuable customers in the Atlassian ecosystem.