Can I have multiple versions of the same addon between different projects in JIRA?

[Lucas Tavares]

I currently work as a QA Coordinator in a multinational company. We are under the same tenant (organization), but each country has it own project.

Recently Im facing some problems with Zephyr (1.0) and I am thinking of updating it to the newer format (2.0), but since our organization has other projects using this same addon and they dont want to update it, Im worried we can cause problems within the other projects if we update it globally.

Is it possible to have one addon (ex.: Zephyr) with different versions between different projects of the same tenant organization? 

Or the only way to update and use pluggins is globally?

[Trudy Claspill · Accepted solution]

Hello @Lucas Tavares 

Welcome to the Atlassian community.

The structure for Atlassian Cloud is

Organization
|-- Site
    |-- Product (i.e. Jira, Confluence)
        |-- Jira Projects/Confluence Spaces

To clarify, are all of your teams using the same site (same base URL), and different project within the same Jira? Or do your teams use different sites (different base URLs) under the organization?

[Lucas Tavares]

Hi @Trudy Claspill we all use the same base URL, but different projects under this URL. Other community members answered me and sadly it seems we cannot update the addon only for our project, it would update globally =(

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

No, you can not do this.  Plugins are added to Jira, not to projects. 

The code in a plugin names it with a set of class names, and you can not use the same class names in a Java application for the same thing - the class for an app is unique and very rarely changes, so having two versions of the same app simply cannot work. 

[Lucas Tavares]

Hi @Nic Brough -Adaptavist- . Thankyou for your answer. We will try to work it out another way.

[Marc - Devoteam · Accepted solution]

HI @Lucas Tavares 

Welcome to the community.

Apps are related to a Jira instance not to individual projects in Jira.

[Lucas Tavares]

Hi @Marc - Devoteam . Thankyou for your answer. We will try to work it out another way.