DATA CENTER AND SERVER | CLOUD

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 15 Next »

Overview

You need to be a Jira Administrator to install R4J – Requirements Management for Jira and manage plugins. Make sure you have the latest version of the Universal Plugin Manager (UPM) installed.

After successful installation of R4J using one of the methods described below, you can begin exploring the plugin by activating a project - see Activate Projects. If you want to use Microsoft Excel to export and import requirements with R4J, please follow the instructions in R4J MS Excel Plugin.

Technical requirements

The system requirements and recommendations to install the R4J plugin are the same as those for your version of Jira.

The minimum supported Jira version is 8.8 since R4J version 4.8.0. Please refer to the compatibility list in the version history at the Atlassian Marketplace. Note that Jira 7 is only supported up to R4J 4.5.0 as a manual download.

Installation via UPM

  • As a Jira Administrator, navigate to Administration > Manage apps > Find new apps.

  • Enter “R4J” as search criteria.

  • Select either “Buy Now” or “Free Trial” and confirm the app installation.

Installation via Manual Download

  • Download the installation file of the latest version of R4J from the version history at the Atlassian Marketplace.

  • As a Jira Administrator, navigate to Administration > Manage apps > Manage apps.

  • Select Upload app.

  • In upload app dialog, browse for the installation file previously downloaded and select Upload.

Project Creation Template

The plugin installs the Requirements Management project template with the workflow shown to the right using the following issue types:

  • Customer Requirement

  • Functional Requirement

  • Non-Functional Requirement

  • Improvement

  • New Feature

  • Test Case

 You are free to use these issue types and workflow or modify them to suit your organization. They are not mandatory for R4J.

  • No labels