Use the Analyse and Assess Tool

Check out the following sections to learn how to analyse an export of a Jira instance:

Upload an export to assess and analyse

Follow these steps to start using the Assess and Analyse tool:

Create or get a script export from the Jira instance with ScriptRunner you want to work with.
Tip: See the Script Registry export from ScriptRunner for Jira Data Center documentation for details on how to create a script export.
Open the ScriptRunner Migration Suite, and log in with your Atlassian ID or email.
Navigate to the Assess and Analyse tool using the toggle or a tile.
Enter a name for Name this analysis.
Drag and drop or upload your script export zip file to the analyser.
Select Upload and Analyse.

How you use the results depends on your processes. You can find guidance in the section below and recommendations on the Best Practices page.

Understand your results

As you view your results, these definitions will be helpful:

Observations: Information that may be helpful to you in your migration.
Ready to Migrate: These configurations are ready for migration. They may include informational messages about possible cloud limitations, but the configuration is otherwise complete. A rewrite will still be required, but all necessary components exist in ScriptRunner Cloud.
Review Recommended: These are configurations with warnings that might not be blockers, but they do signal areas requiring script adjustments, testing, or acceptance of functional limitations in the Cloud environment.
Critical Findings: These are configurations with at least one critical blocker. The next step is to decide whether the configuration needs to be migrated to Cloud, can be migrated, or replicated differently. Blockers occur when:
- The feature is not supported in Cloud.
- Scripts rely on Java APIs or server-side features missing from Cloud's REST API-only architecture, requiring complete rewrites.
- Integrations require direct database or file system access, which cannot be migrated and need alternative solutions or may block migration.

When your results are ready and the Overview tab is selected, you will see the Migration Readiness and Feature Breakdown sections.

Migration readiness

The following sections help you analyse your entire export as a whole:

Overall Progress: progress bar to show how many configurations are ready for migration.
Script Breakdown: Shows how many scripts are unique and duplicated.
Critical Findings: Shows how many critical findings you have.

Feature breakdown

The second section you'll see on the Overview tab is the Feature Breakdown:

You can select one of the feature categories from the tile or the left navigation to see more information. Once you select a feature, you'll see information focused on the migration readiness of that specific feature.

You'll still see the same progress bar with the status of scripts.

Then, for each configuration, you'll see where it is Applied To, and the number of Observations, Critical findings, Review items, and a Status. To see more information, select See Details.

Script breakdown

Select Script Breakdown in the left navigation to see data for all scripts.

From here, you can see the Script, Usages, Findings status, and Duplication status of every script in your export. Click View Script to see where each script is used:

Click the links to see the analysis of the script.

Export as PDF report

Select Export as PDF Report to get your assessment results in a PDF. You can access this feature on the Overview page of the Assess and Analyse tool:

The PDF includes your:

Your Cloud migration readiness assessment
Executive summary, including main risks and script conversion tips
Feature breakdown, with quick wins and needs attention
Findings that need redesigning and adapting
Your Groovy codebase details, including script complexity and API conversion
Feature analysis, like Behaviour details
Suggested approach for recommendations on a migration path
Decisions to make before you start your migration

For example, this is what the Executive summary looks like in the PDF:

Tip: This PDF can be shared with stakeholders that do not have access to ScriptRunner Migration Suite to aid in your migration.

Take next steps

Each script overview shows the number of information messages, things to review, and critical findings.

It also includes the following tabs:

Analysis Findings: Lists all messages for the configuration, along with next steps and more information.
Configuration: An overview of the selected configuration.
Script Analysis: If applicable, it shows an inline review of the script for the selected configuration, displaying info, warning, and blocker messages.

On the Analysis Findings tab of the configuration, you'll have options for next steps:

Explain this configuration: Select this for a detailed explanation of the script.
Convert this configuration: If applicable, you can select Convert this configuration to attempt to convert the Data Center script to a Cloud script.

Note: Selecting Explain the configuration or Convert this configuration moves you into the ScriptRunner Migration Agent.

Work with other exports

You can add more than one export to the tool. To add more or move between exports, follow these instructions:

Analyse another zip file

To analyse a different zip file, select New analysis on the left of the screen:

Retrieve previous results

Results from analysing a zip file are stored in your browser. You can view previous results in the panel on the left:

Warning: This tool only stores results in the browser. If you log in elsewhere, you must reupload your data. Additionally, the data is stored per user. If another member of your team logs in, they will not be able to see your old exports. They will also have to upload.