The available items depend on the widget you are configuring. Below are some common item types:

• Tests: Includes all subtypes of tests - manual tests, automated tests, Gherkin tests, BDD scenarios and test suites.

  For details on the testing frameworks and test types available in ALM Octane, see Testing overview and Manual testing flow.

• Work items: Includes common work items, such as epics, defects, features, user stories, and quality stories.

• Last test runs: Includes only the last runs of all the run types (manual run, automated run, suite run, Gherkin automated run). Popular use case: status and coverage analysis based on selected program, release, milestone, and environment.

  For details on how ALM Octane identifies runs as last runs see Run manual and Gherkin tests

• Backlog items: You can create a widget to show you the trends for Backlog items or Backlog's last test runs.

  For details on the testing frameworks and test types available in ALM Octane, see Backlog.

• Release processes, Release process items: You can create a widget to show DORA metrics and measure team performance. For details, see Release processes.

• Test run history (manual): Includes all manual runs of manual tests, Gherkin tests and BDD scenarios. Tracking manual run progress is a popular use case.

• Test run history (suites): Includes all suite runs. For details see Plan and run test suites.

• Pipeline run: Includes all pipeline runs that represent the builds of all root jobs that were defined as pipelines.

  For details see Automated testing flow.

The filter determines whether the widget is using global or custom widget settings:

• Global: Uses the settings defined in the dashboard's global context filter.

  In widgets with the Global filter setting, the Release, Sprint, Milestone, and Date Range fields are predefined with values set in the dashboard's global context filter.

  To override the global filter settings, change the filter to Local, and set values for this individual widget.

• Local: Lets you define the custom Release, Sprint, Milestone, and Date Range settings for this individual widget.

Note: If your widget includes more than one data set, you can set the Global/Local filter in one place for all existing data sets. You cannot apply different filters to a single widget.

If necessary, apply additional filters.

For example, if you only want to display defects that had a phase age of 60 days or more, add a Days in phase filter and specify Greater than 60.

Note: If you select more than one workspace in the Workspaces field, filters display the fields common to all selected workspaces. Certain reference fields (such as Application Modules or Features) are not available for use in cross-workspace graph filters.

If you update the workspaces that are selected or open the same graph in a different workspace, ALM Octane clears the existing filters.

For details, see Filters.

For trend-based graphs (Status Over Time), specify a time period.

• If a release is not specified, select one of the following:

  • All <items> up to now. The graph contains every item of the selected type from the beginning of your project until now.

  • Set period. Last week, two weeks, or month.

  • Custom period. Last xx days, weeks, or months, or Between specific dates.

• If a release is specified, select one of the following:

  • All <items> up to now. The graph includes the selected item type from the beginning of the specified release until now.

  • Release period. The graph includes the selected item type from the start date to the end date of the release.

  • Set period. Last week, two weeks or month.

  • Custom period. Last xx days, weeks, or months, or Between specific dates.

  • All <items> up to end of release. The graph includes items created or updated from the beginning of the project until the end of the release.

  • All <items> from start of release up to now. The graph includes items created or updated from the start date of the release until now.

For all graph types, a standard bar chart.

For summary graphs only, widget values are displayed in a stacked graph.

You can display a count, sum, average, or a ratio of the item's values.

For summary graphs, you can display multiple bar clusters within a single widget to compare results for different items, such as the number of features per team, separately for each release. You define two metrics, one for each cluster. For each metric, you specify the X and Y axis function and data set. By default, the Feature coverage widget uses this display type.

For trend-based graphs, you can create a vertical multi-bar graph, and sort the results by selected entities. By default, the Issue daily injection widget uses this display type.

For summary graphs only, the widget value as an integer.

You can choose to display a count, sum, average, or the ratio of the item's values.

To apply color coding to the number, enable the Use conditional color ranges option, and specify a range. For example, for a widget showing defects, you can designate red as the color for a count of 25 or more defects.

Line graph

A standard color-coded line graph displaying the field values.

For summary graphs, each graph source, such as defects or tests, has default columns defined, which you can change as needed.

• The grid limit is the maximum number of rows displayed, from 0 (no limit) to 100, by default 25 rows.
• When setting up a grid, you can select up to two fields for sorting. These fields correspond to the X-axis and Group by fields of graphs. If you select a field that cannot be used for sorting, a message appears in a tooltip next to the field name.
• On certain grids, depending on the source type, you can drill down into the grid rows to view full entity details.

Enterprise edition: Grid widgets can display cross-workspace information. For example, you can show the defects with highest severity from all workspaces in a shared space.

For summary widgets, this option shows data from features or application modules with no associated or assigned items.

In summary widgets based on date fields, this option adds columns for dates that have no data to display. For example, you can configure the widget to display Closed on date for defects. In this case, empty columns with no defects closed on that date will be displayed, in addition to the columns with data.

For trend-based widgets, this option counts all status changes in a given time frame—not just the final state of each entity. For example, if you want to see how many defects were opened and closed in each day, giving you a picture of the overall trend. You can use the Defect daily injection days/weeks graph to see how many defects were opened and closed by your team, over a two-week period.

Note: When aggregating by weeks, the number for each date on the graph represents how many records were at the end of the week that started on the start date.

For the bar and stacked bar displays, select this option to display widget values on the respective bars and their segments.

• Bar graphs: The total value per bar is displayed above the corresponding bar.

• Stacked bar graphs: The total value per bar is displayed above the corresponding bar. The value per bar segment is displayed in the corresponding segment.

  If a bar represents only one value that exceeds zero, only the total value above the bar is displayed. If a bar segment represents a low value, and the segment is too small to fit the number, the value is not displayed.

  For segment values, choose to display Actual values or the Percentage out of the total bar value.

Note:

• The Show values on chart option is not available for widgets that do not have the Display configuration tab, such as pipeline widgets.

• In summary widgets with the Average aggregation function, the total value above the bar is not displayed. The reason is that in this case, the total value would represent a sum of the section averages, which has no business value.

For a sum or an average of the X axis values, select a measuring unit, such as Estimated hours or Invested hours.

Only for summary widgets with more than one data set.

For example, you can configure separate data sets to display the following ratios:

• Fields ratio: The ratio between the count of an item's invested hours and story points in a release. In this example, the widget compares an item's fields of the same type, based on the same filter.
• Subsets ratio: The ratio between the count of critical defects and a general number of defects in a release. In this example, the widget compares the same item type based on a different filter.
• Sets ratio: The ratio between the percentage of escaped defects and automation tests per application module. In this example, the widget compares different item types, based on a different filter.

To display a ratio, select the data sets whose values you need to compare:

• Numerator: Display the count, sum, or average of the items defined in Data set 1.
• Denominator: Display the count, sum, or average of the items defined in Data set 2.

Note:

• The fields you define for a numerator and denominator should be of the same type. When you define either a numerator or denominator, the other field adjusts accordingly and lists only the fields of the same type.
• The ratio function supports only a stacked, number, and a tabular display types.