Skip to end of banner
Go to start of banner

Licensing

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 »

Dual Licensing support

Versions 2.0.4 and up support both Kepler and Atlassian licenses, but you only need one valid license to run the plugin, which can either be provided as the jjupin.lic file, or as the key generated via the Atlassian Marketplace.

The order in which the licenses are checked is:

  1. Atlassian License
  2. Kepler License

It is strongly recommended that you do not install both licenses at once, as this might yield unwanted results. For example, consider that you have an Atlassian License with the support date expired and one valid Kepler License. In this case you cannot update the plugin, because the Atlassian License is checked first and its support date is expired.

Atlassian Licensing

The Atlassian Marketplace allows you to easily purchase or generate an evaluation license for JJupin.

Using Universal Plugin Manager 2.0.1+

After generating the license key, all you have to do is access the Administration-> Plugins section in your JIRA instance and paste the key into the corresponding plugin textbox.


Kepler Licensing

The Kepler license is a file (jjupin.lic) which must be placed in the <JIRA_HOME>/kepler folder. 

You can view details for all the license files situated in the kepler folder, by accessing the Kepler Licenses page from Administration > Add-ons > Licensing menu.

The page shows the expiration and maintenance date, user limit and validity message for each selected kepler license.

If the license is expired, user limit is exceeded or license is targeted for a different JIRA server id, a red colored message shows the status:

If kepler license is close to expiration date (less than 10 days remaining), a warning message is displayed, showing the remaining time:

Reminder

Don't forget that you need only one valid license to run the plugin.

Since version 4.0.0, in order to make sure that your JIRA instalation is safe even if you forget to buy or change your license, in JJUPIN 4.0 we let the runtime to execute your scripts (the plugin won't disable).

Removing an unused license

  1. If you want to remove a no longer used Atlassian license, this can be done in UPM (for UPM 2.0.1+) by removing the old license key and clicking Update. To remove a Kepler license, you have to delete the correspondent .lic file from the kepler folder.
  2. For versions alpha and beta of JJUPIN 4.0.0 we provide free licensing until 2nd of February, 2017.


  • No labels