What's new in Power Scripts™ for Jira

Looking for the documentation on the newest versions of Power Scripts for Jira 8 for Server/Data Center? Click here !

Looking for the documentation on the newest versions of Power Scripts for Jira 8 for Server/Data Center? Click here !

We have added many great features to our Power Scripts for Jira 4.5.0 as well as improved the existing ones. Although we have changed the internal architecture of our apps suite we, of course, kept the backward compatibility with Simple Issue Language or SIL.


Log Viewer

The newest version of Power Scripts for Jira now comes with an in-built log viewer, designed to help save Jira admins time as they can now simultaneously write scripts and check their logs all in the same place. Previous to this in-built log viewer, Power Script for Jira server users would have to waste time accessing their logs in the server if they come across an error in their script. Starting with SIL engine 4.5.0 we have added the log viewer to the SIL Manager. This log viewer is ready to use and does not need further special configuration, just upgrade to the newest version of Power Scripts for Jira server and you'll be on your way.

SIL Runner

Testing scripts has never been easier than with the addition of the SIL Runner to the SIL Manager. Now scripts can be run directly from the SIL Manager and messages can be written to an output console below the editor. Not only that but the scripts can be run in the context of an issue by adding the key of a test issue in the Run Configuration.

Log Viewer and SIL Runner in the SIL Manager

Persistent Variables

Often, during the development of an integration or a special customization, people get stuck because of the lack of context. Questions appear: which user clicked the button for the next status? Did the manager approve this item? What was the result of the calculation in the previous step? The traditional way of dealing with such questions was to create additional custom fields to keep that data, usually hidden from users (so excluded from the screens schemes), effectively adding bloat to Jira and ultimately worsening indexing - and general - performance. To help you answer these kinds of questions, Simple Issue Language™ (or SIL™) acquired, starting with version 4.5.0 of the SIL Engine™, a new feature, called persistent variables.


Our new Webhooks feature will give Power Scripts for Jira users the possibility to run existing SIL scripts, from outside of the Jira/Confluence instance, by using a REST/HTTP client and retrieve the results of the script run.

This will now enable Power Script for Jira users to take data from any external application, opening the door far and wide to a multitude of integration possibilities. Previously, like many other plugins, there were limitations in accepting external application's JSON routines as they were often in a format incompatible to Power Scripts' own REST API routines. However, we are pleased to announce that now Power Scripts for Jira is able to accept any type of JSON format from an external system in Jira.

Other Changes

  • We have made the version numbers for all of the Power add-ons consistent. In order to ensure binary compatibility between the SIL Engine and other Power add-ons, both should be upgraded to the same version.
  • Now you can work with Salesforce on environments with proxy access.
  • Integration with SAFe EPIC to Feature Translator for Jira - routines for the SAFe implementations
  • Enhanced support for the Portfolio for Jira plugin - we added more routines to work with Portfolio fields.
  • Verified compatibility with Jira 7.12.3

Changes in the SIL Engine

In the v4.5.0 of the SIL Engine™ we have done the following:

  • Implemented the persistent variables to simplify your usage of SIL™
  • Verified compatibility with Jira 7.12.3
  • Bug fixes:
    • Now when you use the JQL functions, the JQL is limited on the results, not on the examined tickets
    • Other minor bug fixes

Also See