Licensing

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 keplercf-pro.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 Kepler Custom Fields Pro.

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 (keplercf-pro.lic) which must be placed in the <JIRA_HOME>/kepler folder. You can either generate and download a free evaluation license by registering on our site and accessing the Licenses section, or you can purchase the plugin by following these instructions.

You can view details for all the license files situated in the kepler folder, by accessing the Kepler Licenses page from Administration > Add-ons > Kepler Licenses 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: