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.
...
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.
...
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 JSDJira Service Desk, this is in our roadmap, and we'll try to do add this in the near future.
Mail Handler
...
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.
...
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.
...
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.
...