Comparison of easeRisk Cloud and Data Center Features
Summary
easeRisk Cloud already supports the majority of core risk management functionality available in Data Center.
Recent Cloud releases significantly expanded parity, including dashboard gadgets, matrix improvements, and advanced board configuration capabilities.
Remaining differences are primarily related to platform-specific implementation constraints and advanced configuration scenarios.
For many advanced use cases, Jira Automation provides flexible alternatives in Cloud.
Details
The easeRisk 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. The page will be regularly updated.
Feature Comparison
Feature | easeRisk | easeRisk | Comment |
|---|---|---|---|
| Scheme configuration works the same including general configuration, Risk Matrix, Assessment Criteria and Quick Filters for risks definitions.
| ||
| Board configuration for risk portfolio management works the same including general configuration, Risk Matrix definitions, Quick Filter for risks definitions.
| ||
| Risk Register view and functionality is comparable between both editions. The only difference today is that the workflow state cannot yet be modified inline in Cloud, this will be added in next version (1.3). | ||
Both editions support the same matrix reports: Single Matrix View, Side-by-Side Comparison View, Inline Comparison View. | |||
Both editions support the same top risk report including risk trend visualization | |||
The Cloud edition supports same gadgets as Datacenter: Risk Matrix and Risk Register Summary | |||
The DC Formula Editor is not available in Cloud. Jira automation can be used also to gain more flexibility in the calculated results The DC Formula Editor relies on Jira-internal functionality that the Cloud environment does not expose to our app. Jira automation can be used as an alternative: rules can recalculate values whenever issue content is modified. This approach is in fact more flexible than the Formula Editor, calculations are not limited to the current issue and can take linked issues, parents, or children into account. | |||
Export |
| All export views work according to the same principle. | |
Migration of work item data |
| The Jira Migration assistant transfers risks, measures, and the link relations between them from DC to Cloud; no issue-level data is lost. There is currently no migration path for the easeRisk configuration: schemes, boards, registers, and reports must be re-created manually in the target system. In practice, customers often use this as an opportunity to consolidate or rework configurations rather than carry legacy structures forward. | |
Migration of easeRisk configuration |
|