Best Practices
Convert scripts best practices
Use the following tips when rewriting your scripts:
- Create a list of in instance-critical scripts. From there, you can prioritize based on readiness. Focus on INFO scripts first, then move to WARNING scripts and leave BLOCKER scripts last.
- When converting your scripts to Cloud use our Migration Agent. This can be accessed through the Agent tab.
- For any scripts with blockers that can't be fixed, consider if you need the script/configuration. Consider if it can be removed completely or replaced with a native Jira solution.
- House your scripts in an external IDE so they're easy to manage and iterate on.
Embrace Cloud-native solutions
Instead of direct script translations, especially for BLOCKER items, reassess the underlying business needs and explore Cloud-native features. The migration agent can explain what a script does, especially if you inherited it or no longer remember an older script.
Use iterative migration and testing processes
Implement a phased migration approach, moving and testing scripts in small batches. This allows for continuous improvement and reduces risk during the transition.
Tip: For example:
- Phase 1: Migrate mission critical scripts to establish core functionality quickly.
- Phase 2: Address important scripts, adapting as necessary for Cloud.
- Phase 3: Tackle nice-to-have scripts.