Jira Data Center migration Project

[Ruchi Uppal]

For Our Jira Data Center migration Project, I would like to know if you can provide me with a Test plan/ test Script that we can create when our Users are Testing in the Sandbox instance and then in Production for each of their Projects/ Dashboards to make sure all the Data got migrated over without any issues.

Thanks!

[Kian Stack Mumo Systems · Accepted solution]

@Ruchi Uppal, 

You can use the following test cases to get started. You should review Atlassian's recommendations on testing strategies.

Test Case	Expected Results	Actual Results
Can you reach Jira in the Cloud?	You should be able to reach Jira at the supplied URL.
Can you sign in?	You should be able to sign in using your AD username and password (If using Atlassian access with an IDP)
Are you able to see projects you had access to in Jira Server?	All projects you had access to in Jira Server should be visible
Are you able to search for tickets?	Users should be execute searches for tickets.
Are the searches returning similar results to server?	Searching for tickets should return mostly the same results as they did in server. Because these are moving environments there may be some differences.
Do you have access to the same filters you did in server?	Any filter the user had access to in server they should have access to in Cloud.
Is ticket content showing as expected?	Ticket content should align with server fairly closely. Because these are moving environments there may be some differences.
Are attachments showing on tickets as expected?	Any attachment present in server should have been migrated to Cloud.
Are you able to download, upload, and remove attachments from tickets, including those added before the migration?	Users should be able to work with attachments as they were ale to on server.
Are you able to create tickets where you need to?	Users should be able to create tickets in any project they were able to in server.
Are the expected fields available when creating a ticket?	All expected fields should be available.
Are drop down options the same as they are in server?	Drop down options should match what they were on server.
Are you able to modify tickets where you need to?	Users should be able to edit tickets if they could on server.
Are you able to comment on tickets?	Users should be able to comment on tickets if they could on server.
Are you able to transition tickets?	Users should be able to transition tickets if they could on server.
Are there any issues with the workflow?	Workflows should operate correctly.
Can you link tickets together?	Users should be able to link tickets.
Are you able to see agile boards you had access to before?	Users should have access to agile boards they had on server.
Can you work with tickets on the board in the way you could before?	Users should be able to rank tickets, drag them into sprints, ect if they could on server.
If you could create a sprint on a board in server, can you do it in Cloud?	If a user could create a sprint in server they should be able to do so in Cloud.
Can you close sprints and view sprint reports?	If a user could close a sprint in server they should be able to in Cloud.
Do you have access to the same dashboards you did in server?	Users should have access to the same dashboards they did on server.
How do your dashboards look?	Dashboards should appear similar to how they did in server. There may be some unsupported gadgets that will not render.
Can you modify dashboards in Cloud you could in server?	Users should be able to modify dashboards they can in server.

[Ruchi Uppal]

Thank you, Kian. This is great!

[Kian Stack Mumo Systems]

I'm glad I could help!

[Els Bassant · Accepted solution]

Hi Ruchi, and welcome to the community!

I don't have any test plans our scripts, but I can tell you that the only (minor) issues that we had with our migration were plugin related. Specifically with plugins that had to update to a new version. Other than that there were exactly zero issues.