We have added many great features in to our Power Scripts for JIRA 4.0 (formerly known as JJUPIN) , from the introduction of new features to the change of othersas well as improved the existing ones. Although we have changed the internal architecture of our plugins suite, we of course kept the backward compatibility with SIL. As you will see, we have also redesigned all administration pages making them aligned to with the Atlassian guidelines.
...
So far we used to disable our plugins when the license expired. In order to make sure that your JIRA installation is safe even if you forget to buy or change 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 the JJUPIN Agile support in into Power Scripts for JIRA (formerly known as JJUPIN). 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 only little limited support for JSD. We know that you want to have more and more routines and Live Fields support, and we'll try to do this in the near future.
...
You can now process incoming mail using SIL scripts.
A 
Here's a simple example on how you can parse an email is this one:
| Code Block |
|---|
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 – all your scripts will be migrated to the scheduler, since because it provides a more flexible mechanism.
...
Long awaited, this JQL functionality opens wide new possibilities for users. Take a look at a few simple the following JQL examples are below:
| Code Block |
|---|
key in silJQLExpression('not elementExists(watchers, reporter)', 'project = TEST')
project = TEST and key in silJQLExpression('reporter == assignee', '') |
...
As you may know, we already had a start up script mechanism in our older versions of Power Scripts for JIRA. Starting with version 4.0, we have also added introduced a stop script, which (thanks to the integration with JJupin Agile, ) can also be used with JIRA Agile routines. On This was not possible on the older versions this was not possible because the start (and now stop) sequence would have JJupin Agile plugin disabled before the script was executed.
Workflow Viewer
The We have simplified the workflow viewer screen has been simplified. You are now able to . Now you can see how the screens will look like for a given issue type.
...
These changes are explained in depth here. However, weWe'll review list the main changes quickly here as well:
- Datasources - You – Now you can now define your databases directly in our a dedicated page. The old mechanism (JNDI) will still work, but you definitely will , for sure, find it more convenient to define the connection pool at a global level.
- Multiple LDAPs are supported now - We now support many now supported – We have provided support for multiple LDAPs and have also designed a brand new configuration page for LDAP.
- We unified our thread pools. You will now be able to see live what scripts are running at the moment and you can will be able to adjust the parameters accordingly.
- We have extended the template support so you can now add SIL snippets into your email templates.
- Scripts can now be stored either on disk or in the database.