This question is in reference to Atlassian Documentation: Add-ons and plugins
If I have a Cloud instance of JIRA, can I import a connect add-on that resides on a private network? I don't want to have to have an entry in the Marketplace for all the private instances of the target system.
The only possibility to install an add-on which is not listed on the Marketplace is to enable development mode - see the documentation on how to do this. Your add-on still needs to be publicly visible - if hosted on a private network, you'll need a tunneling solution like ngrok.io.
You should only need to create one private Atlassian Marketplace listing for each Atlassian Connect add-on and then you can install it in as many cloud instances (with private installs allowed) as you like.
Does that not work for you?
Thank you, Petar..The situation we have is that we have a product that our customers purchase which is only on-premise. But, many JIRA customers that want to use it are using JIRA Cloud. So, we want them to be able to display iframes inside of a JIRA ticket that are served from the on-premise product.
So, just to confirm what you're saying: in order for a Cloud customer to do that, they would have to enable development mode to point at something that is not itself listed in the Marketplace. Doing this would avoid the error message when trying to import the connect JSON file?
Yes, that's correct - when you enable development mode you can install any connect add-on, provided that JIRA can reach it over the internet.
I still say it would be better to use a private listing in the Atlassian marketplace. In the future "Enable development mode" might enable more than just the ability to install add-ons from other places. It could enable other development mode only features too.
If you are serving multiple OnDemand instances with your plugin (even if its not going to be public) you are probably better off with a private marketplace listing. There is quite a bit that gets taken care of behind the scenes. It is easy to add new instances and, as Robert points out, you avoid putting a production instance into development mode which could have hidden consequences.
It looks like you're new here. Sign in or register to get started.
![Photo of stratejos [stratejos.ai]](https://us.v-cdn.net/6038660/uploads/avatars/8c/e3/n8ce32345c35e9c20af91d2bdb7448738.png)