Getting Started with easeRequirements for Jira Cloud

Atlassian has adopted a new core terminology for Jira Cloud:

project → space
issue → work item
issue type → work type

We are in the process of updating easeRequirements to use the new terminology. Until that work is completed, this documentation will use the old terms.

To get started with easeRequirements for Jira Cloud, the only thing you need to do is install the application - see Installation of easeRequirements for Jira Cloud.

easeRequirements does not require any specific issue types, link types, custom fields or workflow.

There is one configuration that we highly recommend to take full advantage of easeRequirements, but even that is optional - see Specify Folder Issue Type.

In order to get the maximum benefit from the easeRequirements features that support traceability, you should have a well thought-out link configuration - see How to Configure Jira Links to support Traceability.

We have no specific suggestions about your workflow or custom fields. Thanks to our extensive experience in requirements management solutions, we can suggest some issue types that may be worth considering for your own organization - see Suggested Issue Types for Requirements Management.

If you are moving from Data Center to Cloud, the following pages will be helpful:

Comparison of easeRequirements Cloud and Data Center Features: This page explains the differences between both editions and helps you understand what to expect.
Selecting a Migration Path from Data Center to Cloud: This page helps you decide how to migrate app data from your DC instance to your Cloud instance.
How to migrate from Jira Data Center to Jira Cloud using ReqIF: This page explains the entire migration process using the “ReqIF” standard.