Discover our story, vision, and impact.

By Role

DevOps Leaders

Accelerate delivery with clear insights

By Initiative

By Domain

The Coming Divide in Defense: Federation or Fallout Under DoDI 5000.97

Share: The defense industry is entering a pivotal phase of transformation. With the release of DoDI 5000.97, the U.S. Department of Defense (DoD) has made

Migrating to Jira Cloud

For modern enterprises, agility and efficiency are critical for success. Jira cloud migration is no longer optional; it is essential for boosting team productivity and ROI. However, cloud migration can significantly impact business operations, revenue, data security, and costs if not approached with care.
This demo showcases how to achieve a no downtime, zero disruption Jira cloud migration, eliminating interruptions while maximizing benefits. Additionally, it demonstrates how changes made during the Jira Cloud migration to the source effortlessly reflect in the target, ensuring complete visibility between IBM DOORS and Jira Cloud. Take a look!

Video Transcript

This video shows how to seamlessly migrate your projects to the Cloud with zero downtime, minimising disruption and maximising the benefits. In this video we will be migrating two different IBM Rational DOORS modules into a single Jira project. We are using DOORS as an example in this demo. You can migrate any tool to Jira Cloud.

Following the steps on the screen, we can see the first DOORS module created by the product manager, under which we have stories and bugs. These are defined by a custom attribute which is Issue type. In the bugs and stories, we can see the descriptions are formatted which include tables and Ole objects embedded as files or attachments. We can also see the text in the description formatted in bold and underlined. All the details visible here will migrate to the Jira project, retaining the formatting.

Similarly, in the second module in DOORS, we can see the bugs and stories created with the custom attribute and the descriptions in rich text formatting which include bullets and Ole objects amongst others. In both modules, the red and yellow arrows indicate the in and out links configured between the bugs and stories to retain complete traceability between the source and target systems during the migration.

Navigating to Jira, currently, we see the Jira project is empty. OpsHub Migration Manager (OMM) is working in the background checking for the modules to migrate from DOORS to Jira Cloud.

Let’s refresh the page to see if the migrated data is visible. Now the bugs and stories from those are reflecting here in Jira.

Let’s open a story to view the migrated data. We can see OMM has been able to bring over all the details from DOORS to Jira, including the table and other formatted details. Here is the Remote ID and Remote Link which will navigate you to the specific DOORS item, increasing traceability between the two systems. Similarly, other stories and bugs are created in DOORS with tables, Ole Objects, discussions, and associated links. Here, the story is associated with the bug have all migrated to JIRA Cloud. The Ole Object from DOORS is available in Jira as a file and as an attachment. The linkage created between the story and the bug is also preserved between the source and target systems.

The discussion in DOORS has synchronised to Jira as comments. Let’s quickly look at the details of the associated bug which too have migrated from DOORS. The developer now updates a story in Jira. The changes made to the title and the newly added comment will automatically migrate to DOORS.

OMM’s Reverse Synchronization enables users to sync data back from their target to source during the migration. We can also make changes to our source system while the migration is in progress. All the changes made in the interim will reflect in both systems automatically. Let’s take a look at the DOORS object which was recently updated in JIRA. Since the summary in Jira is synced to Short Text in DOORS, the updated information has bidirectionally synced and is available under Short Text.

Here, the bidirectional synchronization allows changes made in one system to automatically reflect in the other. Under discussions, we can see the comment added in Jira has synchronised as well.

Let’s make a quick update to the description in DOORS to see if it migrates back to Jira. One final time In Jira, opening the story, which was updated in DOORS, we can see the updated description as bidirectionally synchronised and is visible here.

That completes the demo. Thank you for watching.

OpsHub Integration Manager

OpsHub Migration Manager

OpsHub Archive Manager

OpsHub Migrator for Microsoft Azure DevOps

OpsHub Data Bridge

DevOps Leaders

DevOps Leaders

Digital Engineering or Transformation Leaders

Enterprise Architects

Digital Thread for DoD

Cloud Migration & Digital Transformation

Digital Thread and Compliance

Smart Engineering for AI, Co-Pilot Initiatives

Software Development & Agile Engineering

IT Service Management & Customer Support

Product Lifecycle Management & Systems Engineering

Requirements Management for Regulated Industries

Blogs

Case Studies

White Papers

Videos

EBooks

Press Releases

Webinars

News Letters

The Coming Divide in Defense: Federation or Fallout Under DoDI 5000.97

Migrating to Jira Cloud

Experience scalable, non-disruptive migration with OMM

Video Transcript

Experience scalable, non-disruptive migration with OMM