Skip to end of banner
Go to start of banner

What's new in Power Scripts™ for Jira 4.5.0

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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

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.

Webhooks

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.


  • Added the Log Viewer and the runner log to the SIL™ Manager to save you time and simplify your debugging and working scripts in general. It also replaces several log plugins, consider that!
  • Implemented the persistent variables to simplify your usage of SIL™
  • Webhooks - now you can create the REST endpoints used by external apps that would be able to run SIL scripts and retrieve results from those SIL scripts.
  • 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.


We have added many great features to our Power Scripts™ for Jira 4.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™. As you will see, we have also redesigned all administration pages making them aligned with the Atlassian guidelines. 

Contents

Updated to work with Simple Issue Language™ 4.0.

We maintained the backward compatibility with SIL. We have also updated Power Scripts™ for Jira in order to let you use all the goodies that SIL 4.0 brings.

Licensing

So far we used to disable our apps when the license expired. In order to make sure that your Jira installation is safe even if you forget to renew your license, in Power Scripts™ for Jira 4.0 we let the runtime execute your scripts as configured, however, the configuration and administration pages will be disabled. 

Power Scripts™ for Jira Agile and Jira Service Desk

We have incorporated JJUPIN Agile into Power Scripts™. This way, you can use all the routines from Jira Agile without any additional purchase. Also, the support we had for Jira Service Desk has been incorporated as well. At the moment we have limited support for Jira Service Desk, this is in our roadmap, and we'll add this in the near future.

Mail Handler

You can now process incoming mail using SIL scripts. 

Here's a simple example on how you can parse an email:

IncomingEmail mail = getIncomingEmail();

string issueKey = matchText(mail.subject, "[A-Z][A-Z]+-[0-9]+");
if(isNull(issueKey)) {
        string [] fields = {};
        fields += {"reporter", currentUserKey()};
        fields += {"assignee", getUserByEmail(mail.cc[0]).key};

        string k = createIssue("TEST", "", "Task", mail.subject, "Minor", mail.body, {}, "", "", 0, fields);
        attachAllFilesFromEmail(k);
        %k%.watchers = getUserKeysFromEmails(mail.cc);
} else {
        addComment(issueKey, currentUserKey(), mail.body);
}

Scheduler and Services 

We have removed standard services from Power Scripts™ for Jira 4.0 – all your scripts will be migrated to the scheduler, because it provides a more flexible mechanism. 

The new scheduler does now keep the jobs alive across Jira restarts, like the SIL services did before.

SIL Listeners

Power Scripts™ for Jira 4.0 comes with even more versatile listeners. You can now configure multiple listeners for the same event or multiple events mapped on the same listener and re-order the execution of the scripts.

SIL JQL

Long awaited, this JQL functionality opens wide new possibilities for users. Take a look at the following JQL examples:

key in silJQLExpression('not elementExists(watchers, reporter)', 'project = TEST')

project = TEST and key in silJQLExpression('reporter == assignee', '')

For simple filters you can use boolean expressions, no matter how complicated. 

For more general searches you have to use two or more JQL functions, namely 'silJQL(silfile, params ...)', returning a single result (such as you can use it with =, ~, ...), and 'silJQLList(silfile, params ...)' returning multiple results (operators 'in', ...). These two can be used to dynamically return priorities, components, and so on.

Start/Stop Scripts

As you may know, we already had a start up script mechanism in our older versions of Power Scripts™. Starting with version 4.0, we have introduced a stop script, which (thanks to the integration with JJupin Agile) can also be used with Jira Agile routines. This was not possible on the older versions because the start (and now stop) sequence would have JJupin Agile app disabled before the script was executed.

Workflow Viewer

We have simplified the workflow viewer screen. Now you can see how the screens will look like for a given issue type.

Changes In SIL Engine™

These changes are explained in depth here. We'll list the main changes here as well:

  1. Datasources – Now you can define your databases directly in a dedicated page. The old mechanism (JNDI) will still work, but you definitely will find it more convenient to define the connection pool at a global level.
  2. Multiple LDAPs are now supported – We have provided support for multiple LDAPs and have also designed a new configuration page for LDAP.
  3. We unified our thread pools. You will now be able to see what scripts are running at the moment and will be able to adjust the parameters accordingly.
  4. We have extended the template support so you can add SIL snippets into your email templates.
  5. Scripts can now be stored either on disk or in the database.
  • No labels