Prerequisites

• Administrator access to both Jira DC and Jira Cloud instances

• Inventory of existing Power Scripts

• Knowledge of Simple Issue Language (SIL)

• Understanding of cloud environment constraints

• Review the Jira DC to Cloud script migration reference to learn which scripts migrate successfully and which scripts require readjustment.

Migration method

You can use an automated or manual migration method

.

Automated migration

For automated script migration, use a tool such as

Jira Cloud Migration Assistant (JCMA) or

Configuration Manager for Jira (CMJ)

. When using a tool, the following consistencies help ensure script compatibility:

• Project and issue type names

• remain exact matches between Jira DC and Jira Cloud. This ensures project keys or issue

• type names used directly in scripts will continue to operate after migration.

• Custom field names

• are preserved as exact matches between Jira DC and Jira Cloud, but custom field IDs will be different.

  • If SIL aliases were used

• • , which is a best practice

• • , you can update the SIL aliases settings in

• • Power Scripts for Jira Cloud. This way, the scripts will automatically work with the new

• • IDs.

  • If custom field aliases were not used

• • , the migration is a good opportunity to

• • start using them.

• Status and transition names

• remain exact matches between Jira DC and Jira Cloud. This ensures scripts using status names, transition names, or

• IDs should continue to operate after

• migration.

For details, see Script migration process.

Manual migration

If you aren’t using a migration tool, scripts can still be migrated by uploading them to the SIL manager or

through the Apps > Power Scripts > Self Help menu in Jira Cloud admin settings and then

configuring them manually.

Script migration process

Post-migration testing

After the migration, test your scripts by performing a syntax check in the SIL Manager (in Power Scripts for Jira Cloud).

If a script passes the syntax

test, it means

that:

• The functions

• shown in

• this code are compatible

• with both Jira DC and

• Cloud environments.

• The syntax of the script it correct.

• Custom field

• IDs are correct or have been updated in the alias file

• .

Some scripts may not

work identically between DC and cloud

environments and can require adjustments due to differences in project names, issue type names, JQL queries,

or other script-contained information. While using migration tools (JMCA or CMJ) improves the chances of successful script migration, these elements may still need to be adjusted to ensure the scripts operate in the cloud instance as expected.

Required post-migration script changes

When migrated between Jira DC and Jira Cloud, the following script types require additional changes: conditions and validator scripts, Live Fields, and mail handler scripts. In addition, all existing scripted JQL functions/keywords must be updated for Jira Cloud.

Conditions and validator scripts

Jira Cloud uses Jira Expressions language for conditions and validators; scripted conditions and validators are not currently supported in Jira Cloud

. While many users find Jira Expressions challenging and time-intensive to work with, there are alternative approaches. As with other features in Jira Cloud, rather than directly converting scripts and replicating Data Center solutions, consider rethinking your approach. To learn about ways to continue using SIL scripted conditions and validators in Jira Cloud, see this article.

issue.issueType.name.match('^(Dev Task)$') == null || 
(issue.issueType.name.match('^(Dev Task)$') != null && 
issue.parent.subtasks.filter(subtask => subtask.assignee != null).length == 
issue.parent.subtasks.length)? true : false

//SIL code
boolean passConditionValue = true;
if(issueType == "Dev Task") {
    for(string s in subtasks(parent)) {
        if(s.issueType == "Dev Task && isNull(s.assignee)) {
            passConditionValue = false;
        }
    }
}
setIssueEntityPropertyValue(key, "passCondition", passConditionValue);

//Jira Expression
JSON.stringify(issue.properties['passCondition']).includes('true')

Live Fields scripts

Live Fields works differently in Jira DC versus Jira Cloud.

In Jira DC	In Jira Cloud
Live Fields is a

Because of these differences, all Live Fields scripts

must be converted from SIL to JavaScript when migrating.

Example

//SIL (Data Center)
lfSet("summary", "Value to set");

//JavaScript (Cloud)
getFieldById("summary").setValue("Value to set");

Mail handler scripts

The Power Scripts incoming email service

works differently in Jira Cloud than in Data Center. Due to Atlassian’s Cloud architecture, email scripts In Jira Cloud:

• Cannot intercept messages sent to your primary Atlassian address (youremail@atlassian.net).

• Can only intercept emails going to

• an external email accounts, such as Gmail.

Due to the differences in email handling between DC and Cloud, email scripts require different functions in each environment. Existing DC email scripts must be updated to use the new Cloud-compatible functions.

IncomingEmail mail = getIncomingEmail();
string issueKey = matchText(mail.subject, "[A-Z][A-Z]+-[0-9]+"); // find an issue key in the subject
if(isNull(issueKey)) {
	// if no issue key found, create a new issue
    string [] fields = {};
    fields += {"reporter", currentUserKey()};
    fields += {"assignee", getUserByEmail(mail.cc[0]).key}; 
    string newIssue = createIssue("TEST", "", "Task", mail.subject, "Minor", mail.body, {}, "", "", 0, fields);
    attachAllFilesFromEmail(newIssue);
    %newIssue%.watchers = getUserKeysFromEmails(mail.cc); 
} else {
	// if issue key found in subject, add a comment
    addComment(issueKey, currentUserKey(), mail.body);
}

IncomingEmail mail = getIncomingEmail();
string issueKey = mail.subject;
if(issueExists(issueKey)) {
    // add comment
    string commentText = mail.body;
    string userCommenting = getUserByEmail(mail.from).key;
    addComment(issueKey, userCommenting, commentText);
    attachAllFilesFromEmail(issueKey);
} else {
    // create issue
    string summary = mail.subject;
    string description = mail.body;
    string [] fields = {};
    fields += {"reporter", getUserByEmail(mail.from).key};
    createIssue("SCRUM", "", "Task", summary , "Minor", description, {}, "", "", fields);
}

Scripted JQL functions

and their keywords

When users write JQL queries that include custom scripted functionality (via keywords), Jira DC and Jira Cloud handle the execution of the scripted JQL functions/keywords

in fundamentally different ways. This difference stems from Jira's core architecture, not from Power Scripts functionality.

These architectural differences require the following changes to JQL script construction for Jira Cloud:

• Scripts no longer contain their own JQL searches within their code.

• Return statements require additional Cloud-specific operations.

• JQL scripts in Jira Cloud can update the search values of parent and child issues as well as

• the value within the issue that triggered the script.

Due to these differences in script execution, all existing scripted JQL functions must be updated to use the new cloud methods

, even though the keywords users type in their JQL queries remain the same.

Converting Groovy scripts to SIL

If your migration plan includes converting Groovy scripts to SIL, familiarize yourself with the key differences between the Groovy and SIL approaches to scripting.

Jira DC to Cloud script migration reference

Learn more about which scripts migrate successfully from Jira DC to Cloud and which scripts will require adjustment.

Useful tools and scripts for post-migration script adjustment