Assess

Full value parity.

◐

Partial value parity.

ALT

No value parity, but custom script alternatives are available.

No value parity or alternatives are available.

◐

Atlassian created an API called UI Modifications on the Forge platform, which made it possible for ScriptRunner to build Behaviours. As more capabilities become available in the UI Modifications API, more functionality can be built in ScriptRunner's Behaviours feature. Behaviours is a key focus within ScriptRunner's product development roadmap. We are actively enhancing this feature by integrating new capabilities as Atlassian release them. 

Notable differences for Behaviours on Cloud:

• You can apply Behaviours to the Create, Issue and Transition views of a Jira issue. Refer to Behaviours Supported Fields and Products for details.
• Jira Service Management is not currently supported.
• Behaviours may be applied to certain supported fields only. Not all fields are currently supported in all available views. Refer to our documentation to discover which fields are supported on each supported view.
• Currently, there is no option to map a behaviour to all issue types; they must be selected individually in the configuration.

Although Jira Service Management support is currently not available from Atlassian, we will implement this functionality into Behaviours as soon as it is released. See our Behaviours Limitations section for more details.

Notable parity for Behaviours on Cloud:

• Compatible with Jira Software.
• Company and team-managed projects are supported.
• Support for over 30 system and custom fields types across all three views (Create, Issue and Transition).

Built-In: Bulk Copy SLA Configuration

Built-In: Bulk Fix Resolution

◐

Jira Cloud does not allow clearing resolutions (selecting None option).

Built-In: Bulk Import Custom Fields

ALT

The same function can be achieved by writing your own script in the Script Console but with all the caveats of time limitations, API availability, etc.
Check out our page on Scripting in ScriptRunner for Jira Cloud for tips. 

Built-In: Change Dashboard, Filter or Board Ownership

ALT

Similar functionality can be achieved by writing a script in the Script Console to call the Change Filter Owner and the Bulk edit dashboards APIs to update and filter dashboard owners.

We have created a sample script for this here.

Built-In: Clean Workflows

Built-In: Clear Groovy Class Loader

Built-In: Configuration Exporter

Built-In: Copy Custom Field Values

◐

Jira Cloud currently supports: 

• Single to multi, for example, single select to multi-select, single user picker to multi-user picker.
• Multi to single, however, only the first value will be retained.
• Multi to text, the values are concatenated with a comma.
• Short text to unlimited text.

Built-In: Copy Project

ALT

Built-In: Generate Events

Built-In: Guardrails - Maximum number of comments per issue.

ALT

You can use the numberOfComments JQL Keyword to search for issues that exceed a maximum number of comments using a JQL query similar to the one below.

numberOfComments > 5

You can then manually review these issues and delete the comments if needed.

To automate this, you could run this query in the Script Console calling the Archive Issues by JQL API with this JQL to archive all issues returned that exceed this threshold.

Built-In: Guardrails - Maximum number of unrchived projects

ALT

Similar functionality can be achieved by writing a script in the Script Console to call the Get Projects Paginated API and filter out results where the insights.lastIssueUpdateTime Property is older than a specified timeframe, such as two years.

You can then call the Archive project API for every project returned by this API.

We have an example script to do this here, which can be run on the script console.

Built-In: Guardrails - Maximum Number of Issue Links Per Issue

ALT

You can use the numberOfLinks JQL Keyword to search for issues that exceed a maximum number of links using a JQL query similar to the one below.

numberOfLinks > 5

You can then manually review these issues and delete the links if needed.

If you wanted to automate this, you could run this query in the Script Console calling the Archive Issues by JQL API with this JQL to archive all issues returned that exceed this threshold.

Built-In: Guardrails - Maximum Attachment Size

Built-In: Guardrails - Maximum Change History Records Per Issue

Built-In: List Scheduled Jobs

Built-In: Re-index Issues

Built-In: Script Registry

Built-In: Service Desk Template Comments

Built-In: Split Custom Field Contexts

ALT

Built-In: Switch to a Different User

Built-In: Test Runner

Built-In: View Server Log Files

Application links

Assets

Attachments

◐

Cloud includes:

• Retrieve attachments.

Comments

Cloud includes:

• Retrieve comments.
• Add comments.

See the Cloud Work with Comments page for more details. 

Entity properties

Cloud includes:

• ProjectEntityProperties
• IssueEntityProperties
• UserEntityProperties
• CommentEntityProperties

For each of the above you can:

• set the value of an entity property (as strings, JSON, integer, long, LocalDate, LocalDateTime, boolean)
• retrieve the value of an entity property
• check for the existence of an entity property
• retrieve the keyset of all entity properties stored against an entity

