How to Use Reports in Cubyts?

Introduction

This guide explains how to use Reports in the Cubyts platform to trace the journey of work and code across the SDLC. Reports help you move from high-level execution signals to detailed, data-backed insights across teams, delivery flow, code, and audits—enabling informed, root-cause-driven decision-making.

Prerequisites

• Access to a Cubyts workspace

• Permission to view reports

• Integrated SDLC tools (for delivery and code context)

Step-by-Step Guide

Step 1: Understand Report Categories

Reports in Cubyts are organized into four categories, each focused on a different aspect of execution:

• Team Reports – Ownership and people-centric insights

• Delivery Reports – Execution flow and delivery progress

• Code Reports – State and movement of code

• Audit Reports – Traceability, governance, and deviations

This structure helps you quickly navigate to the right report based on what you want to analyze.

Step 2: Use Team Reports to Analyze Ownership

Team reports focus on how work items, branches, and pull requests are distributed across team members.

Example: Pull Requests (PR) and Branch Assignments Report

• Open the PR Report under Team Reports.

• Use the filter at the top to view assignments:

  • With flags

  • Without flags

• The list groups data by individual team members and shows:

  • Contributing peers

  • Total flags

  • Recurring flags

  • Average age of peers

This view helps identify ownership patterns, workload distribution, and areas that may need attention.

Step 3: Deep Dive into Individual Contributions

• Select a team member to open the detailed view on the right-hand side.

• The Overview tab provides a consolidated snapshot including:

  • Total flags

  • Flag distribution by category

  • Associated repositories

  • Pull request breakdown

Switch to the Insights tab to view:

• Performance trends over time (e.g., PR age trends)

• Flag distribution across multiple categories

These trends help determine whether contributor performance is improving, stagnating, or deteriorating.

Step 4: Use Delivery Reports to Track Execution Flow

Delivery reports focus on feature progress, work item status, and sprint execution.

Example: Work Item Status Report

• Navigate to the Work Item Status Report under Delivery Reports.

• The delivery hierarchy depends on the planning tool integrated with your workspace, such as Jira or Azure Boards.

• While hierarchies may vary, reporting patterns remain consistent.

This report shows:

• All work items and their current execution state

• Filters for flagged vs. non-flagged work items

• A distribution bar summarizing execution status

Step 5: Analyze Work Item Details

In the list view, each work item displays:

• Status and type

• Total flags

• Active sprint flags

• Recurring flags

• Associated branches

Selecting a work item opens a detailed panel showing:

• Sprint and feature associations

• Delivery status

• Cycle time indicators

• Process flags

• Time spent in each status

• Planning metadata

This allows teams to investigate issues deeply without leaving the report.

Step 6: Explore Code and Audit Reports

• Code Reports focus on repositories, branches, pull requests, and code reviews, helping you understand how code evolves through the SDLC.
  
  

• Audit Reports capture traceability and deviations, supporting governance, compliance, and audit readiness.

Together, these reports provide a complete picture of execution from both delivery and code perspectives.

Step 7: Use Common Report Capabilities

Across all report types in Cubyts, you can:

• Adjust the time range to analyze specific periods

• Apply report-specific filters

• Customize columns (user-specific)

• Search to quickly locate relevant data

• Export reports as CSV

• Use pagination to navigate large datasets

These consistent controls ensure a unified reporting experience.

How Health and Reports Work Together

• Health acts as the signal layer, highlighting what needs attention across portfolios, EPICs, sprints, repositories, or teams.

• Reports allow you to investigate those signals in depth by tracing issues across people, work items, and code.
  
  

This seamless transition from health to reports enables faster root-cause analysis and better decision-making.

Conclusion

Reports in Cubyts provide deep visibility into execution from multiple perspectives—teams, delivery flow, work items, code, and audits. With consistent structure, powerful filters, and tight integration with health insights, reports help you understand not just what needs attention, but why—by tracing the journey of work and code across the SDLC.

Video link: https://www.loom.com/share/f49a0d80e5374dfbbdbe10905fa32ca6