Testing After Migration is Complete
Now that you have completed your Tempo migration, you should do a final check to see if the migration was successful or if there are loose ends that still need to be fixed. If you did a full planning exercise prior to migrating - and followed the steps outlined in our migration planning section - you should have a comprehensive feature list ready for your Jira Cloud instance. You can then use testing procedures to determine if the features and functionalities on your list are available and working as intended in your Jira Cloud instance.
Ideally you should have a team of stakeholders and resources that can conduct the testing with you. You cannot and should not do everything on your own. Please keep in mind that the Jira and Tempo permissions that you and your team have will impact which Tempo data you can test and access.
Here is a list of recommended steps when testing:
Test the overall time tracking and planning workflow.
Start by logging your time, running reports and sending your timesheet for approval. Ensure that you are comfortable with the results and gather feedback from your stakeholders to ensure that they are satisfied as well. Test response times and ensure that Tempo performs well.
Test individual functionalities, such as the Tempo Account and Team custom fields – as well as any add-ons. Test to confirm that the Tempo Account and Tempo Team custom fields are performing as intended. You can try exporting Account data to CSV from the Accounts page as well as confirm that the Account and/or Team custom fields are available within Jira issues. If you use add-ons with your Tempo instance – such as EazyBI or Scriptrunner, or other integrations for your HR or ERP systems – be sure to test them as well.
Re-examine your project permission settings. The project permission settings can be different on Tempo Cloud than Tempo Server. For instance, Tempo Cloud has the View issues hours permission option that does not exist in Tempo Server. Make sure to examine this and other permissions to determine if adjustment are needed.
Get a support/log file from Atlassian and see if there are any errors in the log that refer to Tempo. Inspect your browser console while performing Tempo actions and see if you catch any 4xx or 5xx errors.
A final note
It is critical to give yourself ample time for testing, as the amount of time needed is always underestimated. Ensure that you have built in time to make adjustments as needed. You may need extra time to iterate on problems.
Should something fall between the cracks, don’t hesitate to reach out to Tempo Support. Tempo has a comprehensive migration team that is willing and able to assist you for problems of any kind. We are here to help.