See the Cloud Work with Entity Properties page for more details. 

Fields

Cloud includes:

• Create, read, update, and delete system fields.
• Create, read, update, and delete custom fields. 

See the Cloud Update Fields page for more details.

Filters

Groups

◐

Cloud includes:

• Retrieve groups and group members.
• Add users to a group.

See the Cloud Work with Groups page for more details. 

Cloud includes:

• Create, read, update, and delete issues. 
• Transition issues.
• Search for issues.

See the Cloud Work with Issues page for more details. 

Permission schemes

Projects

Cloud includes:

• Create, read, update, and delete projects.

See the Cloud Work with Projects page for more details. 

Send emails

Users

◐

Cloud includes:

• Retrieve users.
• Retrieve user group membership.

See the Cloud Work with Users page for more details. 

Watchers

◐

Jira Cloud supports: 

• A minimum interval of 1 hour. 
• There is a limit of 240 seconds for script executions. After running for 240 seconds, the logs will be collected, and the code will be terminated.

Jobs: Escalation Service

◐

Jira Cloud supports:

• The maximum number of issues you can modify in any execution of an Escalation Service job is 50. In other words, we limit the number of issues returned by each JQL query to 50 issues.
• A minimum interval of 1 hour.

Jobs: Issue Archiving Job

ALT

JQL Functions: addedAfterSprintStart

This JQL function will identify issues that were added to an open sprint after the feature was released (21st December 2020). Historical searches for issues added to open sprints prior to that date are not supported.

JQL Functions: aggregateExpression

JQL Functions: commented

ALT

There is not a like-for-like function in Jira Cloud, but depending on what you want to achieve you could use some ScriptRunner JQL Keywords to achieve the same: firstCommentedDate, lastCommentedDate, commentedOn, commentedBy, lastCommentBy.

JQL Functions: completeInSprint

ALT

JQL Functions: componentMatch

◐

JQL Functions: dateCompare

JQL Functions: earliestUnreleasedVersionByReleaseDate

JQL Functions: epicsOf

◐

JQL Functions: expression

JQL Functions: fileAttached

ALT

There is not a like-for-like function in Jira Cloud, but depending on what you want to achieve, you could use some ScriptRunner JQL Keywords to achieve the same: numberOfAttachments, attachmentType, firstAttachmentDate, lastAttachmentDate, fileAttachedBy.

JQL Functions: hasAttachments

ALT

There is not a like-for-like function in Cloud, but depending on what you want to achieve, you could use the ScriptRunner JQL Keywords: numberOfAttachments to have the same result.

JQL Functions: hasComments

ALT

The ScriptRunner JQL Keyword: numberOfComments can be used.

JQL Functions: hasLinks

ALT

There is not a like-for-like function in Jira Cloud, but depending on what you want to achieve, you can use native Jira keywords issueLink and issueLinkType. Refer to Atlassian's JQL Fields.

JQL Functions: hasLinkType

ALT

There is not a like-for-like function in Jira Cloud, but depending on what you want to achieve, you can use the native Jira keyword issueLinkType. Refer to Atlassian's JQL Fields.

JQL Functions: hasRemoteLinks

JQL Functions: hasSubtasks

You could use the ScriptRunner JQL Keywords: numberOfSubtasks to have the same result.

JQL Functions: inactiveUsers

JQL Functions: incompleteInSprint

ALT

JQL Functions: issueFieldExactMatch

This feature is called issueFieldMatchExact in Jira Cloud.

JQL Functions: issueFieldMatch

JQL Functions: issuesInEpics

This JQL function is available for Jira company-managed projects but not for team-managed projects.

JQL Functions: jiraUserPropertyEquals

JQL Functions: lastComment

ALT

There is not a like-for-like function in Jira Cloud, but depending on what you want to achieve you could use the lastCommentBy or lastCommentedDate ScriptRunner JQL Keywords to achieve the same.

JQL Functions: lastUpdated

ALT

There is not a like-for-like function in Jira Cloud, but depending on what you want to achieve you could use the updated native Jira keyword to search for issues last udpated within a certain timeframe.


JQL Functions: linkedIssuesOf

JQL Functions: linkedIssuesOfAll

JQL Functions: linkedIssuesOfAllRecursive

JQL Functions: linkedIssuesOfAllRecursiveLimited

JQL Functions: linkedIssuesOfRecursive

JQL Functions: linkedIssuesOfRecursiveLimited

JQL Functions: linkedIssuesOfRemote

JQL Functions: memberofRole

JQL Functions: myProjects

JQL Functions: nextSprint

JQL Functions: overdue

JQL Functions: parentsOf

