Concepts
easeRequirements Ultimate for Jira builds on Jira’s existing features like issue types and custom fields to implement Review Management processes. This gives you full flexibility to model the tool according to your organization’s needs without adding unnecessary overhead to your Jira instance.
The following table explains the key concepts of the Review Cockpit and shows how Jira can be configured to support them. It is assumed the Jira administrator knows how to implement this configuration in Jira.
The recommended names in the table are just that - recommended. If your Jira instance is already configured with appropriate data types, but with different names, or if different names make more sense in your organization, easeRisk for Jira can be configured to use those names instead of the recommended ones.
Concept | Explanation | Jira Data Type | Recommended Name | Note |
|---|---|---|---|---|
Review | A review brings together a number of issues and a group of users that will examine them to determine whether to accept or reject them individually. | issue type | Review | A Review is represented by a Jira issue of a predefined issue type. The Review issue type should be configured in Jira to have a workflow and fields appropriate for your organization's review processes. |
Review Scope | These are the issues that are the subject of the review. | N/A | N/A | The review scope is supported directly by the application. |
Reviewer Subtask | Each reviewer is assigned a subtask associated with the review. | sub-task issue type | Sub-task | The standard Jira sub-task issue type can be reused here. |
Moderators | These are the users that are responsibe for conducting the review and who determine when it is complete. | custom field for review issues | Moderators | |
Reviewers | These are the users that are responsibe to review the issues in the scope of the review. | custom field for review issues | Reviewers |
Jira Configuration
To implement the above-suggested configuration, you need to perform the following actions in the Jira Administration:
Create the Review issue type.
If it doesn’t exist already, create the Sub-task issue type and ensure that the Jira sub-task feature is enabled.
Create the Moderators and Reviewers custom fields of type User Picker (multiple users).
Associate the fields Moderators and Reviewers with the Review issue type screens.
Associate the Review issue type with your projects using Jira schemes.
If the names used for the various data types in your Jira configuration differ from those recommended above, be sure to use the ones used in your instance instead of the recommended names in the configuration options below.
App Configuration
easeRequirements Ultimate for Jira is configured using Review Schemes. A Review Scheme is a collection of configuration options that can be applied to several projects. This simplifies the setup effort and ensures that the Review Management practices are applied uniformly in your organization.
The application comes with a default scheme that is associated with all projects by default. This section explains in detail how to edit the default scheme to implement the recommended setup.
Risk Scheme
The default scheme should be edited as follows:
Go to Jira navigation > Review > Review Schemes.
Select the Edit option for the scheme named “Default Review Scheme”.
Specify the options as follows:
Option | Value | Explanation |
|---|---|---|
Review Issue Type | Review | The issue type used to represent reviews. |
Sub-task Issue Type | Sub-Task | The issue type used to represent review subtasks. |
Moderators Fields | Moderators | The custom fields used for moderators. |
Reviewers Fields | Reviewers | The custom fields used for reviewers. |