The

Secure Alerts

graphic displays data graphs that allow for a more in-depth understanding of the severity trend chart and the discovery of application vulnerabilities. This display presents the total amount of

Open,

Dismissed

, and

Closed

alerts; it shows the name of the most recently opened alert when it was opened, from what application, and the number of critical, high, medium, and low alerts.

The

DevOps Performance metrics

graphic displays data in the form of tiles displaying four metrics,

Deployment frequency

,

Change lead time

,

Change failure rate

, and

Mean time to recovery

for a minimum duration of 30 days.

The

Security posture

graphic presents a summary in the form of a donut graph that shows the total number of

Open security defects

per severity classification (Critical, High, Medium, Low, and Info). You can view the data for each severity by selecting the check boxes at the bottom of the graph.

Hovering over the graph, a given color corresponding to a severity category displays the total number of severities found for that severity category. Also, the graph displays the percentage for each severity category out of the total severities found.

The

Develop

graphic presents a summary in the form of a heat map that shows the commits performed in the selected period, providing the total count of

Commits

and

Contributors

. The display also indicates the

Source tool

from which the data collected. The Develop dashboard, provides the pattern of developer commits on a daily basis. As an example, it might show that developers were most active on 8th August followed by 7th August, but there are no commits on 9th August, which is a Friday, from which you ight infer that Fridays are light commit days because of developer work budget or schedule. Such insights can help managers to understand developer behavior and identify process gaps.

The Develop graphic displays a heat map showing the Commits performed daily. Hovering over the heat map lets you view the exact amount of Commits per day.

The

Issues and defects

graphic gives you insight as to the efficacy of your planning activity. It provides a glimpse of trends regarding issues and defects based on the selection of duration. The graphic maps bugs to software

Defects

and other work items like featuresand user stories are mapped to

Issues

, providing insight to open defects for all applications, how quickly the team is able to resolve bugs and whether the number of bugs are increasing. The graphic shows the total number of open

Issues

(brown) and

Defects

(aqua blue).

The

Test

graphic offers a view of the end result of both unit and functional tests. A critical function for QA managers is to improve the code quality of applications. A trend of passed tests suggest high code quality, whereas a trend of failed tests, suggests a close inspection of the Test module. The grpresents the total count of

All tests

as well as a summary in the form of a graph showing tests per day (data shown is for the last 8 days). The following statuses are reported:

Total:
Total number of tests from both categories.
Failed:
Total number of of Failed test cases
Passed:
Total number of Passed test cases.
Skipped:
Total number of Skipped test cases.
Blocked:
Total number of test cases the team could not perform because they were prevented from running it.

The graphic provides a filter for test type including Unit tests, Functional tests, Other tests and All tests (default).

The

Build

graphic presents a summary in the form of a graph that shows the

Passed

and

Failed

Builds within a determined period. The bar graph allows you to switch between Failed and Passed builds to show data by selecting the checkboxes at the bottom of it. Hovering over the bars in the graph in a specific color corresponding to a given build category displays the following information:

Build date
Total passed
Total failed
Total builds, fast and failed