JQL Functions: portfolioChildrenof()

◐

JQL Functions: portfolioParentOf()

◐

JQL Functions: previousSprint

JQL Functions: projectMatch

In Jira Cloud this function uses the projectKey, whereas in server/data centre it uses project name.

JQL Functions: projectsOfType

ALT

JQL Functions: recentProjects

ALT

JQL Functions: releaseDate

JQL Functions: removedAfterSprintStart

JQL Functions: startDate

JQL Functions: subtasksOf

JQL Functions: versionMatch

JQL Functions: workLogged

Listeners: Adds the current user as a watcher

ALT

Listeners: Clone an issue and links

ALT

The same function can be achieved by writing your own script in the Custom Listener but with all the caveats of time limitations, API availability, etc. Check out our page on Scripting in ScriptRunner for Jira Cloud for tips. 

We have an example script to show how to clone an issue and link it here.

Listeners: Create a sub-task

ALT

The same function can be achieved using a Custom Listener and this script for creating a subtask(s). 

Listeners: Custom Listener

◐

Listeners: Execution failure notifier

ALT

In Jira cloud, the Notifications group setting allows you to specify a group of users who will get an email each time a script fails, but this can't be configured to send to other messaging services such as Slack because the notify API doesn’t allow you to email external emails.

Listeners: Fast-track transition an issue

ALT

The same function can be achieved using a Custom Listener and a script to transition an issue.

Listeners: Fires an event when a condition is true

ALT

In Jira Server/Data Center, this listener is used to send an email when a condition occurs. In Jira Cloud, you can add the condition to be matched to the script conditions box, which uses the Jira Expression Framework. 

When the condition is true, you can call the Send notification for issue API to send a notification to specific users, similar to what is shown in the example script here.

Listeners: Post a message to slack

ALT

The same function can be achieved using a Custom Listener and a script to Post to Slack.

Listeners: Send a custom email (non-issue events)

ALT

The same function can be achieved using a Custom Listener and a script to send a notification.

The notify API doesn’t allow you to email external emails and only allows you to notify users, groups, or user fields (such as assignee or reporter) on an issue.

Listeners: Send a custom email

ALT

The same function can be achieved using a Custom Listener and a script to send a notification.

The notify API doesn’t allow you to email external emails and only allows you to notify Jira users, groups, or user fields (such as assignee or reporter) on an issue. The API does not allow users to send notifications to themselves.

Listeners: Version Synchronizer

ALT

The same function can be achieved by writing your own script in the Custom Listener but with all the caveats of time limitations, API availability, etc. Check out our page on Scripting in ScriptRunner for Jira Cloud for tips. 

Mail Handler

Resources: Database Connection

ALT

Resources: LDAP Connection

ALT

Resources: Local Database Connection

Resources: Slack Connection

ALT

REST End-Points: Custom End-Point

Unlike Server/Data Center, Jira Cloud does not offer custom end-points. Instead it uses the Atlassian REST API. However, with ScriptRunner, you can still connect and interact with other systems by calling their external APIs.

Script Console

There is a limit of 240 seconds for Cloud script executions. After running for 240 seconds, the logs will be collected, and the code will be terminated.

Script Editor

UI Fragments

◐

ScriptRunner for Jira Cloud supports Web Panels only. Script source must be specified (and accessible to Jira), inline script is not available. 

Script Fields: Custom Script Fields

◐

Due to current limitations, the value of Scripted Fields will currently only refresh on issue view.

Script Fields: Custom Picker

Script Fields: Database Picker

Script Fields: Date of the first transition

ALT

Script Fields: Issue(s) Picker

Script Fields: LDAP Picker Field

Script Fields: No. of times in a status

ALT

The same function can be achieved by writing your own script in the Custom Scripted Field but with all the caveats of time limitations, API availability, etc. Check out our page on Scripting in ScriptRunner for Jira Cloud for tips. 

Script Fields: Remote issue(s) picker

ALT

Script Fields: Show parent issue in a hierarchy

ALT

The same function can be achieved by writing your own script in the Custom Scripted Field but with all the caveats of time limitations, API availability, etc. Check out our page on Scripting in ScriptRunner for Jira Cloud for tips.

Script Fields: Time of Last status Change

ALT

Script Edit Permissions

Hapi Code Helper

In-App Communications

◐

Switch User Function

Anonymous Analytics

User Editor Settings

Workflow > Condition: All sub-tasks must be resolved

ALT

The same function can be achieved using a custom script condition and a script to check all sub-tasks are resolved.

Workflow > Condition: Allows the transition if this query matches a JQL query

Workflow > Condition: Checks the issue has been in a status previously

ALT

Workflow > Condition: Custom script condition

ALT

Cloud conditions use Jira Expression language where the result must be true or false.

Cloud function name:

• ScriptRunner Script Condition

Incompatible fields that should be discarded:

• Test Against - Used for testing scripts when creating or editing validators only, so can be safely discarded.

Workflow > Condition: Field(s) required condition

ALT

Workflow > Condition: Group(s) condition

ALT

The same function can be achieved using a custom script condition and a script to check the user is within a specified user group.

Workflow > Condition: JQL query matches condition

Workflow > Condition: Linked issues condition

ALT

Workflow > Condition: Project role(s) condition

ALT

The same function can be achieved using a custom script condition and a script to check the user is within a specified project role.

Workflow > Condition: Regular expression condition

ALT

Workflow > Condition: Simple scripted condition

◐

Cloud conditions use Jira Expression language where the result must be true or false, it does not use Groovy.

Workflow > Condition: User in field(s) condition

ALT

Workflow > Condition: User(s) and User Group(s) condition

ALT

Workflow > Post Function: Add a comment to this issue

ALT

Workflow > Post Function: Add/remove from sprint

Cloud function name:

• Add/remove from sprint

Incompatible fields that should be discarded:

• Return user to Execute As. In Cloud, users can run as the Add-on or initiating user only and cannot choose a specific user to run the post function.

Workflow > Post Function: Adds a comment to linked issues when this issue is transitioned

ALT

Workflow > Post Function: Adds the current user as a watcher

ALT

Workflow > Post Function: Archive this issue

ALT

Workflow > Post Function: Assign to first member of role

ALT

The same function can be achieved using a custom post function.

Cloud function name:

• Assign Issue

Incompatible fields that should be discarded:

• Include Reporter
• Include Assignee
• Force Assignee

Workflow > Post Function: Assign to last role member

ALT

The same function can be achieved using a custom post function.

Workflow > Post Function: Clear field(s) post function

ALT

Workflow > Post Function: Clones an issue, and links

Cloud function name:

• Clone Issue

Incompatible fields that should be discarded:

• Fields to copy

• Copy Comments

• Copy Subtasks

• As User - In Cloud, users can run as the Add-on or initiating user only and cannot choose a specific user to run the post function.

Workflow > Post Function: Copy field values

ALT

The same function can be achieved by writing your own script in the custom post function but with all the caveats of time limitations, API availability, etc. Check out our page on Scripting in ScriptRunner for Jira Cloud for tips.

We have an example script to show how to clone an issue and link it here. 

Workflow > Post Function: Create a sub-task

Cloud function name:

• Create Sub-task

Incompatible fields that should be discarded:

• Fields to copy

• As User - In Cloud, users can run as the Add-on or initiating user only and cannot choose a specific user to run the post function.

Workflow > Post Function: Custom script post-function

Cloud function name:

• Run Script

Workflow > Post Function: Fast-track transition an issue

Cloud function name:

• Fast-Track Transition Issue

Incompatible fields that should be discarded:

• Transition Options

Workflow > Post Function: Fires an event when condition is true

ALT

This post function is used to send an email when a condition occurs in Jira Server/Data Center.

In Jira Cloud you can add the condition to be matched to the script conditions box on a custom post function.

When the condition is true, you can call the Send notification for issue API to send a notification to specific users, similar to what is shown in the example script here.

Workflow > Post Function: Post a message to Slack

ALT

The same function can be achieved using a custom script post-function with a script to post to Slack. 

Workflow > Post Function: Send a custom email

The equivalent in Cloud is “Send Notification”.

Workflow > Post Function: Set issue security level depending on the provided condition

ALT

Workflow > Post Function: Transition parent when all subtasks are resolved

◐

Cloud function name:

• Transition Parent Issue

The same function can also be achieved using the  fast-track transition issue built-in post function and adding a condition script to verify all subtasks are resolved. 

Workflow > Validator: Custom script validator

ALT

Cloud conditions use Jira Expression language where the result must be true or false.

Cloud function name:

• ScriptRunner Script Validator

Incompatible fields that should be discarded:

• Test Against - Used for testing scripts when creating or editing validators only, so can be safely discarded.

Workflow > Validator: Field(s) changed validator

ALT

Workflow > Validator: Field(s) required validator

ALT

Workflow > Validator: Regular expression validator

ALT

Workflow > Validator: Require a comment on transition

ALT

Workflow > Validator: Simple scripted validator

◐

Cloud conditions use the Jira Expression language where the result must be true or false, it does not use Groovy.

Workflow > Validator: User in field(s) validator

ALT