> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/using-hivel/coding-hotspots.md).

# Coding Hotspots

### **What is Coding Hotspots?**

Coding Hotspots feature helps engineering teams identify areas in the codebase that frequently experience bugs. By analyzing **JIRA issues, pull requests (PRs),** and **commit history**, it pinpoints files that are most often modified due to bug fixes. This enables teams to focus on problem areas, improve code stability, and enhance development efficiency.

<div data-with-frame="true"><figure><img src="/files/nc9g0P4hdBjB74cUx7Qs" alt=""><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="/files/qN5cRY4SdVJEi8MGeJDd" alt=""><figcaption></figcaption></figure></div>

### **How It Works**

1. **JIRA Issue & PR Tracking**
   * Links JIRA issues with their associated PRs and commits.
   * Categorizes commits based on related bug fixes.
2. **Repository & File Analysis**
   * Identifies frequently modified files within repositories.
   * Tracks how often each file appears in bug-related commits.
   * Provides insights into the most problematic files.
3. **Enhanced Data Tracking**
   * Shows assignees fixing issues.
   * Lists recent contributors and reviewers for each file.

### How to Use Coding Hotspots

* View repositories with the highest bug-related modifications.
* Drill down into specific files to analyze patterns.

#### Drill-Down Levels

1. **Level 1 (Repositories Overview):**
   * View repositories with frequent bug-related file changes.
2. **Level 2 (File-Level Analysis):**
   * See which files are modified most often, who worked on them, and their issue/PR count.
3. **Level 3 (Issue & PR Breakdown):**
   * View related JIRA issues, PRs, assignees, and contributors.
4. **Filters & Sorting**
   * Filter data by repository, time period (default: last 30 days), and issue type (default: Bug).
   * Customize views to focus on relevant problem areas.

### Key Insights

* Identify Problematic Code Areas: Quickly find files frequently associated with bugs.
* Track Developer Activity: See who contributes and reviews bug fixes.
* Improve Code Quality: Address recurring issues proactively.
* Optimize Workflows: Understand patterns and trends in bug-related modifications.