Diagnose delivery issues
The Diagnostic view in the Unified Quality Dashboard (UQD) helps teams investigate delivery slowdowns, workflow bottlenecks, and engineering signals across SHIP-HATS systems.
Use this view after detecting unusual trends in the Operational view, such as declining deployment cadence or slower development workflows.
Before you begin
Ensure that:
- You can access the Unified Quality Dashboard (UQD).
- The relevant systems and projects are correctly tagged and configured.
See:
Open the Diagnostic view
- Log in to the Console.
- Open Unified Quality Dashboard (UQD).
- Select the Diagnostic tab.
The dashboard displays detailed signals related to development workflow, CI/CD performance, deployment lead time, and system quality.
Filter the data
Use the Controls panel to narrow the dataset.
You can filter by:
| Filter | Purpose |
|---|---|
| Last N Months | Adjust the time range for the analysis. |
| Agency | View metrics for a specific agency. |
| DGP Subsystem | Focus on a specific subsystem. |
| Jira Project | Investigate a particular project. |
| GitLab Group Path | Analyse repositories within a specific GitLab group. |
Filtering allows teams to isolate issues affecting a specific system, project, or time period.
Analyse deployment performance
Review the Production Deployment Performance and Production Deployment Change Performance sections.
Look for:
- Reduced number of production deployments
- Increased deployment change lead time
These signals may indicate delays in moving changes from development to production.
Investigate development workflow efficiency
Use the Merged MR Performance section to analyse development throughput.
Key indicators include:
- Merged MR cycle time — longer times may indicate review delays or development bottlenecks.
- Number of merged MRs — declining throughput may signal reduced development activity.
These metrics help identify friction in the code review or merge process.
Review CI/CD pipeline performance
Examine the CI/CD Pipeline Performance section to evaluate pipeline stability.
Look for:
- Increased MR pipeline duration
- Longer fast pipeline duration
- Pipeline flakiness or instability
Pipeline issues may delay code validation and slow down delivery.
Assess process, code, and system quality
Use the following sections to identify additional factors affecting delivery performance:
| Section | What to review |
|---|---|
| Process Quality | User story acceptance rate and DevSecOps maturity indicators. |
| Code Quality | Open vulnerabilities or functional bugs detected during development. |
| System Quality | Bugs identified in production or UAT environments. |
These indicators help determine whether quality or process issues are affecting delivery flow.
Result
After analysing the Diagnostic view, you can:
- Identify workflow bottlenecks
- Detect pipeline or deployment delays
- Understand quality signals affecting delivery performance
- Determine areas that require process or engineering improvements
Once improvements are implemented, return to the Operational view to confirm that deployment cadence and delivery trends have improved.
