Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this page:

Table of Contents

Requirements

Rights DNA 4.0 is only compatible with Jira 7, starting with Jira version 7.0; JDK version should be at level 8.

Rights DNA 4.0 bundles the Warden and KATL-Commons apps. 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 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 3: Press on "Buy now" or "Free trial" to install


Manual Install

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

...

Step 3. Install a license for rights dna, which can either be provided as the rightsdna.lic file, or as the key generated via the Atlassian Marketplace. See more details about this in Licensing.

Installation Notes

Rights DNA packages together 3 Jira apps:

...

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 app 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?

  1. Remove (uninstall) Rights DNA
  2. Uninstall Warden app
  3. Uninstall KATL-Commons app
  4. Install the right version of Rights DNA (the one compatible with your Jira). Make sure you use the OBR file you downloaded or use directly the UPM search & install feature (recommended)
  5. KATL-Commons and Warden should now have the right versions as well

  6. Check any dependent apps. After you uninstall katl-commons and warden, some apps may remain disabled, so you may need to re-enable them manually. (warning)