On this page:

Dual Licensing support

All versions 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 Atlassian Universal Plugin Manager

After generating the license key, all you have to do is access the Administration → Add-ons section in your JIRA instance and paste the key into the corresponding add-on textbox.

Kepler Licensing

The Kepler license is a file (keplercf-pro.lic) which must be placed in the <JIRA_HOME>/kepler folder. This file may be obtained contacting the cPrime support. After copying it in that directory, and ensuring that JIRA has read and write access to the file, you must restart JIRA.

cPrime License Page

Validity of our add-ons may be checked in the Administration→ Add-ons section, selecting the cPrime Plugins Configuration → Licensing menu.

The page shows the expiration and maintenance date, user limit and validity message for each license, including various warnings that reflect the current status of all your licenses.