Ho, ho, ho!
They say it’s the best time of the year, but this Christmas you have yet another reason why you should be over the moon. We are launching the new version of JJUPIN and it’s better than ever!
It's our pleasure to present you the preview of JJUPIN 4.0, a major release aimed to cover even more JIRA functionality; JQL support and email handling being just two of them. We know you have long-awaited this release, so let's forget about fancy introductions and let's move to the improvements and new features brought by this version.
Support for JIRA Agile & JIRA Service Desk
Because we wanted to make things easier for you, JJUPIN Agile was incorporated into JJUPIN. This simplifies the install for JIRA Software users while providing you with all the available routines from JIRA Agile. The little support we already had for JIRA Service Desk was also incorporated into JJUPIN. Existing JIRA Agile customers will be required to renew only the JJUPIN license.
As a note, JIRA Service Desk integration is a major area for improvements and we know that. We expect to provide you with more routines and LiveFields support for JIRA Service Desk in the near future. You asked for it, our integration team asked for it, and we're determined to cover this as soon as possible.
SIL Mail Handler
Introduced into JJUPIN 4.0, SIL Mail Handler eliminates the need for another mail handler add-on, and moves the processing of mails in the language you already know: SIL. Upon receiving an email, you may add an issue, comment, add files from the mail as attachments, transition the issue, call another system or anything you want. This feature has been already tested into production.
We finally added support for JQL in SIL. This means that you may create filters of arbitrary complexity, tailored to your needs. We have added a JQL function that acts on issues, and two more to support special searches on other elements of the JQL (components, priorities, projects, etc). This also means that your filters may be dynamic, showing results that depend on the user executing them. I can see your smile from here!
Scheduler & Services
Redesigned from scratch, this is another major area that got completely changed with this release. We favored scheduler over standard services, since it has a more flexible configuration (CRON) and all its configurations have become permanent; simply put, jobs will survive JIRA restarts. Backward compatibility is assured, no changes are required in the code using currently the scheduler. Services have been removed and existing scripts bound on standard services will be moved to scheduler.
You can now have multiple SIL scripts listening for the same JIRA event and multiple events mapped on the same SIL file. Of course, you can reorder the script execution to achieve what you want, in the order that you want.
Start / Stop Scripts
You asked for a stop script, we added it. Now you have both start and stop events treated in JJUPIN and you may call JIRA-Agile routines from there.
Licensing has changed. When the license gets invalid, instead of disabling the add-on, we let the runtime execute your scripts; however the entire administration pages go disabled. This is hugely important because your installation will maintain the integrity of the operations until you will buy the license.
Plugin Suite Changes
Of course, as you already may know by now, we have a suite of add-ons, and not just JJUPIN. Touching the base means changing the entire suite, and this was a huge challenge. Version 4.0 brings in some important changes, we'll briefly review them below.
The old mechanism of data storage was removed completely, and after this upgrade, our custom tables will be dropped. This impacts backup and restore strategy, simplifying it, since the new mechanism (Active Objects) is recognized by Atlassian, and therefore natively understood by JIRA.
Scripts may be stored now on disk, as before, or in database. While keeping them on disk has the advantage of speed, storing them in database may have the advantage of moving them from one installation to another quickly.
Minimal asynchronous SIL execution thread monitoring has been put in place: you can now examine and manage the SIL execution queue more quickly.
UI & SIL Editor
UI has been changed according to Atlassian Look&Feel recommendations. Editor has been largely improved, and we intend to add more on this one, too.
Better support for templates
Creating rich templates for emails is easier now. You can now embed SIL script snippets in an email template (as opposed as only variables), execute it and get a fully formatted message. We added the possibility to parse templates and use them for your own purposes, not only in emails.
We added support for multiple LDAPs. There's now a nice configuration page allowing you to define, edit and remove LDAPs from the configuration.
No more JNDI and JIRA restarts! A datasource, along with its pooling parameters can be defined now directly from JIRA, provided that you already have the JDBC driver installed. The old mechanism is still in place, so use what you like.
New options for remotes
Some previously advanced proxy settings for remotes are now configurable with support for both normal and Windows domain networks.
New options for mails
Mail has got a shiny configuration page, too. Check it, as it now allows you to configure the email sender in different ways, including one which may be helpful for debug.
sendEmail() routine has been upgraded and it’s now capable of auto-detecting if the sent mail is HTML or text. There’s no difference anymore between calling sendHtmlEmail or sendEmail.
In order to incorporate the other two products, alongside with the new rich set of features, the price will be adjusted to better suit the number of users.
Licensing fees structure for JJUPIN, valid from the official release, expected mid Q1 2017, is presented below.
- 10 users – $10
- 25 users - $25
- 50 users - $100
- 100 users - $200
- 250 users - $500
- 500 users - $1000
- 2000 users - $2000
- 10000 users - $4000
- 10000+ users - $6000
We’re an open company,so that’s why we’ll justify the need of changing the prices. This pricing structure was calculated based on the JJUPIN and JJUPIN Agile, which was incorporated into JJUPIN, as well as the new features brought to you by this version. For comparison, here is the list of prices, in USD, for both products, summed and individually:
- 10 users – $45 (JJUPIN $25, JJUPIN Agile: $20)
- 25 users - $85 (JJUPIN $50, JJUPIN Agile: $35)
- 50 users - $170 (JJUPIN $100, JJUPIN Agile: $70)
- 100 users - $320 (JJUPIN $190, JJUPIN Agile: $130)
- 250 users - $600 (JJUPIN $350, JJUPIN Agile: $250)
- 500 users - $600 (JJUPIN $350, JJUPIN Agile: $250)
- 2000 users - $1000 (JJUPIN $600, JJUPIN Agile: $400)
- 10000 users - $1400 (JJUPIN $800, JJUPIN Agile: $600)
- 10000+ users - $1700 (JJUPIN $1000, JJUPIN Agile: $700)
You will notice an oddity at the 250/500 license tier. That was because we maintained a very stable price policy, something you should also expect in the future. In short, we believe that the new pricing better reflects the value of the product, already covering a wide range of features, while enabling us to improve the support we’re providing right now.
Somehow, we feel like JJUPIN has become a new tool, getting the JIRA integration and customization at a new level, and we hope that it will increase your users' satisfaction with JIRA.
Happy JIRA customization to you, all!
This is not the release of JJUPIN, but a preview of the release. The upgrade tasks are missing – we’re still working on them, making sure your transition will be smooth - and the version is time-bombed to expire on 30th of March, 2017. Do not install in production systems! Note that it will not work alongside previous add-on releases, e.g. do not install it in the same instance which contains any add-on downloaded from our published list on https://marketplace.atlassian.com