How to developed an addon both for jira cloud and server?

[Michael Grosse]

How do I develop an addon that is available both for sever and for cloud instances? Like Zephyr?

I cannot use Atlassian Connect, because it works only for the cloud and not for JIRA server.

I cannot use a common JIRA server addon, because it cannot be installed in the cloud.

So how am I supposed to develop an addon both for the JIRA cloud and JIRA server? Is there somewhere a documentation page that explains this?

[Nic Brough -Adaptavist- · Accepted solution]

You can't.  When you see offerings for Cloud and Server, there's one of three things happening:

1. It's not an add-on that is installed in JIRA, but something that works from the outside.
2. There are two separate add-ons.  A "type-2" add-on (for Server), and a Connect add-on.
3. It's a type-2 add-on that Atlassian have chosen to offer to Cloud customers.

Connect and type-2 add-ons are fundamentally different.  Although you can share some of the core code for them in some ways, the framework you have to implement them in is totally different.

[Travis Smith]

Most of the documentation refers to what you call "type-2" as "Plugins 2" (as in Plugins System Version 2). Searching for type-2 will likely just lead you to the wrong content or diabetes content elsewhere.

[Nic Brough -Adaptavist-]

Yes, sorry, I've spent too long hanging around with developers recently.

[Robert Massaioli _Atlassian_]

It's also important to note that, with point 3, we have not accepted any new vendor written Plugins 2 addons into our Cloud offering for a long time and that is not likely to change any time soon. Also, Atlassian Connect will not be getting Server support: https://developer.atlassian.com/static/connect/docs/latest/resources/connect-for-server.html

[Ralph Whitbeck]

The frameworks for developing discrete binary add-ons for our Server software, and developing multi-tenant cloud-based add-ons for our SaaS products are fundamentally different. This means there is no path to developing only one add-on for both, and is why you won't find documentation on our site. 

That said, at AtlasCamp last year @Patrick Streule gave a talk called "Connect everywhere - Cloud and Server" where he talks about techniques to architecting your add-on so that most of your code can be used for both Connect and P2. 

You can see that talk here: 

https://www.youtube.com/watch?v=ybhmYq9QOxY&index=23&list=PLaD4FvsFdarQsi3IUT9btuRPXukhkmC43

Additionally, we have a guest blog post from a vendor we're finalizing that will be published on http://developer.atlassian.com/blog and that talks about this topic as well. Keep an eye on the blog for that.

[Adam Wride]

Is this the article? https://developer.atlassian.com/blog/2016/02/universal-addons-for-jira-server-cloud/

[Volodymyr Krupach]

Please check Cloud and Server Atlassian Common Code. It goes with sources and demonstrates approach for creating common Atlassian Cloud and Server plugins. The beauty of the apporach is that booth JavaScript and Java sources are shared.