Content Comparison

...

1. Go to “My organization” and resemble the project hierarchy to match your Server / DC instance (see My Organization for more information)

2. Check and update hierarchical links via ‘SAFe® Hierarchy’ panel in Jira Issue Detail View for individual issues as needed.

3. Adjust your project configuration of Screens, Screen Schemes, and Issue Type Screen Schemes to the Agile Hive default or adjust as needed (see Configure Jira Projects For Use With Agile Hive for additional information on recommended / minimum required configuration).

   1. The “Milestone Date” custom field gets migrated automatically, but is not included in the Screens from Agile Hive Cloud. You can add the migrated field to the desired screens (where the Cloud version of the field should already exist), rename the Cloud field to something else and make sure that your migrated field is called “Milestone Date” (without any “migrated”-suffix). Now the Milestones should also appear in Agile Hive views like the Roadmap or in Reports

4. To maintain your set dependencies from Server / DC, go to the Agile Hive Administration and select the Issue Link Type and Direction that you used before, and click “Save”.

   You can see

5. Create your PIs as you need for the future

   • If you already had PIs planned for the future on you Server/DC instance, you can recreate the PIs with the same dates in the Cloud Solution Train and/or ART and go to each corresponding team’s Agile Hive project settings to map the iterations created in Cloud with the sprints, that were migrated from Server/DC. You can delete the newly created sprints from Cloud again afterwards
     

...