Jira Service Management CLOUD + Jira Data Center

[Humberto Gomes]

Hi Community

Currently,

our organization is utilizing Jira Service Desk and Jira Core within the same Data Center instance. As we observe ongoing advancements and developments in Cloud Apps, it has come to our attention that certain features essential to our operations are exclusively available for the Cloud version.

We are exploring the possibility of migrating only the Jira Service Desk component to the Cloud while retaining the Jira Core in the Data Center version. In this regard, I would appreciate your assistance in addressing some key considerations and potential challenges associated with this transition.

Here are a few specific concerns:

1. Connector Requirement: Will an additional connector be necessary to facilitate communication between the Jira Service Desk in the Cloud and Jira Core in the Data Center?

2. Automation Integration: Can we seamlessly run and invoke processes in both instances, such as creating tickets and copying information, particularly concerning Automation functionalities?

3. Single Sign-On (SSO) with Active Directory: How can we ensure a smooth transition with respect to SSO, specifically integrated with Active Directory?

4. Behaviors Functionality in Cloud: Are we able to execute and maintain behaviors in the Cloud, particularly those aimed at controlling field list options?

Your expertise and guidance on these matters would be invaluable as we evaluate the feasibility and implications of this potential migration. Any additional insights or recommendations you can provide will be greatly appreciated.

Thank you for your time and assistance in helping us make informed decisions.

Best regards,

[Earl McCutcheon · Accepted solution]

Helklo @Humberto Gomes ,

Thanks for reaching out to the Community, as a starting and reference point the answers to your questions are touched on in the following documentation:

• Integrate Jira Cloud with Jira Server
  • Particularly the "In Summary" section at the top that notes what features are available and what is not possible
• Single Sign-on Integration with Atlassian products
• Manage users between cloud and Data Center products

So breaking these down into a brief overview and connecting the info to your specific questions, SSO syncing with Atlassian Access should get you on the right track covered in detail above but with data syncing that gets a bit complex and when linking a Could and Data Center instance (or even a cloud to cloud or Data center to data center) the issue Link data can be shared and activity stream data can be shared but the Syncing and combination of data on the independent sites cannot be shared.

So as an example you can link issues from site 1 to site 2 and the link data will be displayed on each instance with recursive links naoting the link status (for example blocks/is blocked by) with the issue details like status and summary etc.. but you cannot synchronize or share data of have actions transferred from one instance to another such as make a comment on an issue in instance 1 and have that comment transferred to instance 2. 

Additional Examples on the concept are the following feature requests for similar behavior noting all these are automation-related but overall any action that applies to synchronizing data between sites is not natively possible without additional add-ons:

• https://jira.atlassian.com/browse/JSDCLOUD-3746
• https://jira.atlassian.com/browse/JRACLOUD-62177
• https://jira.atlassian.com/browse/ENT-348
• https://jira.atlassian.com/browse/ENT-335
• https://jira.atlassian.com/browse/JSDSERVER-3746

So Options to sync data is going to fall onto third-party apps or design a custom integration.

A list of issue synchronization tools can be found in the Marketplace here:

• https://marketplace.atlassian.com/search?query=syncronization

Alternatively, While I don't have any examples or references to other users with working examples but if you want to look into developing and customizing something using an automation rule I would suggest starting in the dev documentation of automation-triggered Webhooks to pull data from external resources and follow up actions that can use that data that might be something to leveraged to find a solution, detailed more here:

• https://developer.atlassian.com/cloud/jira/service-desk/automation-webhooks

Hope this helps get you on the right track.

Regards,
Earl

[Humberto Gomes]

Many thanks for your time and clear answer.