Helps you monitor bug reports occurring during your teams' software development processes.
The Oobeya Bug Report module helps you track bug records occurring during your teams' software development processes by collecting data from project management tools such as Jira and Azure Boards. It provides organization and team-level visibility into open and closed bugs. This empowers you to make data-driven decisions that improve software quality and detect bottlenecks at an early stage.
Key Features
Centralized reporting view across the entire organization
Team-level filtering and analysis
Multiple time interval views (daily, weekly, monthly, quarterly)
Visualizations of open bug trends
Severity distribution analysis
Bug distribution by team
Detailed bug list: Team Bugs, Unassigned Bugs, Other Teams' Bugs (Work item, Assignee, Project, Status, etc.)
Prerequisites (Admin Settings)
To ensure the Bug Report module functions correctly, certain configurations must be completed in the Admin Panel.
1. Category Mapping Settings
Under Administration > AgileSpace, define the relevant issue types (e.g., Bug, Defect, Problem, Incident, Error) mapped to the Bug Fixing category.
If this mapping is not configured, related work items will not be classified as bugs and won't be reflected in the report.
Category Mapping
2. Severity Mapping
To classify bugs by severity level, map the severity fields from Jira or Azure Boards to Oobeya’s predefined severity categories.
For Jira: Map values from the Priority field such as Highest, High, Medium, Low, etc.
For Azure: Use numeric values sorted by criticality (e.g., 1 - Critical, 2 - High, etc.)
Changes in these settings will trigger a reanalysis of historical data.
Severity Mapping
Dashboard Components
1. Open Bugs Over Time
Displays the trend of open bugs over time, broken down by severity levels (Blocker, Critical, High, Medium, Low).
Interactive chart: Hover to view detailed counts of bugs per severity for each time interval.
Time filter options: Choose from Last 7 Days, Last 30 Days, Monthly, Quarterly, or custom date ranges.
Open Bugs Over Time
2. Bug Severity Summary
Displays the distribution of bugs by severity level.
Bug Severity
3. Bug Distribution by Team
Displays the number of bugs per team and helps identify which teams are reporting the most bugs.
Pie chart visualization
Quick identification of high-volume bug teams
Bug Distribution By Team
4. Bug Details
Displays a full list of bugs, including:
Work item ID
Summary
Assignee
Project and Team
Type, Severity, Status, and Date fields
Bug Details Table
FAQ (Frequently Asked Questions)
Is this module available to all users?
Yes. The Bug Report Dashboard is available organization-wide. Users can filter results based on the teams to which they belong.
Why are severity levels not showing correctly?
Please verify your severity mapping settings in the Admin Panel. The fields in Jira or Azure Boards might not be correctly matched to Oobeya's categories.
Why is the bug count different from what's shown in Jira or Azure?
This might be due to incorrect category mapping or excluded work item types in your configuration.
Conclusion
The Bug Report module is a powerful tool for teams aiming to streamline issue tracking and improve software quality. When properly configured, it enables clear visibility into bug volume, resolution trends, and risk zones.
