Share this page

# Configure entity graphs

You can configure an entity graph to select data to be included in the graph.

In this topic:

## Overview

Configure an entity graph to select data to be displayed and how the data is displayed in the graph.

- To configure an entity graph, select the graph from the Analysis tree, and click the Configuration tab.

- If you have the required administrator permissions, in the Analysis Menu tab of the Analysis View module, select a graph and click the Configuration tab.

- The available configuration options depend on the graph type. Entity graphs of the same graph type share the same configuration options. For example, a progress graph for defects and a progress graph for requirements have the same configuration options.

Back to top

## Configure progress graphs

You can configure a progress graph using the following options:

Option | Description
--- | ---
Period | The time period covered by the graph. Select a time period from the drop-down list: Custom. A time period between any two dates. Set the start and end dates. Week/Month/Quarter/Year. A fixed time period any time in the past. Use the arrows to jump to the next or previous period, or set the start or end date of the period in the drop-down calendars. Last. A time period ending at the current date. Select a time unit (day, week, month, quarter, or year) and set the number of time units you want to cover in the graph. All days. Includes all time periods from the beginning of the project until the current date.
Resolution | The time interval at which data is grouped on the x-axis.
Display | Raw Data. View the number of requirements, tests, or defects over the period of time you selected. Changes over Time. View the change in the number of requirements, tests, or defects over the period of time you selected. Each record begins at 0.
Grouped By | Select a field to determine the information by which OpenText Application Quality Management groups data in the graph. You can group the data only by string or list fields. For cross-project graphs, select QC Projects to group the data by project. If you set a filter on the same field as the Group By field, groups in the graphs may include values that you filtered out. This is because in progress graphs the filter operates on current values, while groupings operate on historical values. For example, the Group By field in a Defects graph is set to Status, and the current filter includes all defects whose status is Open. When the graph is generated, all previous statuses of the open defects, such as Rejected, will appear in the graph even if Rejected was not included in the filter.
Show Not Covered parents | Available for Requirements only. Whether or not to include parent requirements with the Not Covered status.

Back to top

## Configure summary graphs

You can configure a summary graph using the following options:

Option | Description
--- | ---
Y-Axis | Select the data that displays on the y-axis. Count. Display the total number of items (for example, a count of open defects). Sum of. Choose a numerical field. For example, in Defects graphs, choose Estimated Fix Time to display the estimated time required for fixing the defects. Choose Actual Fix Time to display the actual time spent on fixing the defects.
X-Axis | The information displayed along the x-axis of the graph. Tip: In cross-project graphs, select QC Projects to display the data by project.
Grouped | Select a field to determine the information by which OpenText Application Quality Management groups data in the graph. You can group the data only by string or list fields. Tip: For cross-project graphs, select QC Projects to group the data by project.
Show Not Covered parents | Available for Requirements only. Whether or not to include parent requirements with the Not Covered status.
Show full path | If you select Subject, Plan: Subject, Test: Subject, or Test Set: Name in the X-Axis field, OpenText Application Quality Management displays the full path of the test subject folder.
Include Historical Data | Available for Defects only. Enables you to filter entities that have changes in the specified fields by the specified user during the specified periods. For example, you can filter defects whose status was changed from Open to Fixed by you in the last 7 days. To configure historical data, click Configure and specify the following: Field. Select the field that was changed. Value. In the From field, click Update List to specify the old values the field was changed from. In the To field, click Update List to select the new values the field was changed to. Changed By. Select the user who made the change. Changed In. Specify when the change happened.

Back to top

## Configure cycle time by phase graphs

You can configure a cycle time by phase graph using the following options:

