Download as PDF, PPTX
Uploaded byAtlassian
Are you Ready to Rumble? Let's Migrate Some Jira Data
The document outlines the process and considerations for migrating Jira data, detailing the importance of preparation, discovery, and the use of various tools. It emphasizes the significance of defining goals, validating requirements, and involving customers throughout the migration phases. Additionally, the document shares insights on handling large migrations, metadata modifications, and offers practical tips for successful execution.
More Related Content
Similar to Are you Ready to Rumble? Let's Migrate Some Jira Data
Are you Ready to Rumble? Let's Migrate Some Jira Data
- 1. MARK LANG |JIRA ADMIN | CISCO | @MARKLANG78 Are You Ready to Rumble? Let’s Migrate Some Jira Data
- 2. Legal Disclaimer THE INFORMATIONHEREIN IS PROVIDED ON AN “AS IS” BASIS, WITHOUT ANY WARRANTIES OR REPRESENTATIONS, EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION, WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.”
- 3. Agenda Background What’s Your Goal? AskFirst Process Tools as a Guide Other Tips & Tricks Takeaways & Resources
- 4. Agenda Background What’s Your Goal? AskFirst Process Tools as a Guide Other Tips & Tricks Takeaways & Resources
- 5. There are neither beginningsor endings…But it was a beginning ROBERT JORDAN
- 6.
- 7. 1 Instance in ProductionFebruary 2014
- 8. 43 Separate Jira &Confluence Instances
- 9. Paid Apps acrossour instances 111+ Marketplace; Source (https://marketplace.atlassian.com/)
- 10.
- 11.
- 12. What I toldyou was true, from a certain point of view STAR WARS VI
- 13. Agenda Background What’s Your Goal? AskFirst Process Tools as a Guide Other Tips & Tricks Takeaways & Resources
- 14. Get ALL theData
- 15. Before • No clearprocess forward • Not sure what data migrates • Don’t know what you don’t know • Frustrated customers enews; Source (http://bit.ly/cliff_image)
- 16. Before • No clearprocess forward • Not sure what data migrates • Don’t know what you don’t know • Frustrated customers After • Defined process • Questionnaire facilitates dialog • Better idea on timeline • Prepared to deal with bumps and bruises enews; Source (http://bit.ly/cliff_image) SWNS; Source (http://bit.ly/basecliff_image)
- 17. Migrate as much aspossible
- 18. Full System Application Export Merge Projectsor Spaces Native DB and Filesystem (home) Other Applications What are you choices?
- 19. Agenda Background What’s Your Goal? AskFirst Process Tools as a Guide Other Tips & Tricks Takeaways & Resources
- 20. Discovery Most Important Take yourtime Document Well Validate Requirements
- 22. Set Expectations • Goalis to avoid surprises later • Call out limitations • Set the tone • Build a connection
- 23. Start High Level •Typical “W” Questions • Who, Where, When, What • Get an idea of the big picture • What are their expectations?
- 24. Drill Down • Typeof Migration • Where is the data coming from? • Jira, Bugzilla, Rally • Support Choices
- 25. Details • Where isthe data coming from? • Actual URL, Versions • How much data? • User Accounts and Access • Apps
- 26. Integrations • Deep Integrationsyou directly support • Everything Else - Indirectly Connected • Confluence Apps
- 27. Agenda Background What’s Your Goal? AskFirst Process Tools as a Guide Other Tips & Tricks Takeaways & Resources
- 28.
- 29. Plans are worthless,but planning is everything DWIGHT EISENHOWER
- 30.
- 31.
- 32.
- 33. Discovery Sandboxing Validate Production Closeout • CopyfromProduction • DocumentWell •TimeIt YoPriceVille; Source (http://bit.ly/sandbox_phase)
- 34. Discovery Sandboxing Validate Production Closeout • CopyfromProduction • DocumentWell •TimeIt YoPriceVille; Source (http://bit.ly/sandbox_phase)
- 35.
- 36. Discovery Sandboxing Validate Production Closeout • Preparation • OutsideBusinessHours •HardCutover WorldArtsMe; Source (http://bit.ly/prod_deploy)
- 37. Discovery Sandboxing Validate Production Closeout • High-Touch • DataValidation •ReviewTimeStamps • TwoWeeksorLess
- 38. Agenda Background What’s Your Goal? AskFirst Process Tools as a Guide Other Tips & Tricks Takeaways & Resources
- 39. If the onlytool you have is a hammer, you tend to see every problem as a nail ABRAHAM MASLOW
- 40.
- 41. Migration Details Metadata User Data • Users •Custom Fields • Workflows • Schemes • Field Configurations
- 42. Metadata User Data • Projects •Issues • Assignees • Reporters • Dashboards • Filters • Agile Boards • History Migration Details
- 43. WHAT WE MODIFY Metadata Mustbe first data migrated App We use Botron Configuration Manager
- 44. Why we modify Avoid AffectingDefault Configuration Remove Unnecessary Metadata Contain Changes to Specific Projects
- 45. Why we modify Avoid AffectingDefault Configuration Remove Unnecessary Metadata Contain Changes to Specific Projects
- 46. What we lookfor Switch from Global to Specific Field Context Reduce Scope by Removing Parameters Rename Workflows Remove Excess Metadata
- 47. What we lookfor Rename Workflows Remove Excess Metadata
- 48.
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55. JiraData • UserandGroupMapping • TakingapartJiraExportfiletogetatEntities.xml •Retainhistoricalactions
- 56. • User’sactions • Watches •History • UserPermissions Whywemodify Retain:
- 57.
- 58. Let’s work withan example of John Doe Where’sWaldo? Source Target Name John Doe John Doe userName JohnDoe4 jdoe4 groupName Devgroup1 dev_group1
- 59.
- 60. SED Pass 1 sed's|(.*)#(.*)|s/"1"/"2"/gI|' < user_group_mapping_mini.txt | sed -f- entities.xml > output.xml Attributes Elements User Mentions Markdown
- 61. SED Pass 2 sed's|(.*)#(.*)|s/>1/>2/gI|' < user_group_mapping_mini.txt | sed -f- output.xml > output2.xml Attributes Elements User Mentions Markdown
- 62. SED Pass 3 sed's|(.*)#(.*)|s/~1/~2/gI|' < user_group_mapping_mini.txt | sed -f- output2.xml > output3.xml Attributes Elements User Mentions Markdown
- 63. SED Pass 4 sed's|(.*)#(.*)|s/=1/=2/gI|' < user_group_mapping_mini.txt | sed -f- output3.xml > output4.xml Attributes Elements User Mentions Markdown
- 64. SED Pass 4 sed's|(.*)#(.*)|s/=1/=2/gI|' < user_group_mapping_mini.txt | sed -f- output3.xml > output4.xml Attributes Elements User Mentions Markdown
- 65.
- 66. Pick a Strong Team RightSkills Community Atlassian Support Solution Partners
- 67. Pick a Strong Team RightSkills Community Atlassian Support Solution Partners
- 68. Pick a Strong Team RightSkills Community Atlassian Support Solution Partners
- 69. Pick a Strong Team RightSkills Community Atlassian Support Solution Partners
- 70. Agenda Background What’s Your Goal? AskFirst Process Tools as a Guide Other Tips & Tricks Takeaways & Resources
- 71. • Versions! • ChangingProjectKey •ManuallyWiringUpAttachments • AddingIssuestoSprints • MigratingRallyData Tips&Tricks
- 72. Agenda Background What’s Your Goal? AskFirst Process Tools as a Guide Other Tips & Tricks Takeaways & Resources
- 73.
- 74.
- 75. Usealifeline • AtlassianCommunity • SolutionPartners •AtlassianSupport
- 76. Usealifeline • AtlassianCommunity • SolutionPartners •AtlassianSupport
- 77. MIGRATION RESOURCES • QuestionnaireExample •SEDExamples • DocumentedTips&Tricks http://go.atlassian.com/summit19-migration
- 78.
- 79. MARK LANG |JIRA ADMIN | CISCO | @MARKLANG78 Thank you!
- 80.
- 81.
- 82. Questions 1.Whydoyouhavetodothis -withsomanymigrationsandsomanyinstances? 1. Ciscoismadeupofalotofseparatebusinessunits.Theseareeffectively separatebusinessesandoftenhavetheirownbudgetsandrequirements. 2.Youhavetodoalotofupgradesasaresultofyourscale.Haveyouconsidered consolidatingmorethanyoudonowandforcingsomeoftheteamstobeonshared instanceswithmoreappsthantheymightnormallywant? 1.Wehaveabsolutelyconsideredit.Weweighoutthecostsvstheamountof resourcesneededtosupportandtheflexibilityorlackofflexibility. Oftenthe licensecostsandtheneedforflexibilitydriveustothistypeofdesign. 3.Howdoyouchargebackfortheseservices? 1.EachDepartment(BusinessUnit)hasadepartmentidthatwecaninternallybillas acrosscharge
- 83. Questions 1.Howdoyouhandleupgrades? 1.Itisa4monthcycleforus. Thefirstmonthisreviewofthelatestenterpriserelease inalab/stageenvironment. Thefirst/secondmonthalsogetsthefirstsetof instancesinonegeographiclocationupgradedinasandbox/DRenvironmentand testedwiththeirdataandapps.Thatgroupisupgradedtoproductionoverthe weekendthatmonthwhileweareupgradingthesecondsetofinstancesfroma secondgeographiclocationinSandbox/DR. Thethirdmonthseestheupgradeof thoseinstancesalongwiththefinalgroupSandbox/DRandthefourthmonthisthe productionupgradeofthelastlocation. 2.Howdoyoumanageglobalteams? 1.Wehave3tiersofsupportandourtier1isinIndia,whiletier2and3areintheUS. WearelookingatexpandingthistohaveapresenceinEurposetoo
- 84. Questions 1.IsallofCiscorunbyyou? 1.Imanagethelicensesonabout60%ofCisco. Thatisstillgrowingbutnotquiteas fastapace. Alotofgroupswanttokeepthatcompletecontrol. 2.Arenttherepartnersthatcouldbehelpfultoyouinsomeofthetoughmigrations? 1.Absolutely,butnooneunderstandstheinsideofCiscolikeaCiscoemployee.The partnersareverygoodatAtlassian,butwehavebecomeverygoodatAtlassian withhowCiscoworks. Pluswehavemoreexperiencewithmigrationsthanmany partnersatthispoint. 3.Whataresomegoodtipsforlearningtheskillsyousaidyoumightneedtobegood atmigrations? 1.Practiceinadevenvironment. Startwithsmallchangesandseewhattheeffects areinsandbox. Don’tbeafraidoftheentities.xmlandConfigurationmanager.xml
- 85.
- 86. Details Part 2 •Apps • Customizations • Special Configurations
- 87. Integrations • Deep Integrationsyou directly support • Everything Else - Indirectly Connected • Confluence Apps
- 88. Full System Application Export Merge Projectsor Spaces Native DB and Filesystem (home) Other Applications What are you Choices
- 89. RinseandRepeat 1.Download project snapshotfile with Configuration Manager 2.Create a directory and Unzip 3.Utilize a tool like UltraEdit or Notepad ++ for *.xml 4.Modify the XML and save in UTF-8 5.Zip 6.Deploy
- 90. • FixDescriptions,Icons,andColors • System/GlobalFIelds(likeRankandPriority) •Rename/CreateSchemes • Remove“Default”Tags • RemoveDependentPlugins • Priorities • Resolutions • CleanupExtras • ProjectRoles • RenameWorkflows Whydowemodify • CreateCustomFieldContexts
- 91. ISSUE FIELD CONTEXTS ModifiedFields Keep Target Context
- 92. ISSUE FIELD CONTEXTS Projects Tobe Migrated Attributes Reference as parameters
- 93.
- 94.
- 95.
- 96.
- 97.
- 98.
- 99.
- 100. • Linked byuserName or lowerUserName not by "ID" • issues • changeHistory • auditLogs • ID's within the entities XML, are utilized to link other JIRA data. • customFields • workflows • statuses • resolutions • screens • As well as the ID's of the above and their association to a Scheme, or a project are linked by numerical "ID" BitofHistory
- 101. CommonFixes • MissingCustomFields • MissingProjectRoleID •NoAdministratorAccountafterSystemImport • InvalidCharacters