/
Coverage View

DATA CENTER AND SERVER | CLOUD

Coverage View

Owned by RamandeepK (Unlicensed)
Last updated: Feb 21, 2025 by Ron B. Bugay
5 min read

Overview

The Coverage View provides an overview of project requirements or subsets of requirements from the point of view of completeness. The view helps answer questions such as how well high-level requirements can be traced to lower-level requirements, or other types of issues such as test cases. It helps identify gaps in coverage that may require attention.

The view displays a customizable chain of linked requirements or other issue types, organized into columns. This arrangement helps users assess the extent to which these requirements cover the entire domain. A completeness calculation aids in this assessment. For example, you can determine if customer-level features are appropriately broken down into technical requirements, and whether these are in turn covered by test cases.

To navigate to the coverage view, open an easeRequirements project and select Coverage > Coverage in the easeRequirements menu bar.

The effective use of the coverage view depends on the practices of your organization and its development process. You need to take into account how different types of requirements or other types of issues are structured, as well as how they are linked together and used. An organization might have different practices for different situations, so different coverage views can be defined and saved in the Coverage View.

The sheer number of requirements in a project may also be a challenge to understanding the coverage, so identifying significant subsets of the requirements and organizing them in different views is also an effective practice.

User Interface

A coverage view is displayed as a table whose cells contain requirements or other types of issues. The columns, called “levels”, indicate relationships between the requirements. For example, the first column might contain high-level Customer Requirements, while the second column contains lower-level Functional Requirements, representing a relationship between the two sorts of requirements. The relationship is defined by links between the requirements.

By default, the relationship involves adjacent columns, but it is possible to have a relationship between non-adjacent columns. This is indicated with the option Column Basis in the coverage view configuration.

By inspecting the table, users can quickly identify gaps in coverage by the appearance of cells labeled “Not covered”. For example, a Customer Requirement that has no related Functional Requirement is easily spotted by that label appearing in an adjacent cell in the Functional Requirement level. Each level except for the first also displays a completeness percentage.

Coverage views with different configurations can be saved and are displayed to the left of the coverage view. The views are organized into two folders:

  • Personal Views are only available to the user that created them. By default, a newly created view is personal.

  • Public Views are available to everyone who has access to the Jira project.

Coverage View Operations

Purpose

Operation

Comment

Purpose

Operation

Comment

Open saved coverage view

  • Select the desired view in the left panel.

 

Create new coverage view

  • Select New View.

  • Configure the first column in the dialog:

    • Enter a label for the column.

    • Determine the source of the issues for the column using one of the options:

      • Issue types:

        • Projects: Select the desired projects.

        • Issue types: Select <any> for issues of any type or select one or more types.

      • Filter: Select an existing filter.

      • JQL: Enter a JQL query. The default value is the project JQL for the current project.

    • Select Select.

  • Configure the second column in the dialog:

    • Select Add Coverage Level.

    • Enter a label for the column.

    • Determine the source of the issues for the column using one of the options:

      • Issue types:

        • Projects: Select the desired projects.

        • Issue types: Select <any> for issues of any type or select one or more types.

      • Filter: Select an existing filter.

      • JQL: Enter a JQL query.

    • Select Add.

  • Optionally configure additional columns as above.

  • Select Save.

  • Enter a name for the view.

  • Select Save icon.

As of the third level, the option Column Basis becomes available, making it possible to select a different level as the anchor of the relationship rather than the level immediately to the left.

Create new coverage view from existing view

  • Select a saved view.

  • Modify the view configuration as desired.

  • Select Save As.

  • Enter a name for the new view.

  • Select Save icon.

 

Export coverage view to Excel

  • Select Export Excel from the context menu of the view.

  • Select the file name under which the Excel file should be saved.

Export is handled as a background task since the operation may take some time. It is possible to continue working while the task is executing. A save file dialog will appear when the task is complete.

Export coverage view to Excel using a template

  • Select Export Template… from the context menu of the view.

  • Select the file name under which the Excel file should be saved.

Copy coverage view link to clipboard

  • Select Copy Link Address from the context menu of the view.

 

Delete coverage view

  • Select Delete from the context menu of the view.

  • Select Delete.

 

Change position of coverage view in list

  • Grap desired view.

  • Drag and drop it in the desired position.

This is how to change a view from private to public or vice-versa. Only the owner of the view can do this.

Update level configuration

  • Select the update icon in the header of the desired column.

  • Modify the level configuration in the dialog.

  • Select Update.

 

Add level

  • Select Add Coverage Level.

  • Enter a label for the column.

  • Determine the source of the issues for the column using one of the options:

    • Issue types:

      • Projects: Select the desired projects.

      • Issue types: Select <any> for issues of any type or select one or more types.

    • Filter: Select an existing filter.

    • JQL: Enter a JQL query.

  • Select Add.

As of the third level, the option Column Basis becomes available, making it possible to select a different level as the anchor of the relationship rather than the level immediately to the left.

Remove level

  • Select the remove icon in the header of the rightmost column.

Only the rightmost level can be removed.

Enable folder filter

  • Select the filter icon in the header of the first column.

  • Select a project.

  • Select a folder in the project tree.

  • Select Select.

It obviously makes no sense to select a project that is not one of the projects used in the view.

Disable folder filter

  • Select the filter icon in the header of the first column.

  • Select Reset.

 

Link or unlink issues

  • Select “…” in an issue cell.

  • Select the desired action:

    • Create linked issue

    • Link existing issue

    • Remove issue link

  • Complete the ensuing dialog.

 

Review suspect link

  • Select the suspect icon in an issue link flagged as suspect.

 

Open issue

  • Select the issue key in a cell.

 

Determine display fields

  • Select Display Fields from the easeRequirements menu bar.

  • Select the fields to be displayed in the issue cells.

  • Select Save.

The fields displayed by default are Summary, Key, Issue Type, Status, Priority, and Suspect Links. The configuration is saved when the view is saved.

The default list of fields for a project can be configured by the app administrator by selecting “Save as project default” text.

Refresh coverage view

  • Select Refresh.

 

Formulas for calculating coverage completeness

By default, the row based formula is used in calculating coverage completeness percentage. The formula can be configured in the global easeRequirements Configuration by a system administrator.

Row based

given a = total number of rows in previous column b = number of rows not covered in current column ((a - b) / a * 100

Issue based

given a = number of issues in previous column b = number of issues in previous column not covered in current column ((a - b) / a * 100

Related content

Display Fields Configuration
Display Fields Configuration
easeRequirements Data Center - Requirements Management for Jira
Read with this
Coverage View
Coverage View
easeRequirements Cloud - Requirements Management for Jira
Read with this
4.15 - 4.21
4.15 - 4.21
easeRequirements Data Center - Requirements Management for Jira
Read with this
Activate Projects
Activate Projects
easeRequirements Data Center - Requirements Management for Jira
Read with this
Managing easeRequirements Permissions in the Jira Project Permission Scheme
Managing easeRequirements Permissions in the Jira Project Permission Scheme
easeRequirements Data Center - Requirements Management for Jira
Read with this