The easeRequirements application has two different implementations, one for Jira Cloud and the other for Jira Data Center (DC). In general, both implementations have the same or very similar functionality. However, a few features are not yet implemented in Cloud and in some cases, there are differences in functionality between Cloud and DC. The following table lists the features and describes any differences in the state of implementation and will be regularly updated.
Feature | easeRequirements | easeRequirements | Comment | Documentation |
|---|---|---|---|---|
Folder Structures - Organize requirements in a hierarchical folder structure. |
|
| Adding existing Jira issues and moving them around via Drag and Drop in the project tree is available in both easeRequirements DC and Cloud. | |
|
|
| Both editions provide a tree view for the organization of requirements in a hierarchical folder structure. In DC, folders are a built-in data structure. By contrast, Cloud folders are simply issues of a specified type. The Jira administrator must specify the issue type for folders as part of the overall configuration of easeRequirements - see Specify Folder Issue Type. | |
|
|
| In Cloud, search and filter using plain text or JQL is possible. In DC, several filter options are available including Basic, JQL, Jira Filter, and Folder search filters. | |
|
|
| Since folders are issues in Cloud, they have all the functionality of Jira issues. For example, folders have a history and workflow status, neither of which is available for folders in DC. | |
Reading View - Display requirements inside their hierarchy. |
|
| Both editions provide equivalent functionality. The look and feel is currently different, but alignment between the two is ongoing. | |
Tabular View - Display requirements as a table, suitable for reviewing large numbers of requirements. |
|
| Both editions provide equivalent functionality. The look and feel is currently different, but alignment between the two is ongoing. | |
Version Control - View detailed, comparable change histories to track the evolution of your requirements. |
|
| Both editions provide equivalent functionality. | |
Baselines - Snapshot current data to keep track of milestones and support reviews. |
|
| Both editions provide equivalent functionality. Baselines in DC can get approvals by electronical signatures. | |
Artifact Reuse - Reduce time to market by reusing requirements from existing projects. |
|
| Both editions support requirement reuse by providing copy and paste operations. DC provides several options that can be used to customize what is copied to the new issue, including the folder structure, fields, sub-tasks, attachments and links. The original and copied requirement are can be linked. The administrator can also create predefined reuse configurations. Cloud provides also options that can be used to customize what is copied to the new issue. Folder structure, attachments and link relations from parents to children are included. The original and copied requirement can be linked. Predefined reuse configurations not yet possible. | |
Import - Import requirements in ReqIF format. |
|
| DC allows importing any ReqIF file (as long as a ReqIF mapping is provided). easeRequirements Cloud currently only supports ReqIF import from DC as part of the migration from DC to Cloud. | |
Export - Export requirements in various formats. |
|
| Both editions provide equivalent functionality. | |
|
|
| DC provides export in ReqIF format with a ReqIF mapping. Cloud does not currently provide export in this format. | |
|
|
| DC provides export in Word format in its various views. Cloud only provides export in Word format in the project tree view. | |
|
|
| DC provides export a template based Excel format in its various views. The administrator can provide different export templates. Cloud currently only provides export in a predetermined Excel format in the Coverage View. | |
|
|
| DC provides export in XML format in all of its views. Cloud does not currently provide export in this format. | |
Microsoft Excel Integration - Seamless roundtrip integration with MS Excel. |
|
| Both editions provide equivalent functionality. | |
Traceability Matrix - Visualize and analyze the relationships within requirements as well as other sorts of issues. |
|
| Both editions provide equivalent functionality. | |
Coverage Analysis - Detect gaps in the coverage of your requirements across the hierarchy. |
|
| Both editions provide equivalent functionality. | |
Suspect Logic - Discover requirements that need review when related requirements or other sorts of issues have been changed. |
|
| DC supports suspect logic directly. Cloud does not yet directly support suspect logic. However, it is possible to implement suspect monitoring using native Jira automation. Direct support of suspect logic is on the roadmap. | |
Advanced Queries - Use JQL to query the easeRequirements specific data structures. |
|
| DC extends JQL with “query functions”, while Cloud provides “issue properties” to accomplish the same purpose. Cloud does not yet support queries for links. | |
REST API - Integrate and extend easeRequirements using the extensive API. |
|
| Both editions provide equivalent functionality, due to the nature of the Jira cloud concept the APIs differ. |