Option | Description
--- | ---
Field | Select a field that is used to define phase. For example, if you want to define phase by the Status system field, such as Open, Fixed, and Closed, then select Status for this field. You can also specify a user-defined field to define phases. The user-defined field should meet the following requirements: It's a lookup list field. It enables the History property. It enables verify values. It disables multiple values. For details, see Customize project entities.
End Phase | Select a phase as the end phase of the defect lifecycle. The end phase is not displayed in the X-axis. When a defect enters the end phase, the time it spent on the phase is not calculated, and such defects are excluded from the graph.
X-Axis | Read-only. Auto-filled with what you select in the Field option.
Y-Axis | Select the data that displays on the y-axis. Sum of. Display the total time spent on each phase. Average of. Display the average time spent on each phase.

Back to top

## Configure trend graphs

You can configure a trend graph using the following options:

Option | Description
--- | ---
Period | See Period.
Resolution | See Resolution.
Grouped By | See Grouped.

Back to top

## Configure age graphs

The Age Graph type is available for Defects only. You can configure a defect age graph using the following options:

Option | Description
--- | ---
Age | Select how defects are grouped in the graph: No Grouping. Defects are not grouped. View defects at all available periods. Group at 1 Week. Defects are divided into 2 groups (columns), with one group including defects aged no more than 1 week, and the other group including defects aged more than 1 week. Group at 1 Month. Defects are divided into 2 groups, with one group including defects aged no more than 1 month, and the other group including defects aged more than 1 month. Group at 6 Months. Defects are divided into 2 groups, with one group including defects aged no more than 6 months, and the other group including defects aged more than 6 months. Group at 1 Year. Defects are divided into 2 groups, with one group including defects aged no more than 1 year, and the other group including defects aged more than 1 year. Customize. Defects are divided into a custom number of groups at a custom age interval. Set Customize Grouping Settings for custom periods. For details about how defect age is calculated, see Age Graph.
Customize Grouping Settings | Available when you select Customize in the Age option. Group at. The age interval (in days) at which the defects are grouped. You can use the automatic age interval or specify a custom age interval. Auto. ALM calculates the group-at value as follows: The automatic group-at value = Defect maximum age / Number of Groups. If Number of Groups is also set to Auto, the automatic group-at value = Defect maximum age / 7. Custom number. The default value is 7. You can enter any positive integer less than 100,000. Suppose you enter 10, then defects are divided by the following intervals: 0 to 9 days, 10 to 19 days, 20 to 29 days, and so on. Number of Groups. The number of groups into which you want to divide the defects. You can use an automatic number of groups or specify a custom number. Auto. ALM calculates the number of groups automatically as follows: The automatic number of groups = Defect maximum age / Group-at value. If Group at is also set to Auto, the automatic number of groups is 7. ALM displays 18 groups at maximum. If the automatic number of groups is greater than 18, defects that fall out of the first 17 groups are all included in the last (18th) group. Custom number. The default value is 7. Enter any integer between 1 and 18 (inclusive) you want. Suppose the group-at value is 10 and the number of groups is 5, then defects are divided by the following age intervals: 0 to 9, 10 to 19, 20 to 29, 30 to 39, and 40 to maximum age. Example: If you want to divide defects aged 0 to 14 days in a group, defects aged 15 to 29 days in a second group, defects aged 30 to 44 days in a third group, and defects aged more than 45 days in the last group. You can set Group at to 15, and Number of Groups to 4.
Y-Axis | Select the data that displays on the y-axis. Count. Select Count to display the total number of items (for example, a count of open defects). Sum of. Select Sum of and choose a numerical field. For example, in Defects graphs, choose Estimated Fix Time to display the estimated time required for fixing the defects. Choose Actual Fix Time to display the actual time spent on fixing the defects.
Grouped By | See Grouped.

Back to top

## Configure anomalies graphs

The Anomalies Graph type is available for Defects only. You can configure a defect anomalies graph using the following options:

