Configuration Manager SPI: The building blocks of an integrated and cohesive Atlassian ecosystem

 

When the Atlassian Marketplace was launched in 2012, it was a turning point for the Atlassian ecosystem – one that fostered a true spirit of collaboration between the needs of the end-users and the third-party application developers looking to enhance the functionality of Atlassian’s diverse product portfolio.

Botron Software’s Configuration Manager for Jira was the first significant innovation leap in the space of Jira administration. The data capturing capabilities of the tool enabled admins to quickly capture and transfer a diverse set of Jira configurations and data, including new custom field types and a list of the more popular third-party apps.

As Jira’s powerful extension model led to the emergence of hundreds of apps designed to augment the functionality of the platform, the need to quickly transfer third-party app data and configuration has become a pressing issue for marketplace vendors, especially in the light of the fact that a rising number of enterprises are migrating or consolidating their servers.

In light of these challenges, Botron Software launched a solution that will help foster a more integrated and cohesive ecosystem amongst the vast network of marketplace vendors – Configuration Manager Service Provider Interface (SPI).

Introducing Service Provider Interface (SPI) for Configuration Manager for Jira

Service Provider Interface (SPI) is designed to enable the entire Atlassian ecosystem of vendors to enhance their apps for quick and easy portability, without compromising their configuration and data integrity. SPI will ultimately bridge the gap between a platform and apps by offering a streamlined process that will enable the Atlassian customer base to be compliant with the enterprise best practices of Dev-Staging-Production and migration processes for Jira Software and Jira Service Desk.

The configuration of apps may be arbitrary but may also contain references to other configuration elements in Jira (priorities, resolutions, custom fields, filters, etc.). As part of the robust process, CMJ’s SPI technology provides the means for collecting app references on the source instance and properly resolving them on the target instance.

The collect-and-resolve process of moving configuration and data involves the capture of all these references, their analysis for dependencies and usage from the source server. For a successful deployment on the target server, a similarly complex process takes place and resolves these references with new or matching objects.

The core of the SPI technology handles the entirety of this complex logic generically, thus ensuring that the app-specific information and implementation is rather minimal. SPI provides the means for collecting such references on the source instance and correctly resolving them on the target instance.

Vendors are now able to quickly adapt their apps for seamless portability by adding the SPI as maven dependency and implement one of the SPI interfaces, depending on what type of configuration you want to support.

Vendors of Jira apps: Unite! Botron Software partners with ProForma

Following Atlassian’s latest conference in Las Vegas, Botron Software’s team approached numerous marketplace vendors with a partnership offer to enhance their apps for seamless portability.

The first success story from this partnership initiative is already evident – Botron Software’s partnered with ProForma in implementing SPI for their powerful application.

ProForma is a powerful application for Jira Software, Jira Core, and Jira Service Desk, designed to enable teams to empowers teams to control the way they collect information in Jira issues. ProForma allows organizations to build and design forms based on their unique business needs, without the necessity of creating custom fields.

ProForma is now SPI-compatible, and any customer engaged in migrations will be able to move the data and configuration of this application as easily, quickly and securely as the rest of the Jira project components.

In the upcoming weeks, Botron Software and ProForma will be launching a series of blog posts and use cases, where we will go into more technical detail about the process of implementing SPI for vendor apps, and the benefits of this compatibility.

Let’s build a better Atlassian ecosystem together!

Be sure to check out ProForma’s blog post for more information about our apps integration.