The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
How to link Jira Cloud Issues with Jira Data Center Issues Using Application Links
How to link Jira Cloud Issues with Jira Data Center Issues Using Application Links
October 16, 2024 edited
In a recent client engagement, two departments needed to collaborate while using separate Jira instances—one in the cloud and one on Data Center. Due to security requirements mandating that certain team activities remain on-premise, we chose to implement application links instead of consolidating them into a single platform. In this article, I’ll highlight the benefits of using application links and provide a video tutorial on how to set them up effectively.
Benefits of Application Links:
Using application links to connect Jira Cloud and Jira Data Center is essential for several reasons:
Cross-System Integration: Application links enable seamless integration between the two systems, allowing teams to work collaboratively across different environments.
Issue Synchronization: Linking tickets helps maintain visibility and traceability between related issues in both systems. This ensures that updates in one Jira instance reflect in the other, improving communication.
Single Sign-On (SSO): Application links can facilitate SSO, allowing users to navigate between Jira Cloud and Jira Data Center without needing to log in multiple times.
Shared Functionality: Certain features, like comments, attachments, and issue history, can be accessed across both systems, enhancing user experience and productivity.
Improved Reporting: Linking the two systems allows for more comprehensive reporting and metrics, providing a unified view of project progress.
Overall, application links are crucial for maintaining efficiency and collaboration between teams using different Jira deployments.
2 comments
Comments for this post are closed
Community moderators have prevented the ability to post new comments.
2 comments