Option | Description
--- | ---
Phase Defined by | Select the field that defines phases for anomalies graphs. For example, if you want to define phase by the Status system field, such as Open, Fixed, and Closed, then select Status for this field. You can also specify a user-defined field to define phases. The user-defined field should meet the following requirements: It's a lookup list field. It enables the History property. It enables verify values. It disables multiple values. For details, see Customize project entities.
Stuck in Phase | Select a phase. The available values of this field depend on which field you use to define phases. For example, if you want to know how many defects remained in the Open status for a certain duration, select Status in the Phase Defined by field, and Open in the Stuck in Phase field.
Duration | Specify the pending duration for defects that remained in the phase defined by the Stuck in Phase field. For example, if you want to know how many defects remained in the Open status for no less than 5 days, enter 5 in the >= field.
X-Axis | See X-Axis.
Y-Axis | See Y-Axis.
Working Days | Select the working days. Non-workings days are not counted when calculating how long a defect remained in a specific phase.

Back to top

## Configure planned vs. actual graphs

The Planned vs. Actual (Last Test Run ) and Planned vs. Actual (Test Run History) graph types are available for Test Instances only. You can configure a planned vs. actual graph using the following options:

Option | Description
--- | ---
Period | See Period.
Resolution | See Resolution.
Grouped By | Read-only. Planned vs. actual graphs are grouped by status.
Complete Status | Select the statuses that are considered as complete status. If the run status of a test instance is one of the selected values, ALM treats the test instance as completed. Availability: Starting from 17.0.1, this option is available for both Planned vs. Actual (Test Run History) graphs and Planned vs. Actual (Last Test Run) graphs. Before 17.0.1, this option is available for Planned vs. Actual (Test Run History) graphs only.
Planned Line (Available in 17.0.1 and later) | Specify how ALM calculates the Plan line for the graph: Calculate Automatically (default). The Plan line shows the ideal test execution progress, assuming the same execution rate in each period. Calculate using Planned Exec Date. The Plan line shows the number of test instances whose Planned Exec Date falls within the specified period.

Back to top

## Configure test execution treemap graphs

The Test Execution Treemap graph type is available for Test Instances only. You can configure a test execution treemap using the following options:

Option | Description
--- | ---
Failed | Select the test instance statuses that are considered as failed statuses. For example, if you select Failed, Blocked, and Deferred, then tests of all these statuses are considered as failed tests.
Executed | Select the test instance statuses that are considered as executed statuses. When generating the graph, test instances of all selected failed statuses are considered as executed test instances, even when these statuses are not selected in the Executed field.
Filter | Use the Test Set: Test Set Folder filter to select the test set folder under which all the test sets are included in the treemap.

Back to top

## Configure test execution status trend graphs

The Test Execution Status Trend graph type is available for Tests only. You can configure a test execution status trend graph using the following options:

Option | Description
--- | ---
Period | See Period.
Resolution | See Resolution.
Grouped By | See Grouped.

Back to top

## Filter entities for a graph

You can use the Filter dialog box to filter entities to be included in a graph. This configuration is common to all types of graphs.

For details, see Filter dialog box.

Back to top

## Select projects for a graph

You can select multiple projects to be included in an entity graph. This configuration is common to all types of graphs.

Editions: Cross-project graphs are not available for Quality Center Enterprise Edition. For information about editions and their functionality, see Editions and lifecycle. To find out which edition you are using, ask your site administrator.

To select projects for a graph:

1. From the Analysis tree, select the graph and click the Configuration tab.

2. At the bottom of the page, click Select Projects.

3. From the Projects Tree list, select the target projects and click Add .

   - You can select only projects in which you are listed as a user.

   - If you selected a domain, all the domain's projects are added to the grid.

   - You can change the maximum number of projects that OpenText Application Quality Management allows you to include in a graph, by setting the PROJECT_SELECTION_MAX_PROJECTS site parameter. For details, see Set parameters at site level.

4. Click OK.

Back to top

See also:

- Entity graph types
- Generate an entity graph

https://admhelp.microfocus.com Application Quality Management 8942
Tips to improve your search results... OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help 26.1 All View Local Help Center View Online Help Center Version: