In case you haven’t heard, Atlassian recently announced that they’re accelerating the journey to Cloud with the end of life plan for Server. To help you best strategize your product transitions to Cloud, we want to familiarize you with the feature similarities and differences for Power Scripts™ for Jira on Data Center, Server, and Cloud.
FEATURE |
SERVER / DC |
CLOUD |
NOTES |
---|---|---|---|
Event Listeners |
● |
● | |
External Database Integration | ● | ● | |
Jira Agile Support | ● | ![]() |
• Direct support scheduled for Q4 2020. • Indirect support via REST is available. |
Jira Portfolio (Roadmaps) Support | ● | ![]() |
• Direct support scheduled for Q1 2021. • Indirect support via REST is available. |
Jira Service Desk Support | ● | ![]() |
• Direct support scheduled for Q4 2020. • Indirect support via REST is available. |
JQL Functions | ● | ●* | *Available to the extent to which cloud allows. |
JSD Automation | ● | ![]() |
Investigating feasibility. |
Live Fields (Screens) | ● | X | This will never be possible in Cloud. Alternative solutions are being explored. |
Mail Handlers | ● | X | This will never be possible in Cloud. |
Remote LDAP Integration | ● | ● | |
Remote Systems | ● | ● | |
REST Service | ● | ● | |
Scheduled Services | ● | ● | |
Script Gadget | ● | ● | |
SIL® Panel | ● | ● | |
SIL® Template Language | ● | ● | |
Slack Support | ● | X | |
Start/Stop Scripts | ● | X | This functionality is not relevant in Cloud. |
Switch User | ● | X | This functionality is not permitted in Cloud. |
Version Control | ● | ● | |
Webhooks | ● | ● | |
Workflow Viewer | ● | ![]() |
Scheduled for Q3 2021. |
Workflows Conditions/ Validators | ● | ●* | *Available to the extent to which Cloud allows. |
Workflows Post Functions | ● | ● |
To further elaborate:
JQL Keywords vs JQL Functions
A JQL function performs an evaluation of the issue in real-time during the JQL search. This type of search is not possible in Jira Cloud and may never be possible in Cloud because it is a very resource-intensive way of searching.
A JQL keyword is meta-data for an issue that has been evaluated and saved before a JQL search. This type of search will always be faster and more efficient than a traditional, functional search since the results can be indexed and it is less resource-intensive.
Live Fields (screen manipulation)
Due to the limitations of the Atlassian Connect framework and the Forge framework this type of direct screen manipulation will never be possible (or permitted) in Cloud. Alternative solutions using panels are being explored.
Conditions/Validators
The only solution available for custom workflow conditions and validators is through the Atlassian Expressions language which has limited functionality compared to SIL.
Routine Availability
Currently, not all of the routines that exist in Server are supported by the API available in Cloud. Some routines are missing from Cloud that has not been created yet although we are working on them. These actions (for the missing routines) are still supported using the REST API.
Review the feature comparisons of our other apps available on Cloud:
– Surveys for Jira
– Issue History Collector
– Electronic Signatures
Download a free Power Scripts™ for Jira Cloud trial today, and we will be announcing new Cloud features in the future. Stay tuned!
Tagged with: API support, external database integration to jira, Jira agile support, Jira portfolio (roadmaps) support, JQL Keywords, JSD automation, JSD support, live fields screen manipulation, mail handlers, remote LDAP integration, remote systems, REST service, routine availability, schedule services, script gadget, SIL® panel, SIL® templates, start/stop scripts, switch user, version control, webhooks, workflow viewer
Categorized in: Automation, Cloud, Conditions, custom fields, Jira Admin, JQL Functions, Routines, Validators, Workflows