JIRA Service Desk CLOUD with JIRA SERVER

[Markus Raab]

Hi there, 

we run JIRA internally on-premise and want to introduce JIRA Service Desk + Confluence as a knowledge base to increase self-service for our customers. 

It is not clear by now if we want JIRA Service Desk Cloud or Server. However, a key question is if we could link JIRA Service Desk Cloud tickets to our internal JIRA Server? If this is not possible or very error-prone then it would be clear that we focus on JIRA Service Desk Server and run it on-premise as well.

Thanks for your advice!

best

Markus

[Gonchik Tsymzhitov]

Hi! 

Start with: 

https://confluence.atlassian.com/cloudkb/pros-and-cons-of-cloud-vs-server-691011844.html?_ga=2.90895896.387552184.1507535646-393805446.1489735886

https://community.atlassian.com/t5/Jira-questions/JIRA-SD-cloud-vs-server/qaq-p/355326

But they do leave out some stuff:

• If you have a many attachements more than > 30GB nearest feature 

plust quote from ither threads:

• If you want >2,000 users (not service desk customers, but actual JIRA / Confluence users), you need Server. 
• If you have a huge installation, you'll need Server on Data Centre
• If you want to store personal data on it, you need Server (Cloud is hosted in the US, making it illegal to store quite a lot of types of personal data on it for EU users)
• There is mention of the limited list of add-ons you can use on Cloud, but frankly, that lack of flexibility is the main driver we see for people migrating off Cloud and on to Server (whether they self-host the server or get a third-party to do it).  People need Script Runner, the integrated reporting add-ons, the PPM tools, etc

I hope it will help you.

Cheers, 

Gonchik Tsymzhitov

[Markus Raab]

Thanks for the link to the comparison and your further notes on cloud vs. server.

Do you by chance know if one JIRA Service Desk CLOUD instance works with JIRA Software SERVER instance? (2 instances in total).

[Gonchik Tsymzhitov]

Hi! 

Why not? 

In fact, you need understand a use case. 

May be it is enough to create app links and linking between issue for different project on-demand and cloud.

Or your need a copy issue from cloud to server, if you have use case. Then Development based in Server version, hence user story can be copied from cloud JSD. 

Please, read this thread 

https://community.atlassian.com/t5/Jira-Service-Desk-questions/How-to-create-a-JIRA-issue-from-a-Service-Desk-Ticket-and-have/qaq-p/122147

I hope it is helped for you

Cheers,

Gonchik Tsymzhitov

[Gonchik Tsymzhitov]

Hi! 

Start with: 

https://confluence.atlassian.com/cloudkb/pros-and-cons-of-cloud-vs-server-691011844.html

https://community.atlassian.com/t5/Jira-questions/JIRA-SD-cloud-vs-server/qaq-p/355326

But they do leave out some stuff:

• If you have a many attachements more than > 30GB nearest feature 

plust quote from ither threads:

• If you want >2,000 users (not service desk customers, but actual JIRA / Confluence users), you need Server. 
• If you have a huge installation, you'll need Server on Data Centre
• If you want to store personal data on it, you need Server (Cloud is hosted in the US, making it illegal to store quite a lot of types of personal data on it for EU users)
• There is mention of the limited list of add-ons you can use on Cloud, but frankly, that lack of flexibility is the main driver we see for people migrating off Cloud and on to Server (whether they self-host the server or get a third-party to do it).  People need Script Runner, the integrated reporting add-ons, the PPM tools, etc

I hope it will help you.

Cheers, 

Gonchik Tsymzhitov