FAQ: Migration and ScriptRunner Migration Suite
Q: What are best practices for using the ScriptRunner Migration Suite?
A: Check out the following pages for the most comprehensive look at how to use the tools:
- Best Practices for the Migration Analyse and Assess Tool
- Best Practices for the Migration Agent
- Best Practices for the Dev and Deployment Tool
Additionally, when using scripts from ScriptRunner Migration Suite, validate them using these methods:
- Always test in a sandbox/test instance in Jira Cloud first.
- Review code before deploying to production.
- Ask the Migration Agent to explain its reasoning if you are unsure of an answer.
- Challenge suggestions from the Migration Agent that seem wrong.
- Monitor execution history in your Jira Cloud instance after deployment.
- Use version control in your Dev and Deployment project so you can roll back changes if needed.
Tip: The example repository uses git, but you can use whatever version control system your organization is familiar with.
Q: Where can I get more information about the ScriptRunner Migration Suite, AI, and data residency?
A: The AI Training and Usage and Data Residency and Privacy pages.
For in depth information about data privacy, please read our terms and conditions. By using this tool, you agree to the terms of:
- The Adaptavist Group's EULA
- Adaptavist's DPA and Privacy Policy
- Specific addendums and supplementary terms which apply for this product:
- Legal Notice
Q: Does the ScriptRunner Migration Suite replace the need for a technical consultant:
A: No, ScriptRunner Migration Suite does not replace the need for a technical consultant. Instead, it aims to empower Technical Consultants by enhancing their productivity, reducing the time spent on script migration, and allowing them to focus on tasks that matter most.