On this page:

Requirements

User Group Picker PRO 4.0 is compatible with JIRA 7 only, starting with JIRA version 7.0; JDK version should be at level 8.

User Group Picker PRO 4.0 bundles the Warden and KATL-Commons plugins. It is upward compatible meaning it works with any Warden version 4.0 and up and with any KATL-Commons version 4.0 and up. Please see Installation Notes chapter below for an explanation.

Installation via Atlassian UPM (Universal Plugin Manager)

If you are not familiar with Universal Plugin Manager (UPM), please read this document before we begin.

Steps to install

Step 1: Go on the Administration menu → Add-ons → Find new add-ons

Step 2: Search for our add-on by entering "User Group Picker PRO" in the search box

Step 3: Press on "Buy now" or "Free trial" to install

That's all.

Manual Install

Do not worry, it's a simple task to install it manually:

Step 1. Download the correct obr file from Atlassian Marketplace.

Step 2. Go to Administration->Add-ons->Manage add-ons. Install the previously downloaded obr file by using 'Upload add-on' link.

Step 3: [Optional, but highly recommended]: Besides the User Group Picker PRO™ app itself, there are also two dependencies, two complementary apps that are installed with it:

• SIL Engine™ – a library having countless utility routines, but most importantly, it contains a SIL™ language parser. 
• warden – licensing support for several of our apps
  
  

Installing via Atlassian Universal Plugin Manager

If you are connected to the Atlassian Marketplace website from your Jira administration console, you can install our apps directly from the Marketplace. 
For more information, see Installing add-ons and Universal Plugin Manager pages.

1. Log into your Jira as Admin.
2. In the cog wheel menu, go to Add-ons.
3. In the Find new add-ons section, search for "User Group Picker PRO™".

This installation method is the quickest way. You can also install by file upload, as described in the next section.

Installing by file upload

It might seem more complicated but a manual install is quite easy to do. After all, all you have to do is to copy certain files. Here's how.

1. Download the User Group Picker PRO™ file from the Atlassian Marketplace.
2. Log into your Jira as Admin.
3. From Jira administration console, click the Manage add-ons link.
4. Click Upload add-on and select the file you downloaded, and click Upload.
5. If not already done, enable logging on our modules. Open with a text editor of your choice the

...

1. Jira log4j configuration

...

1. file JIRA_INSTALL_DIR/atlassian-jira/WEB-INF/classes/log4j.

...

1. properties and add these 2 lines at the end of it. 

2. Restart

...

1. Jira.

   log4j.logger.com.keplerrominfo=INFO, filelog log4j.additivity.com.keplerrominfo=false

...

What should I do if I installed an incompatible version?

User Group Picker

...

1. Warden add-on, responsible for licensing of the cPrime products. This add-on is not published on Atlassian Marketplace, however is it bundled in all our paid add-ons,
2. KATL-Commons, providing all SIL functionalities and common services built over JIRA
3. User Group Picker PRO add-on, providing the user picker custom field you're looking for

KATL-Commons and Warden are shared across our line of products. If any of those become disabled, the functionality built on top of them will cease to work. Unlike Warden, KATL-Commons is published on Atlassian Marketplace and updates that are compatible for this add-on should be installed as soon as they appear, since they contain bug fixes and enhancements.

What should I do if I installed an incompatible version?

...

PRO™ is only compatible with Jira v7.0.0 and higher; JDK version should be at level 8.

If you have installed an incompatible version, perform the following steps:

1. Uninstall warden.
2. Uninstall the SIL Engine™.
3. Uninstall the User Group Picker PRO™.

4. Install the version of the User Group Picker PRO™ that is compatible with your Jira version.
   SIL Engine™ and warden should now have the right versions as well.

5. Check any dependent apps, such as Power Scripts for Jira™, Power Actions™, etc. Note that these apps must be re-enabled manually.