# Table of Contents - [Welcome to Hivel | Hivel](#welcome-to-hivel-hivel) - [Welcome to Hivel | Welcome Packet | Hivel](#welcome-to-hivel-welcome-packet-hivel) - [Integrating Your Tools | Welcome Packet | Hivel](#integrating-your-tools-welcome-packet-hivel) - [KPIs in Hivel | Welcome Packet | Hivel](#kpis-in-hivel-welcome-packet-hivel) - [Understanding and Selecting KPIs | Welcome Packet | Hivel](#understanding-and-selecting-kpis-welcome-packet-hivel) - [Reviewing and Adjusting KPIs | Welcome Packet | Hivel](#reviewing-and-adjusting-kpis-welcome-packet-hivel) - [Configuring KPIs in Hivel | Welcome Packet | Hivel](#configuring-kpis-in-hivel-welcome-packet-hivel) - [Best Practices for Effective KPI Management | Welcome Packet | Hivel](#best-practices-for-effective-kpi-management-welcome-packet-hivel) - [Monitoring and Tracking KPIs | Welcome Packet | Hivel](#monitoring-and-tracking-kpis-welcome-packet-hivel) - [Issue Age | Hivel](#issue-age-hivel) - [How to download reports | Hivel](#how-to-download-reports-hivel) - [How to add Custom fields for Product and Allocation Label in Jira | Hivel](#how-to-add-custom-fields-for-product-and-allocation-label-in-jira-hivel) - [Using Hivel | Hivel](#using-hivel-hivel) - [Meetings Breakdown | Hivel](#meetings-breakdown-hivel) - [Pull Request | Hivel](#pull-request-hivel) - [How to set up Products & Allocation tabs in the Investment Screen? | Hivel](#how-to-set-up-products-allocation-tabs-in-the-investment-screen-hivel) - [Cockpit | Hivel](#cockpit-hivel) - [Metrics & Definitions | Hivel](#metrics-definitions-hivel) - [How to exclude outlier commits and PRs? | Hivel](#how-to-exclude-outlier-commits-and-prs-hivel) - [Process | Hivel](#process-hivel) - [Review Cycles | Hivel](#review-cycles-hivel) - [Investment | Hivel](#investment-hivel) - [Comments Categorization | Hivel](#comments-categorization-hivel) - [Coding | Hivel](#coding-hivel) - [How are Active Days calculated | Hivel](#how-are-active-days-calculated-hivel) - [Best Practices | Hivel](#best-practices-hivel) - [Dev360 | Hivel](#dev360-hivel) - [AI Adoption | Hivel](#ai-adoption-hivel) - [Goals | Hivel](#goals-hivel) - [Release Merge Frequency | Hivel](#release-merge-frequency-hivel) - [Pickup time | Hivel](#pickup-time-hivel) - [Coding Time | Hivel](#coding-time-hivel) - [Speed | Hivel](#speed-hivel) - [Review Time | Hivel](#review-time-hivel) - [New Work% | Hivel](#new-work-hivel) - [PRs Open, PRs Ready to Review or Merge | Hivel](#prs-open-prs-ready-to-review-or-merge-hivel) - [Best Practices for Software Development Efficiency | Hivel](#best-practices-for-software-development-efficiency-hivel) - [Throughput | Hivel](#throughput-hivel) - [Team Pulse | Hivel](#team-pulse-hivel) - [Configurations | Hivel](#configurations-hivel) - [Set Up | Hivel](#set-up-hivel) - [GitHub Copilot: Expanded Metrics Guide | Hivel](#github-copilot-expanded-metrics-guide-hivel) - [Copilot Adoption | Hivel](#copilot-adoption-hivel) - [Hivel AI Impact Screen: Overview & Insights | Hivel](#hivel-ai-impact-screen-overview-insights-hivel) - [Understanding Rework, New Work, and Maintenance | Hivel](#understanding-rework-new-work-and-maintenance-hivel) - [Work Item Breakdown | Hivel](#work-item-breakdown-hivel) - [Performance Appraisal | Hivel](#performance-appraisal-hivel) - [Hotfix Rate | Hivel](#hotfix-rate-hivel) - [PRs > 400 LoC | Hivel](#prs-400-loc-hivel) - [Sign Up | Hivel](#sign-up-hivel) - [Cycle Time | Hivel](#cycle-time-hivel) - [Flashy Reviews | Hivel](#flashy-reviews-hivel) - [Branch Configurations | Hivel](#branch-configurations-hivel) - [Maintenance | Hivel](#maintenance-hivel) - [Repositories | Hivel](#repositories-hivel) - [Quality | Hivel](#quality-hivel) - [Hotfix Resolution Time | Hivel](#hotfix-resolution-time-hivel) - [Merge Time | Hivel](#merge-time-hivel) - [Track hotfixes via patch version pattern | Hivel](#track-hotfixes-via-patch-version-pattern-hivel) - [Rework | Hivel](#rework-hivel) - [Hotfix Configurations | Hivel](#hotfix-configurations-hivel) - [General Configurations | Hivel](#general-configurations-hivel) - [Best practices for adopting Story Points | Hivel](#best-practices-for-adopting-story-points-hivel) - [Investment Configurations | Hivel](#investment-configurations-hivel) - [Exclusions | Hivel](#exclusions-hivel) - [Coding Hotspots | Hivel](#coding-hotspots-hivel) - [Unreviewed PRs | Hivel](#unreviewed-prs-hivel) - [PR Reviewed | Hivel](#pr-reviewed-hivel) - [How to sign up to Hivel? | Hivel](#how-to-sign-up-to-hivel-hivel) - [Code Telemetry FAQs | Hivel](#code-telemetry-faqs-hivel) - [Hotfix & Jira Integration - Best Practices | Hivel](#hotfix-jira-integration-best-practices-hivel) - [Enabling Hivel's AI-Powered Features | Hivel](#enabling-hivel-s-ai-powered-features-hivel) - [Jira Best Practices | Hivel](#jira-best-practices-hivel) - [Setting Up Slack to Receive Hivel Alerts | Hivel](#setting-up-slack-to-receive-hivel-alerts-hivel) - [Hivel Score | Hivel](#hivel-score-hivel) - [AI usage - PR checklist + Prompt Cookbook + Cursor Rules | Hivel](#ai-usage-pr-checklist-prompt-cookbook-cursor-rules-hivel) - [Org level Hivel Score Calculation | Hivel](#org-level-hivel-score-calculation-hivel) - [Metric Behaviour | Hivel](#metric-behaviour-hivel) - [Cursor: Expanded Metrics Guide | Hivel](#cursor-expanded-metrics-guide-hivel) - [Lucy | Hivel](#lucy-hivel) - [How to update the name of an user? | Hivel](#how-to-update-the-name-of-an-user-hivel) - [How to Encourage Jira Hygiene Without Creating Friction | Hivel](#how-to-encourage-jira-hygiene-without-creating-friction-hivel) - [Alerts in Hivel | Hivel](#alerts-in-hivel-hivel) - [Users | Hivel](#users-hivel) - [How to archive users? | Hivel](#how-to-archive-users-hivel) - [Team Versioning | Hivel](#team-versioning-hivel) - [Team level Hivel Score Calculation | Hivel](#team-level-hivel-score-calculation-hivel) - [Teams | Hivel](#teams-hivel) - [How to add or update an user's email id? | Hivel](#how-to-add-or-update-an-user-s-email-id-hivel) - [Cursor Adoption | Hivel](#cursor-adoption-hivel) - [How to merge users? | Hivel](#how-to-merge-users-hivel) - [Can I see the data of a user or repo that I don’t have access to on my SCM tool? | Hivel](#can-i-see-the-data-of-a-user-or-repo-that-i-don-t-have-access-to-on-my-scm-tool-hivel) - [How to create teams? | Hivel](#how-to-create-teams-hivel) - [How to modify a team? | Hivel](#how-to-modify-a-team-hivel) - [Access Management | Hivel](#access-management-hivel) - [Leader's Guide to Engineering Metrics | Hivel](#leader-s-guide-to-engineering-metrics-hivel) - [Labels | Hivel](#labels-hivel) - [Use Cases | Hivel](#use-cases-hivel) - [How to invite more users to use Hivel? | Hivel](#how-to-invite-more-users-to-use-hivel-hivel) - [How to delete a team? | Hivel](#how-to-delete-a-team-hivel) - [How to create sub-teams? | Hivel](#how-to-create-sub-teams-hivel) - [Marco - Code Review Tool | Hivel](#marco-code-review-tool-hivel) - [How to remove users from a team or sub-team? | Hivel](#how-to-remove-users-from-a-team-or-sub-team-hivel) - [How to add users to a team and sub-team? | Hivel](#how-to-add-users-to-a-team-and-sub-team-hivel) - [SCM | Hivel](#scm-hivel) - [Improve Performance | Hivel](#improve-performance-hivel) - [Best practices for AI usage | Hivel](#best-practices-for-ai-usage-hivel) - [Developer's Guide to Hivel | Hivel](#developer-s-guide-to-hivel-hivel) - [What are the impacts of context switching on developer productivity and how to reduce it? | Hivel](#what-are-the-impacts-of-context-switching-on-developer-productivity-and-how-to-reduce-it-hivel) - [How to balance speed and quality? | Hivel](#how-to-balance-speed-and-quality-hivel) - [Why does the filters change when I move to dashboards but in other screen it remains same? | Hivel](#why-does-the-filters-change-when-i-move-to-dashboards-but-in-other-screen-it-remains-same-hivel) - [System Behavior & Limitations FAQs | Hivel](#system-behavior-limitations-faqs-hivel) - [How to improve planning and throughput | Hivel](#how-to-improve-planning-and-throughput-hivel) - [Azure AD SSO | Hivel](#azure-ad-sso-hivel) - [FAQs | Hivel](#faqs-hivel) - [Why am I not able to select more than 6 months at a time? | Hivel](#why-am-i-not-able-to-select-more-than-6-months-at-a-time-hivel) - [Project Management | Hivel](#project-management-hivel) - [Team & User Management FAQs | Hivel](#team-user-management-faqs-hivel) - [Google Calendar | Hivel](#google-calendar-hivel) - [How to improve Speed? | Hivel](#how-to-improve-speed-hivel) - [How can I see the progress against my goals? | Hivel](#how-can-i-see-the-progress-against-my-goals-hivel) - [Calendar | Hivel](#calendar-hivel) - [What to do if my Coding Time is high? | Hivel](#what-to-do-if-my-coding-time-is-high-hivel) - [What metrics can I use to prevent developer burnout? | Hivel](#what-metrics-can-i-use-to-prevent-developer-burnout-hivel) - [What to do if my Merge Time is high? | Hivel](#what-to-do-if-my-merge-time-is-high-hivel) - [How to track, manage, and reduce technical debt? | Hivel](#how-to-track-manage-and-reduce-technical-debt-hivel) - [How to Use Hivel Support | Hivel](#how-to-use-hivel-support-hivel) - [How to mark leaves & absences? | Hivel](#how-to-mark-leaves-absences-hivel) - [CI/CD | Hivel](#ci-cd-hivel) - [Why can't I remove a user from a team? | Hivel](#why-can-t-i-remove-a-user-from-a-team-hivel) - [Leveraging data for more effective sprint planning | Hivel](#leveraging-data-for-more-effective-sprint-planning-hivel) - [How to build a data-driven culture of Engineering? | Hivel](#how-to-build-a-data-driven-culture-of-engineering-hivel) - [Marco - Code Review Agent | Hivel](#marco-code-review-agent-hivel) - [How to integrate Google Calendar in Hivel | Hivel](#how-to-integrate-google-calendar-in-hivel-hivel) - [How to change a team owner? | Hivel](#how-to-change-a-team-owner-hivel) - [Azure | Hivel](#azure-hivel) - [What to do if my Review Time is high? | Hivel](#what-to-do-if-my-review-time-is-high-hivel) - [Why do I see "No existing user found" message while login | Hivel](#why-do-i-see-no-existing-user-found-message-while-login-hivel) - [BitBucket | Hivel](#bitbucket-hivel) - [Jira | Hivel](#jira-hivel) - [Azure Boards | Hivel](#azure-boards-hivel) - [API Documentation | Hivel](#api-documentation-hivel) - [Gitlab | Hivel](#gitlab-hivel) - [How to ensure Gitlab token has access to required groups/repositories | Hivel](#how-to-ensure-gitlab-token-has-access-to-required-groups-repositories-hivel) - [PR, Issues & Workflow FAQs | Hivel](#pr-issues-workflow-faqs-hivel) - [Microsoft Outlook | Hivel](#microsoft-outlook-hivel) - [What happens if there are too many Flashy Reviews and how to prevent them? | Hivel](#what-happens-if-there-are-too-many-flashy-reviews-and-how-to-prevent-them-hivel) - [Why Product and Allocation's previous data is not reflecting? | Hivel](#why-product-and-allocation-s-previous-data-is-not-reflecting-hivel) - [Reporting & Goal Tracking FAQs | Hivel](#reporting-goal-tracking-faqs-hivel) - [Release Notes - December 2024 | Hivel](#release-notes-december-2024-hivel) - [AI Tools | Hivel](#ai-tools-hivel) - [BitBucket Integration | Hivel](#bitbucket-integration-hivel) - [How to Re-authorize Jira with OAuth 2.0 | Hivel](#how-to-re-authorize-jira-with-oauth-2-0-hivel) - [Azure DevOps | Hivel](#azure-devops-hivel) - [How to identify root cases of high change failure rates? | Hivel](#how-to-identify-root-cases-of-high-change-failure-rates-hivel) - [Okta SSO | Hivel](#okta-sso-hivel) - [GitHub | Hivel](#github-hivel) - [Setting up your own key for AI features | Hivel](#setting-up-your-own-key-for-ai-features-hivel) - [Cursor Integration | Hivel](#cursor-integration-hivel) - [How to improve Quality | Hivel](#how-to-improve-quality-hivel) - [Building a feedback loop for continuous code improvement | Hivel](#building-a-feedback-loop-for-continuous-code-improvement-hivel) - [How to Integrate Jira with OAuth 2.0 | Hivel](#how-to-integrate-jira-with-oauth-2-0-hivel) - [Azure GIT Server | Hivel](#azure-git-server-hivel) - [Release Notes - July 2025 | Hivel](#release-notes-july-2025-hivel) - [How do I exclude a PR from rework/maintenance/new work calculation? | Hivel](#how-do-i-exclude-a-pr-from-rework-maintenance-new-work-calculation-hivel) - [Alternate methods | Hivel](#alternate-methods-hivel) - [What to do if my Rework is high? | Hivel](#what-to-do-if-my-rework-is-high-hivel) - [Why don't I see delivery accuracy for Kanban boards? | Hivel](#why-don-t-i-see-delivery-accuracy-for-kanban-boards-hivel) - [Slack Integration with Hivel | Hivel](#slack-integration-with-hivel-hivel) - [Release Notes | Hivel](#release-notes-hivel) - [Why do some Jira issues show as spillover in Hivel even though they were completed in Jira? | Hivel](#why-do-some-jira-issues-show-as-spillover-in-hivel-even-though-they-were-completed-in-jira-hivel) - [Easing into Kanban: How to set your team up for success | Hivel](#easing-into-kanban-how-to-set-your-team-up-for-success-hivel) - [What to do if my Cycle Time is high? | Hivel](#what-to-do-if-my-cycle-time-is-high-hivel) - [Claude Code | Hivel](#claude-code-hivel) - [On-Prem Setup | Hivel](#on-prem-setup-hivel) - [Gitlab Server | Hivel](#gitlab-server-hivel) - [Github Copilot Integration | Hivel](#github-copilot-integration-hivel) - [Why some of the repositories are not imported or synced? | Hivel](#why-some-of-the-repositories-are-not-imported-or-synced-hivel) - [Release Notes - January 2025 | Hivel](#release-notes-january-2025-hivel) - [Release Notes - March 2025 | Hivel](#release-notes-march-2025-hivel) - [How can I add a template in dashboards for my org to follow? | Hivel](#how-can-i-add-a-template-in-dashboards-for-my-org-to-follow-hivel) - [Gitlab Cloud | Hivel](#gitlab-cloud-hivel) - [DORA Metrics Powered by New APIs in Hivel | Hivel](#dora-metrics-powered-by-new-apis-in-hivel-hivel) - [How to integrate GitHub with account wide access? | Hivel](#how-to-integrate-github-with-account-wide-access-hivel) - [How to integrate GitHub with repository level access? | Hivel](#how-to-integrate-github-with-repository-level-access-hivel) - [Release Notes - October 2025 | Hivel](#release-notes-october-2025-hivel) - [Strategies to Reduce Hotfix Resolution Time | Hivel](#strategies-to-reduce-hotfix-resolution-time-hivel) - [How to re-authorize / re-initiate GitHub integration with repository level access? | Hivel](#how-to-re-authorize-re-initiate-github-integration-with-repository-level-access-hivel) - [How to re-authorize / re-initiate GitHub integration with account wide access? | Hivel](#how-to-re-authorize-re-initiate-github-integration-with-account-wide-access-hivel) - [How to integrate Jira Server with Hivel | Hivel](#how-to-integrate-jira-server-with-hivel-hivel) - [Release Notes - February 2025 | Hivel](#release-notes-february-2025-hivel) - [Best Practices for Team Ownership in Code Review | Hivel](#best-practices-for-team-ownership-in-code-review-hivel) - [Create Incident API | Hivel](#create-incident-api-hivel) - [ClickUp | Hivel](#clickup-hivel) - [Best Practices for Ensuring Strong Pull Request Review Coverage | Hivel](#best-practices-for-ensuring-strong-pull-request-review-coverage-hivel) - [Release Notes - October 2024 | Hivel](#release-notes-october-2024-hivel) - [Jira On-Prem | Hivel](#jira-on-prem-hivel) - [Release Notes - September 2025 | Hivel](#release-notes-september-2025-hivel) - [Release Notes - August 2025 | Hivel](#release-notes-august-2025-hivel) - [Release Notes - November 2024 | Hivel](#release-notes-november-2024-hivel) - [How to reauthorize Github with a classic token? | Hivel](#how-to-reauthorize-github-with-a-classic-token-hivel) - [Creating a Bitbucket App Password | Hivel](#creating-a-bitbucket-app-password-hivel) - [Gitlab On-Prem | Hivel](#gitlab-on-prem-hivel) - [SonarQube On-Prem | Hivel](#sonarqube-on-prem-hivel) - [Validation at a metric level for BitBucket | Hivel](#validation-at-a-metric-level-for-bitbucket-hivel) - [Release Notes - April 2025 | Hivel](#release-notes-april-2025-hivel) - [On-Prem Installation Guide | Hivel](#on-prem-installation-guide-hivel) - [How to create Github fine-grained token for Hivel Integration? | Hivel](#how-to-create-github-fine-grained-token-for-hivel-integration-hivel) --- # Welcome to Hivel | Hivel ![Page cover](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FluolO7UltYX0kNgpsuMe%252FSPEED%2520%281%29.jpg%3Falt%3Dmedia%26token%3D743a7009-c92b-40ec-929d-74785603c7ff&width=1248&dpr=3&quality=100&sign=9740759e&sv=2) Hivel is an intelligence platform providing Software Engineering Leaders with **actionable insights** from Dev Tools, empowering them to unlock their organization's full potential. These insights empower **hi**gh-**vel**ocity teams, and **boost business impact**. [](https://docs.hivel.ai/using-hivel) ![Cover](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F7Knv1k3uVOkkmCifn5DT%252FMain%2520Features.jpg%3Falt%3Dmedia%26token%3D25889f43-ba53-429c-8cd4-926f345aaf7f&width=490&dpr=3&quality=100&sign=b669b5a0&sv=2) **Using Hivel** _know the ins and outs of Hivel's main features_ [](https://docs.hivel.ai/metrics-and-definitions) ![Cover](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FASu9uq9DW1SCf7Rk80zO%252FMetrics%2520%2526%2520Def.jpg%3Falt%3Dmedia%26token%3D70271fb5-0d3b-4a90-976c-634a32ec4d0c&width=490&dpr=3&quality=100&sign=985d0268&sv=2) **Metrics & Definitions** _dive deep into the metrics_ [](https://docs.hivel.ai/set-up) ![Cover](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FiE1GM9AU5lHTiL6LqsPt%252FSetUp.png%3Falt%3Dmedia%26token%3Da756a0ac-f521-4b1c-939d-5ed307743cd3&width=490&dpr=3&quality=100&sign=91141399&sv=2) **Setup** _configure Hivel to match your workflow_ [](https://docs.hivel.ai/integrations) ![Cover](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F1rTYhGCJP5hP3frMH0k1%252FIntegration%2520%281%29.png%3Falt%3Dmedia%26token%3Df319589b-917b-4483-92d3-156f95922630&width=490&dpr=3&quality=100&sign=3b5aad9c&sv=2) **Integrations** _connect with the most widely used tools and derive correlation_ [](https://docs.hivel.ai/best-practices) ![Cover](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FyrmhizmTt3hcdVWJ73jN%252FThroughput%2520%281%29.jpg%3Falt%3Dmedia%26token%3D16742404-8b8f-404f-8011-2a290d3c937d&width=490&dpr=3&quality=100&sign=9ad1dae6&sv=2) **Best Practices** _keep up with the latest industry trends_ [](https://docs.hivel.ai/ai-adoption) ![Cover](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fe71PRtbRZY4rMtvk8Hxq%252FSpeed%2520%282%29.jpg%3Falt%3Dmedia%26token%3D643819a6-ae27-4231-b317-ec0d69eb2927&width=490&dpr=3&quality=100&sign=1219805b&sv=2) **AI Adoption** _Measure you AI adoption & usage_ Last updated 2 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Welcome to Hivel | Welcome Packet | Hivel ![Page cover](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F1678521024-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FxFR2Rv2DoZlYsSKT7aaT%252Fuploads%252FQ6FnCOkJ3NZBL0FQ8T3p%252Fhivel%2520rocket.jpeg%3Falt%3Dmedia%26token%3Dbc7b2f98-3aa7-45ca-9dcc-371be57dbae1&width=1248&dpr=3&quality=100&sign=4e8047fb&sv=2) Hivel is an intelligence platform providing Software Engineering Leaders with **actionable insights** from Dev Tools, empowering them to unlock their organization's full potential. These insights empower **hi**gh-**vel**ocity teams, and **boost business impact**. This packet contains the following topics: 1. Signing up to Hivel 2. Inviting team members to start using Hivel 3. Integrating Hivel with all dev tools you use 4. Best Practices for efficient Software Development 5. Setting and monitoring KPIs in Hivel 6. Case studies on the results customer's have seen with Hivel [NextIntegrating Your Toolschevron-right](https://docs.hivel.ai/welcome-packet/quick-start-guide/integrating-your-tools) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Integrating Your Tools | Welcome Packet | Hivel [](https://hivel.gitbook.io/knowlegebase/integrations/github) Github [](https://hivel.gitbook.io/knowlegebase/integrations/gitlab) Gitlab [](https://hivel.gitbook.io/knowlegebase/integrations/bitbucket) Bitbucket [](https://hivel.gitbook.io/knowlegebase/integrations/jira) Jira [](https://hivel.gitbook.io/knowlegebase/integrations/azure-devops) Azure DevOps [](https://hivel.gitbook.io/knowlegebase/integrations/sonarqube) SonarQube [PreviousWelcome to Hivelchevron-left](https://docs.hivel.ai/welcome-packet) [NextKPIs in Hivelchevron-right](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # KPIs in Hivel | Welcome Packet | Hivel In this section, we will understand how to define, configure, and monitor KPIs tailored to your engineering goals by covering the below topics in depth. 1. Understanding KPIs in Hivel 2. Selecting Relevant KPIs for Your Team 3. Configuring KPIs in Hivel 4. Monitoring and Tracking KPI Progress 5. Regularly Reviewing and Adjusting KPIs [PreviousIntegrating Your Toolschevron-left](https://docs.hivel.ai/welcome-packet/quick-start-guide/integrating-your-tools) [NextUnderstanding and Selecting KPIschevron-right](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel/understanding-and-selecting-kpis) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Understanding and Selecting KPIs | Welcome Packet | Hivel **Understanding KPIs** Key Performance Indicators (KPIs) in Hivel are specific metrics chosen to represent essential aspects of your team’s performance. These indicators provide data-driven insights into areas like speed, quality, and team efficiency. Hivel categorises KPIs into Speed Metrics, Quality Metrics and Throughput Metrics to give teams a balanced view across these dimensions. * Speed Metrics: Cycle Time, Deployment Frequency. * Quality Metrics: Change Failure Rate, Mean Time to Repair (MTTR), Flashy Reviews, and Large PRs Reviewed * Throughput Metrics: Commits, PRs Opened, New Work, Active Days **Selecting KPIs** Start by defining what success looks like for your team. Are you looking to decrease development cycle time? Increase code quality? Identifying objectives helps choose KPIs that align with those goals. Prioritize based on impact by choosing a manageable set of KPIs that directly impact your team’s objectives. For example: * If reducing bottlenecks is essential, Cycle Time and Review Time might be top priorities. * To improve stability, focus on Change Failure Rate (CFR) and Mean Time to Repair (MTTR). * To reduce Review Time, focus on Avg. Size of PRs and percentage of PRs over 400 LoC * To improve on code quality, focus on Flashy Reviews and Rework. [PreviousKPIs in Hivelchevron-left](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel) [NextConfiguring KPIs in Hivelchevron-right](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel/configuring-kpis-in-hivel) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Reviewing and Adjusting KPIs | Welcome Packet | Hivel **Monthly or Quarterly Reviews:** * Set up a regular cadence, such as monthly or quarterly reviews, to assess how each KPI aligns with the team’s evolving goals. **Adjust Targets as Needed:** * If the team consistently meets a KPI target, consider adjusting the threshold to encourage continuous improvement. Conversely, if a KPI is challenging, adjust the baseline or provide additional resources to help the team meet expectations. **Learning from Outliers:** * Use Hivel’s insights feature to investigate outliers and spikes in KPI data. Outliers often reveal bottlenecks or issues that, when addressed, lead to significant performance gains. [PreviousMonitoring and Tracking KPIschevron-left](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel/monitoring-and-tracking-kpis) [NextBest Practices for Effective KPI Managementchevron-right](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel/best-practices-for-effective-kpi-management) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Configuring KPIs in Hivel | Welcome Packet | Hivel The Goals page allows you to set targets for metrics in Speed, Quality, and Throughput, enabling you to track and assess your team's progress. This guide will help you understand how to view and modify these goals and interpret the progress indicators. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F1678521024-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FxFR2Rv2DoZlYsSKT7aaT%252Fuploads%252FZBnemCgXE7ihd5KkSwGi%252FSet%2520goals.gif%3Falt%3Dmedia%26token%3Dbb88b6ee-5114-476e-9108-344e79968afd&width=768&dpr=3&quality=100&sign=a14cfda9&sv=2) To view the goals against each metric, you can click on "View Goals". The current value displayed for each metric represents the average value over the last 60 days. This historical data can be helpful when setting new goals. **Setting or Modifying Goals:** You can set or modify goals at both the organizational and team levels. Here’s how: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F1678521024-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FxFR2Rv2DoZlYsSKT7aaT%252Fuploads%252FoyHZvqmedXZTt1rivmzu%252FSet%2520Goals.gif%3Falt%3Dmedia%26token%3Dc780eab5-9807-49a5-a37a-a6a87223d075&width=768&dpr=3&quality=100&sign=b2b4c86d&sv=2) 1. Click on "Modify" to go ahead and edit the set goals. 2. You can edit the org-level goals from the "Organization" tab. To edit the goals at a team level, switch to "Team" tab and select any particular team. 3. Once done, click on Publish to track your progress against the new goals. **Understanding progress against goals:** Click on any of the Red/Yellow/Green indicators at the top of the dashboard to highlight the R/Y/G status for all metrics, allowing you to quickly identify areas that need attention. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F1678521024-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FxFR2Rv2DoZlYsSKT7aaT%252Fuploads%252FYpn94riXHJqdvfw8YFAR%252FUnderstanding%2520progress%2520to%2520goals.gif%3Falt%3Dmedia%26token%3D732f6b5c-15cb-46ff-b997-bdee45a45d59&width=768&dpr=3&quality=100&sign=18aff3c2&sv=2) The logic behind the R/Y/G is below: 1. Green = if the current value is 90% or above the goal 2. Yellow = if the current value is between 70% and 90% of the goal 3. Red = if the current value is below 70% of the goal You can also download a CSV report of the Goals and their progress. [Click herearrow-up-right](https://hivel.gitbook.io/knowlegebase/using-hivel/faqs/how-to-download-reports) to see how. If you have any questions or need any more help, please don't hesitate to contact [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#b9caccc9c9d6cbcdf9d1d0cfdcd597d8d0) . [PreviousUnderstanding and Selecting KPIschevron-left](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel/understanding-and-selecting-kpis) [NextMonitoring and Tracking KPIschevron-right](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel/monitoring-and-tracking-kpis) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Best Practices for Effective KPI Management | Welcome Packet | Hivel Create a streamlined KPI setup that aligns with your team’s goals and drives performance in meaningful and measurable ways. Regularly reviewing and adjusting these KPIs will help keep your team on track and focused on achieving continuous improvement with Hivel. * **Focus on Actionable KPIs:** Only track KPIs that the team can influence directly. This approach keeps the team motivated and engaged. * **Communicate the importance of KPIs:** Make sure each team member understands why KPIs matter and how their contributions help improve overall performance. * **Appreciate Progress:** Recognize when the team meets or exceeds KPI targets. Positive reinforcement encourages continued success. [PreviousReviewing and Adjusting KPIschevron-left](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel/reviewing-and-adjusting-kpis) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Monitoring and Tracking KPIs | Welcome Packet | Hivel **Understanding progress against goals:** Click on any of the Red/Yellow/Green indicators at the top of the dashboard to highlight the R/Y/G status for all metrics, allowing you to quickly identify areas that need attention. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F1678521024-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FxFR2Rv2DoZlYsSKT7aaT%252Fuploads%252FiwipgLbgynF2cKWt4TkT%252FUnderstanding%2520progress%2520to%2520goals.gif%3Falt%3Dmedia%26token%3D564573f7-3cc9-4246-b580-34d913d413e8&width=768&dpr=3&quality=100&sign=f1d3f4f&sv=2) The logic behind the R/Y/G is below: 1. Green = if the current value is 90% or above the goal 2. Yellow = if the current value is between 70% and 90% of the goal 3. Red = if the current value is below 70% of the goal You can also download a CSV report of the Goals and their progress. [Click herearrow-up-right](https://hivel.gitbook.io/knowlegebase/using-hivel/faqs/how-to-download-reports) to see how. [PreviousConfiguring KPIs in Hivelchevron-left](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel/configuring-kpis-in-hivel) [NextReviewing and Adjusting KPIschevron-right](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel/reviewing-and-adjusting-kpis) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Issue Age | Hivel **Issue Age** is a key metric that provides insight into how long it takes for a team to resolve a ticket or issue, from its creation to its completion. Understanding and optimizing Issue Age is crucial for maintaining a high level of productivity and ensuring customer satisfaction. circle-info **Formula:** Issue Age = Completion Date - Creation Date ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F26TpaG3A28JGzusr7JGE%252Fimage.png%3Falt%3Dmedia%26token%3D0fcdc105-d627-4405-afd7-c6abe29f1cc2&width=768&dpr=3&quality=100&sign=13a6addb&sv=2) #### [hashtag](https://docs.hivel.ai/using-hivel/investment/issue-age#example) **Example**: * **Creation Date**: August 1, 2024 * **Completion Date**: August 5, 2024 * **Issue Age**: 4 days #### [hashtag](https://docs.hivel.ai/using-hivel/investment/issue-age#why-is-issue-age-important) Why Is Issue Age Important? Issue Age is a critical metric for several reasons: * **Team Efficiency**: A lower Issue Age indicates that your team is resolving issues quickly, which is a sign of efficiency. A higher Issue Age might suggest bottlenecks or delays in the workflow that need to be addressed. * **Customer Satisfaction**: For customer-facing teams, reducing Issue Age is essential. Faster resolution times lead to higher customer satisfaction and a better overall experience. [PreviousInvestmentchevron-left](https://docs.hivel.ai/using-hivel/investment) [NextHow to set up Products & Allocation tabs in the Investment Screen?chevron-right](https://docs.hivel.ai/using-hivel/investment/how-to-set-up-products-and-allocation-tabs-in-the-investment-screen) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to download reports | Hivel Downloading reports in CSV format is a convenient way to analyze your data offline. In Hivel, you can download reports from the **Cockpit Pro, Pull Request, and Settings** screens. Below are step-by-step instructions for each type of report. **Cockpit Pro reports:** Cockpit Pro reports can be downloaded for data in the Speed, Quality, or Throughput buckets. To pull data from all buckets simultaneously, switch to tabular view and select "All." Here’s how to download a Cockpit report: 1. Navigate to Cockpit Pro screen. 2. Choose the relevant date range. 3. Apply filters for the desired team, repository, or projects. 4. Switch to tabular view. 5. Under the graphical/tabular option, click on the "Export to CSV" option. The file will be downloaded instantly with the columns and fields as visible in the platform. **Pull Request reports:** The Pull Request report includes all data available for each PR in the Pull Request screen. Here’s how to download a Pull Request report: 1. Navigate to Pull Request screen. 2. Apply filters to narrow down the relevant PRs. 3. Click on the "Export CSV" button. 4. The report will be sent to your mail. #### [hashtag](https://docs.hivel.ai/using-hivel/cockpit/how-to-download-reports#other-reports) **Other reports:** **Settings -> Download Reports:** You can download 4 kind of reports for the date range and teams that you select: 1. **Activity** - Number of Active days where the engineers had some Git activity for the selected time period. 2. **Activity (Raw)** - Detailed information on commits and PRs in various stages (merged, reviewed, opened, declined). 3. **Code Base Changes (Raw)** - Summary of codebase changes (across New Work, Rework, and Maintenance) for the selected time period for the selected teams. 4. **Commits part of PR Merged** - Details on commits that are part of PRs merged into the destination branch, including Lines of Changes, Rework, Maintenance, New Work, and other important information. 5. **Goals** - Targets and the values of the metrics based on the frequency. These reports will be sent to your mail, please check your spam folder in case you do not receive it within a few minutes. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FlLOUxm2gvHCtwZRO8YW3%252FScreenshot%25202024-09-10%2520at%25203.17.14%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D714118cb-6c8f-47ae-865e-70ed74e730fb&width=768&dpr=3&quality=100&sign=3d3b71da&sv=2) If you encounter any issues or have further questions, feel free to contact us at [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#ff8c8a8f8f908d8bbf9796899a93d19e96) . [PreviousCockpitchevron-left](https://docs.hivel.ai/using-hivel/cockpit) [NextMeetings Breakdownchevron-right](https://docs.hivel.ai/using-hivel/cockpit/meetings-breakdown) Last updated 11 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to add Custom fields for Product and Allocation Label in Jira | Hivel Here are the steps to add custom fields in Jira to map Product and Allocation Label in Hivel:- 1. **Access Jira Administration**: Log in to Jira as an administrator. 2. After successful login, go to the **Settings** (gear) icon in the top right corner near the profile and click on it. Then, select "Issues" from the dropdown. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2Fhivel.zendesk.com%2Fhc%2Farticle_attachments%2F17619139344669&width=768&dpr=3&quality=100&sign=5fc0db06&sv=2) 3. **Navigate to Custom Fields**: After clicking on "**Issues**" on the left the side panel, under the fields there is "**Custom fields"**, click on it. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2Fhivel.zendesk.com%2Fhc%2Farticle_attachments%2F17619139345949&width=768&dpr=3&quality=100&sign=e47e51cc&sv=2) 4. **Select Field Type:** Now you will be redirected to select field type; you can select any of the following field types "Select List(single choice)" or "Short Text(plain text only)." Jira offers various types such as text field, select list, date picker, etc. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2Fhivel.zendesk.com%2Fhc%2Farticle_attachments%2F17619139349405&width=768&dpr=3&quality=100&sign=a2ec45d1&sv=2) 5. **Configure the Field:** Provide a name for the custom field and configure any additional options based on the field type you selected. For example, if you're creating a dropdown select list, you'll need to define the list of options. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2Fhivel.zendesk.com%2Fhc%2Farticle_attachments%2F17619125679389&width=768&dpr=3&quality=100&sign=9b4133fd&sv=2) 6. **Associate with Screens:** Choose the screens where you want the custom field to appear, preferably all screens, so select all. Screens determine where the field will be displayed when users create or edit issues and update. 7. **Add to Projects:** Now, in the left panel, Click on "Project Settings" and drag and drop all the projects that need those custom fields. **Note:** Repeat the above steps to create additional custom fields if needed. After creating the custom fields, you can add them to the details of the Jira ticket to capture relevant information. [PreviousHow to set up Products & Allocation tabs in the Investment Screen?chevron-left](https://docs.hivel.ai/using-hivel/investment/how-to-set-up-products-and-allocation-tabs-in-the-investment-screen) [NextPull Requestchevron-right](https://docs.hivel.ai/using-hivel/pull-request) Last updated 4 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Using Hivel | Hivel **Welcome to Hivel’s Knowledge Base** Your go-to guide for getting the most out of Hivel - from tracking performance and managing goals to optimizing your engineering workflows. Explore how to enhance productivity, streamline collaboration, and make the most of every feature. All your essential Hivel know-how, in one place. [](https://docs.hivel.ai/using-hivel/cockpit) Cockpit [](https://docs.hivel.ai/using-hivel/investment) Investment [](https://docs.hivel.ai/using-hivel/pull-request) Pull Request Screen [](https://docs.hivel.ai/ai-adoption) AI Adoption [](https://docs.hivel.ai/using-hivel/goals) Goals [](https://docs.hivel.ai/using-hivel/coding) Coding Screen [](https://docs.hivel.ai/using-hivel/team-pulse) Activity [](https://docs.hivel.ai/using-hivel/dev360) Dev360 [](https://docs.hivel.ai/using-hivel/process) Process Screen [](https://docs.hivel.ai/using-hivel/work-item-breakdown) Work Item Breakdown [](https://docs.hivel.ai/using-hivel/coding-hotspots) Coding Hotspots [](https://docs.hivel.ai/using-hivel/hivel-quadrant) Hivel Quadrant [](https://docs.hivel.ai/using-hivel/performance-appraisal) Performance Appraisal [](https://docs.hivel.ai/using-hivel/lucy) Lucy [](https://docs.hivel.ai/using-hivel/hivel-score) Hivel Score [PreviousWelcome to Hivelchevron-left](https://docs.hivel.ai/) [NextCockpitchevron-right](https://docs.hivel.ai/using-hivel/cockpit) Last updated 1 day ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Meetings Breakdown | Hivel The Meetings Breakdown feature provides an overview of your team's meeting schedules, helping you identify if they're overwhelmed by excessive long meetings. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fn4e1ueeMat8FGsLXkCH2%252FScreenshot%25202024-09-10%2520at%25203.22.19%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D8344f5f8-6fa7-4400-87bd-20154f4bcebc&width=768&dpr=3&quality=100&sign=5fef782b&sv=2) This feature can be accessed while creating a new custom dashboard or by navigating to the custom dashboards page -> selecting any metric -> "Meetings Breakdown" from the dropdown. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FqSA7Yv2bp2Y2OGx1oJy6%252FGIF%2520Recording%2520Sept%252010%2520%281%29.gif%3Falt%3Dmedia%26token%3Dacbecfd9-e765-4edb-bf8b-08bbbbf7280a&width=768&dpr=3&quality=100&sign=8eb7c760&sv=2) _Accessing from within a metric_ ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FPYl1pD1wKXetqlUHDfqB%252FGIF%2520Recording%2520Sept%252010%2520from%2520Jumpshare.gif%3Falt%3Dmedia%26token%3D1700354c-091b-4b82-bd1b-5d110b6fb49f&width=768&dpr=3&quality=100&sign=bf9a3a0f&sv=2) _Adding the metric as part of new dashboard creation_ #### [hashtag](https://docs.hivel.ai/using-hivel/cockpit/meetings-breakdown#the-total-time-spent-is-broken-down-into-the-following-categories-of-meetings) The total time spent is broken down into the following categories of meetings: 1. **Deep** \- If the gap between two meetings is more than 2 hours, it's considered Deep work. This allows developers to focus on their tasks without interruption. _Ideally majority of the developers' time should be in this category._ 2. **Shallow** - When the gap between two meetings is less than 2 hours, it's classified as Shallow work, as frequent meetings require context switching. 3. **Private** - All meetings marked as Private in Google Calendar or personal time blocks fall under this category. 4. **Team** - These are meetings with three or more people from the same organization. 5. **External** - Meetings that include at least one person from outside the organization. 6. **One\_On\_One** - Meetings involving just two people from the same organization. You can filter this data based on specific teams and dates to gain the insights you need. If google calendar is not integrated with Hivel yet, please follow the steps mentioned [herearrow-up-right](https://hivel.zendesk.com/hc/en-in/articles/19341040186909-How-to-integrate-Google-Calendar-in-Hivel) . If you encounter any issues or have further questions, feel free to contact us at [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#a9dadcd9d9c6dbdde9c1c0dfccc587c8c0) . [PreviousHow to download reportschevron-left](https://docs.hivel.ai/using-hivel/cockpit/how-to-download-reports) [NextInvestmentchevron-right](https://docs.hivel.ai/using-hivel/investment) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Pull Request | Hivel Pull Requests are the holy grail of any software development process, and getting a 360-degree view into them, and the ability to filter to see the PRs that may require your attention is necessary. #### [hashtag](https://docs.hivel.ai/using-hivel/pull-request#you-can-use-data-on-this-screen-to) You can use data on this screen to: * Consistently get a view of the process, proactively coach the team and remind them of your best practices or SLA. * Show the reviewer reviewing most PRs and schedule a knowledge-sharing session. * Look at the PRs that are open for longer, and clear roadblocks to push them to production. * If your average cycle time is higher than expected, you can look at the PRs or engineers swinging the most toward this number. #### [hashtag](https://docs.hivel.ai/using-hivel/pull-request#major-metrics-and-what-they-mean) Major metrics and what they mean ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F3vMk2TJKmkc5fOMpNi0m%252Fimage.png%3Falt%3Dmedia%26token%3D20431abf-bf69-4eef-a6b2-06e99395d81e&width=768&dpr=3&quality=100&sign=8d1267c3&sv=2) 1. **Release Merge Frequency** is the total number of PRs merged to release branch in that selected time period/total number of days in the selected time period. 2. **Hotfix Rate** is the number of hotfix PRs merged to release branch over the total number of PRs merged to release branch. 3. **Hotfix Resolution Rate** shows the average cycle time of the hotfix PRs. 4. **Unreviewed PRs** gives the number of PRs that were merged without any approval. #### [hashtag](https://docs.hivel.ai/using-hivel/pull-request#other-metrics-and-filters) **Other metrics and filters:** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FSerHpsr8pY9649PHoCqN%252Fimage.png%3Falt%3Dmedia%26token%3D3e4f7e4e-f605-4fb3-b329-372594871bd3&width=768&dpr=3&quality=100&sign=a7e628fb&sv=2) * **Unaccounted Work** includes all PRs that are not linked to Jira or any other project management tool's tickets. * **Ready to Review** shows all PRs that are open and are pending a review or approval. * **Ready to Merge** shows all PRs that have been approved and are awaiting merge. * **PRs > 400 LoC** helps you track larger PRs over a certain number of lines of code in the selected time period. The larger the PR, the slower it moves through the review cycle and the higher the probability of bugs. * The threshold of 400 LoC is modifiable from Configurations screen. * **Cycle time > 5 days** shows all PRs merged in that time period with cycle time greater than 5 days. * The threshold of 5 days is modifiable from Configurations screen. * **Flashy Review** is used to identify PRs which were reviewed very fast and indicate ineffective review. By default PRs > 200 LoC with a review time < 5minutes, are considered flashy, [but this is configurable](https://docs.hivel.ai/configurations/branch-configurations#flashy-review) . [PreviousHow to add Custom fields for Product and Allocation Label in Jirachevron-left](https://docs.hivel.ai/using-hivel/investment/how-to-add-custom-fields-for-product-and-allocation-label-in-jira) [NextComments Categorizationchevron-right](https://docs.hivel.ai/using-hivel/pull-request/comments-categorization) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to set up Products & Allocation tabs in the Investment Screen? | Hivel Hivel's Products and Allocation feature helps you see where your team's efforts are going. It shows how resources are split across your products through Jira tickets. By mapping your custom Jira labels in Hivel, you can get a clear picture of this distribution and make smarter investment decisions. Let’s walk through how to set this up. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FIkIXrQmFkVaU2RwTkLbm%252Fimage.png%3Falt%3Dmedia%26token%3D3fb0d152-dc8d-4c14-8db6-84a7af3e61cf&width=768&dpr=3&quality=100&sign=9192080e&sv=2) _Product section_ ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FneVqqtokkWRyXYL6mBiI%252Fimage.png%3Falt%3Dmedia%26token%3D2ba85a82-7f3a-4cde-acec-2f071d887c3c&width=768&dpr=3&quality=100&sign=a74e6716&sv=2) _Allocation section_ #### [hashtag](https://docs.hivel.ai/using-hivel/investment/how-to-set-up-products-and-allocation-tabs-in-the-investment-screen#to-populate-the-graphs-hivel-requires-information-about-two-custom-fields) **To populate the graphs**, Hivel requires information about two custom fields: * **Product/Projects:** This field categorizes work into distinct product lines or projects in ways you may want to monitor effort spread across projects. Examples include Payments, Data Engineering, Checkout, AI, and Compliance. * **Work Type:** This field categorizes tasks based on their nature or purpose such as OKRs, initiatives and more. Examples include Roadmap, Tech Debt, R&D, Customer Success, KTLO (Keep the Lights On), etc. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F3ErkhMLLGcubbilIKePn%252Fimage.png%3Falt%3Dmedia%26token%3D44b067fa-6f80-4ce5-8971-94fe19e73655&width=768&dpr=3&quality=100&sign=2caafab6&sv=2) These custom fields enable better organization and tracking of tasks within the Hivel platform, allowing teams to effectively manage their work and visualize progress across different product lines and types of work. Please note that we can use any name for the above that you may be or prefer using internally. circle-info If you don't have the custom fields set up on Jira yet, you can [**follow the instructions here**](https://docs.hivel.ai/using-hivel/investment/how-to-add-custom-fields-for-product-and-allocation-label-in-jira) to create them. **Once you have custom fields**, follow these steps: 1. **Go to Settings screen** 2. Under Investment Configuration, set the 2 custom fields for Product and Allocation. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FlFiMh4Iwk1cbTdCpcXRz%252Fimage.png%3Falt%3Dmedia%26token%3D9031cd92-bbb1-492b-9474-72b8e108ed15&width=768&dpr=3&quality=100&sign=2ff0ad84&sv=2) That's it, all done! The new data will be within 24 hours. In case the data does not show up, please reach out to [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#c6b5b3b6b6a9b4b286aeafb0a3aae8a7af) . [PreviousIssue Agechevron-left](https://docs.hivel.ai/using-hivel/investment/issue-age) [NextHow to add Custom fields for Product and Allocation Label in Jirachevron-right](https://docs.hivel.ai/using-hivel/investment/how-to-add-custom-fields-for-product-and-allocation-label-in-jira) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Cockpit | Hivel Cockpit is your centralized command center for engineering insights. It brings together all your boards and templates into a streamlined view, making it easy to track key engineering metrics, explore trends, and derive insights without jumping across multiple screens. With quick access to favorites, flexible filtering, drilldowns across time and teams, Cockpit helps you move from high-level visibility to actionable understanding in just a few clicks. [hashtag](https://docs.hivel.ai/using-hivel/cockpit#key-features) Key features ----------------------------------------------------------------------------------- #### [hashtag](https://docs.hivel.ai/using-hivel/cockpit#unified-view-of-boards-and-templates) Unified View of Boards & Templates * Access **all created boards** and **Hivel-provided templates** in a single place. * Easily differentiate between **private boards**, **public boards**, and **templates** with clear visual indicators. **Favorites & Quick Access** **Pin frequently used boards** to the side menu for instant access. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fhpgkf8phOMBxbNOC0Kz1%252FGoogle%2520Keep%2520Note.png%3Falt%3Dmedia%26token%3Dbb45b456-29a5-4c9f-8639-e368d2324594&width=768&dpr=3&quality=100&sign=88c0bc4d&sv=2) **Metrics list** **Hover over any template card** to quickly view a list of all metrics included in the board. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FYjlEwMLJQCNz84ZreN0K%252FGoogle%2520Keep%2520Note%2520%281%29.png%3Falt%3Dmedia%26token%3D5f929609-4857-4f5a-ba08-5a4bde3287c0&width=768&dpr=3&quality=100&sign=1dd70b3d&sv=2) **Board Ownership** See **who created a board and when it was created** for better tracking and collaboration. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDNdmeuYlPDyJTUUFKSv3%252FGoogle%2520Keep%2520Note%2520%282%29.png%3Falt%3Dmedia%26token%3D3f70008b-c5f8-4d88-91d9-c28fdde704e7&width=768&dpr=3&quality=100&sign=3ca232b9&sv=2) [hashtag](https://docs.hivel.ai/using-hivel/cockpit#features-available-for-the-boards) Features available for the boards ----------------------------------------------------------------------------------------------------------------------------- #### [hashtag](https://docs.hivel.ai/using-hivel/cockpit#create-your-own-board-for-set-of-metrics-and-save-filters) Create your own board for set of metrics and save filters * Navigate to '**All Boards**', Click the '**Create dashboard**' button, and create your customized board by giving the board name, description, and type of board. * Select the metrics and click on '**Apply Changes**.' ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FdoayQXbCMt7GDH3YFqU8%252FScreen%2520Cast%25202026-01-30%2520at%252012.15.16%2520PM.gif%3Falt%3Dmedia%26token%3D2a72ba7f-35d3-46e8-8923-17d18d1d8e7b&width=768&dpr=3&quality=100&sign=e33519c&sv=2) * You can tailor the dashboard to your liking and select a single team, multiple teams, one repository, or a group of repositories. * Choose a specific date range to focus on the period that is most relevant to your analysis. * Click on the '**Save Filter**' button, give the filter name, and save it for future reference. * Upon saving, the filter's unique URL is automatically updated in the browser’s address bar. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FcxtgkXa9jQHrTBxqHVp9%252FScreen%2520Cast%25202026-01-30%2520at%252012.19.39%2520PM.gif%3Falt%3Dmedia%26token%3Da2b24845-29cf-45c6-93a5-77678b32a966&width=768&dpr=3&quality=100&sign=75138dc7&sv=2) * Remember to copy the URL from the address bar for future use or to share it with your team. #### [hashtag](https://docs.hivel.ai/using-hivel/cockpit#drilldown-from-quarterly-to-daily-levels) **Drilldown from Quarterly to Daily Levels** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FSdKHX7t1R9CxqrLNRbFM%252Fimage.png%3Falt%3Dmedia%26token%3D3c13d75e-c832-4458-95b5-0061e43157b2&width=768&dpr=3&quality=100&sign=f6632fbf&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FNmxEQu72JRlCfFXrQmyP%252Fimage.png%3Falt%3Dmedia%26token%3D0e334dac-fd8a-46e8-a870-8cfce453b0f1&width=768&dpr=3&quality=100&sign=7770d1ea&sv=2) * Start at a quarterly overview and **drill down into monthly, weekly, or daily trends** for deeper insights. * View pull requests (PRs) related to specific time periods for better traceability and exclude outliers. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F9UQY6RkxfIubnTcEneT5%252Fimage.png%3Falt%3Dmedia%26token%3D912e3a12-2123-4c02-93ca-2df9df750967&width=768&dpr=3&quality=100&sign=70fb460f&sv=2) #### [hashtag](https://docs.hivel.ai/using-hivel/cockpit#dashboard-access-and-permissions) Dashboard Access & Permissions ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FUYkv0DVDLiozImUOehUJ%252FGoogle%2520Keep%2520Note%2520%284%29.png%3Falt%3Dmedia%26token%3D78d887dc-a0c3-4f75-a503-6c8ed3203def&width=768&dpr=3&quality=100&sign=f01a0ef6&sv=2) * **Public Dashboards:** Visible to everyone in the organization, but only the owner can modify them. * **Private Dashboards:** Only the owner can view, edit, and delete them. #### [hashtag](https://docs.hivel.ai/using-hivel/cockpit#workspaces-and-team-views) Workspaces & Team Views ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F5SHIbRB8FP7x89XoeEgE%252Fimage.png%3Falt%3Dmedia%26token%3D676e0c85-e076-4d4d-a31b-484cc470976e&width=768&dpr=3&quality=100&sign=94c69fb9&sv=2) * If [Workspaces are enabled from the configuration](https://docs.hivel.ai/configurations/general-configurations) , users can view the combination of both Teams and Workspaces for a more structured and categorized view of performance metrics. * This allows for **cross-team and cross-workspace comparisons**, helping organizations track performance across different projects and initiatives. #### [hashtag](https://docs.hivel.ai/using-hivel/cockpit#side-by-side-team-comparison) Side-by-Side Team Comparison ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F1XNOM6sAQLVZe1foQhi6%252FGoogle%2520Keep%2520Note%2520%283%29.png%3Falt%3Dmedia%26token%3Da794c86a-ff87-4ee5-9cb2-5045e012e3d2&width=768&dpr=3&quality=100&sign=f49461fe&sv=2) * Compare **selected teams side by side** to **analyze performance trends over time**. * Easily track progress across multiple teams and benchmark their efficiency, cycle time, and other critical metrics. #### [hashtag](https://docs.hivel.ai/using-hivel/cockpit#tv-mode) **TV Mode:** You can select the TV icon at the top right corner to switch the dashboard display to TV mode, optimizing it for larger screens. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FG43HPH2A1XGSfFECqeje%252Fimage.png%3Falt%3Dmedia%26token%3D00b1ad57-06e5-435f-bee6-42042bcc661e&width=768&dpr=3&quality=100&sign=21e9a4b9&sv=2) #### [hashtag](https://docs.hivel.ai/using-hivel/cockpit#download-report) **Download Report:** Next to the TV view icons, find the ‘**Download** ’icons. Click on this to download an image of the currently displayed graph or chart for offline reference. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F5QqemVYdIzifxdDQsY7f%252Fimage.png%3Falt%3Dmedia%26token%3D6915abe4-c994-4da9-a1b5-25f4b64bfff8&width=768&dpr=3&quality=100&sign=2be8c5d0&sv=2) For further guidance or support with Custom Dashboards, feel free to reach out to our support team at [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#84f7f1f4f4ebf6f0c4ecedf2e1e8aae5ed) . [PreviousUsing Hivelchevron-left](https://docs.hivel.ai/using-hivel) [NextHow to download reportschevron-right](https://docs.hivel.ai/using-hivel/cockpit/how-to-download-reports) Last updated 1 month ago * [Key features](https://docs.hivel.ai/using-hivel/cockpit#key-features) * [Features available for the boards](https://docs.hivel.ai/using-hivel/cockpit#features-available-for-the-boards) sun-brightdesktopmoon sun-brightdesktopmoon --- # Metrics & Definitions | Hivel [🚅Speedchevron-right](https://docs.hivel.ai/metrics-and-definitions/speed) [💯Qualitychevron-right](https://docs.hivel.ai/metrics-and-definitions/quality) [📈Throughputchevron-right](https://docs.hivel.ai/metrics-and-definitions/throughput) [PreviousTeam level Hivel Score Calculationchevron-left](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation) [NextSpeedchevron-right](https://docs.hivel.ai/metrics-and-definitions/speed) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to exclude outlier commits and PRs? | Hivel Are some known outliers (like extra large commits) skewing your average metrics? Fear not, you can exclude them from your reports easily. Here's how - Click the **Exclude button**![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FJ5lakWkMXjiOlGRcs7Ri%252Fimage.png%3Falt%3Dmedia%26token%3D8e11539a-0882-4cb6-84ed-a3091a546111&width=38&dpr=3&quality=100&sign=1a53ebc9&sv=2) on the * right panel in Process screen to exclude a PR. * right panel in Coding screen to exclude a Commit. * "PR size" column in Pull Request screen to exclude a PR. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FtjAaC7CfM2sijBCenz49%252Fimage.png%3Falt%3Dmedia%26token%3D34940921-d0d7-48c8-83db-3894a2d71f14&width=768&dpr=3&quality=100&sign=48d1b894&sv=2) * All screens will be **updated instantly**. Only Cockpit will take 24 hours to reflect the change. * You can also **include** a PR/commit after it's been excluded by clicking on the![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FBVcSARjzqdOF7kRfhWAh%252Fimage.png%3Falt%3Dmedia%26token%3Da224fa32-c99e-4eb9-ac78-35eab2057dee&width=40&dpr=3&quality=100&sign=d89d945d&sv=2)icon in the **Excluded Items** section in Settings page. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FedYaiJgnxjv2AifGzByU%252FScreenshot%25202024-09-10%2520at%25204.06.03%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Db6b4d205-6caf-4eb2-9858-b4b41e7faf6b&width=768&dpr=3&quality=100&sign=373f3a9a&sv=2) [PreviousReview Cycleschevron-left](https://docs.hivel.ai/using-hivel/pull-request/review-cycles) [NextProcesschevron-right](https://docs.hivel.ai/using-hivel/process) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Process | Hivel The Process Screen in Hivel gives you a visual breakdown of your cycle time—from writing code to merging it into production. This view is designed to help you identify bottlenecks, track engineering efficiency, and make data-driven improvements. ### [hashtag](https://docs.hivel.ai/using-hivel/process#view-the-prs-behind-any-metric) 🔍 View the PRs Behind Any Metric Click on any metric to instantly see the pull requests contributing to it. Noticed a spike? Just click on that time frame to view the PRs involved. ### [hashtag](https://docs.hivel.ai/using-hivel/process#dive-into-pr-details) **Dive Into PR Details** Drill down into you version control and see the tickets associated with the PR. This gives you a clear picture of where time is being spent and who’s involved. ### [hashtag](https://docs.hivel.ai/using-hivel/process#identify-bottlenecks) ⚠️ Identify Bottlenecks See how long each stage took for a specific PR. This helps you pinpoint where delays occur—whether it's extended coding time, slow reviews, or lag in merging. ### [hashtag](https://docs.hivel.ai/using-hivel/process#clean-up-outliers) 🧹 Clean Up Outliers If a spike is expected or due to a known outlier, you can **exclude specific PRs** from the board. This ensures your averages stay accurate and meaningful. **You can use data on this screen to:** * See the stage at which your team is spending most of their time - coding, review, or release process. * Averages could sometimes be deceiving, so check the right panel for all the PRs and their respective breakdown into various stages. * You can look at your current sprints or past sprints and use this data during retrospectives. circle-info Refer [here](https://docs.hivel.ai/using-hivel/pull-request/how-to-exclude-outlier-commits-and-prs) to know how to exclude certain PRs and commits from the calculation. [PreviousHow to exclude outlier commits and PRs?chevron-left](https://docs.hivel.ai/using-hivel/pull-request/how-to-exclude-outlier-commits-and-prs) [NextGoalschevron-right](https://docs.hivel.ai/using-hivel/goals) Last updated 11 months ago * [🔍 View the PRs Behind Any Metric](https://docs.hivel.ai/using-hivel/process#view-the-prs-behind-any-metric) * [Dive Into PR Details](https://docs.hivel.ai/using-hivel/process#dive-into-pr-details) * [⚠️ Identify Bottlenecks](https://docs.hivel.ai/using-hivel/process#identify-bottlenecks) * [🧹 Clean Up Outliers](https://docs.hivel.ai/using-hivel/process#clean-up-outliers) sun-brightdesktopmoon sun-brightdesktopmoon --- # Review Cycles | Hivel A review cycle is defined as the sequence of comments and commits within a PR. Each cycle is counted when a comment or request for change is followed by a commit or approved by someone. This cycle can repeat multiple times, indicating multiple review cycles within the same PR. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F6mcADUvBpZMFeIXPiZze%252FScreenshot%25202024-09-10%2520at%25203.59.35%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D28c7ba24-4238-468a-98ca-5a12ae52ea76&width=768&dpr=3&quality=100&sign=589ec9be&sv=2) circle-info _This field can be found in the PR screen as a column._ Understanding the review cycle count helps in assessing the thoroughness and efficiency of the review process. High review cycle counts might indicate thorough reviews or potential issues in the code requiring multiple revisions, whereas low counts might suggest either fewer issues or potentially less thorough reviews. #### [hashtag](https://docs.hivel.ai/using-hivel/pull-request/review-cycles#below-is-the-explanation-on-how-it-gets-calculated) Below is the explanation on how it gets calculated: 1. **Review Cycle = 0** - If a pull request has neither comments nor approval, the review cycle count is 0. 2. **Review Cycle = 1** - If a pull request has been approved with or without comments, the review cycle count is 1. This accounts for the fact that some form of review has taken place (the approval), even if no comments were left. `_**Example**_` A PR is created and a reviewer approves it without leaving any comments. Then review cycle count is 1 because the PR was reviewed (approved) even though no comments were made. 3. **Review Cycle is more than 1** - For pull requests with both comments and commits, the review cycle count is calculated based on the number of comment-commit pairs. Each sequence where a comment is followed by a commit is counted as one review cycle. This means that for each set of comments followed by a commit, the review cycle count increases. `_**Example**_` A PR is created, and a reviewer leaves comments. The developer makes changes and commits those changes. This sequence repeats. - _**Result**_: The review cycle count is incremented for each comment-commit pair. - 1st Cycle: Reviewer comments -> Developer commits changes (Cycle 1) - 2nd Cycle: Reviewer comments again -> Developer commits changes again (Cycle 2) - The review cycle count is the number of these comment-commit sequences. If you encounter any issues or have further questions, feel free to contact us at [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#9deee8ededf2efe9ddf5f4ebf8f1b3fcf4) . [PreviousComments Categorizationchevron-left](https://docs.hivel.ai/using-hivel/pull-request/comments-categorization) [NextHow to exclude outlier commits and PRs?chevron-right](https://docs.hivel.ai/using-hivel/pull-request/how-to-exclude-outlier-commits-and-prs) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Investment | Hivel The Investment Screen provides a detailed view of your team's efforts as tracked in Jira issues. It is divided into four sections, each offering specific insights into different aspects of your team's work: [**Issue**](https://docs.hivel.ai/using-hivel/investment#h_01hywypcmca37vt49c4764ms90) | [**Epic**](https://docs.hivel.ai/using-hivel/investment#id-01hywzfvmctbkdjc1x2wn46w6h) | [**Product and Allocation**](https://docs.hivel.ai/using-hivel/investment#id-01hywzmp6s17w4s3z0h4ks82cj) | [**Delivery**](https://docs.hivel.ai/using-hivel/investment#id-01hyx089atjhwfc8anp8q73ajw) ### [hashtag](https://docs.hivel.ai/using-hivel/investment#h_01hyx2e4t4s1edt663bwbjq25b) **Sections:** #### [hashtag](https://docs.hivel.ai/using-hivel/investment#h_01hywypcmca37vt49c4764ms90) **Issue** * Gain visibility into the volume of issues or story points per sprint and issue type. This helps you assess whether your team is working within capacity or if there is room for improvement ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FfFtuqhi7tvNCJHKvIHnp%252FInvst%25201.1.jpg%3Falt%3Dmedia%26token%3D6eb58269-1ddc-48b2-8c3b-cb3e6d4f763b&width=768&dpr=3&quality=100&sign=6546418b&sv=2) 1. **Filter on issuetypes:** Click on any issue type to filter the graph data to only that issue type. The available issue types will be based on the issues created in your Jira project and board. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FCpDXU3G0EH2vj0z9yNgN%252FInvst%25202.1.jpg%3Falt%3Dmedia%26token%3D2d296732-a162-48ae-89b2-e2df809c68c7&width=768&dpr=3&quality=100&sign=7964a354&sv=2) 1. **Sprint-level drilldown:** Click on a particular sprint to view detailed fields of each Jira issue within that sprint. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FtdTnc06jgs8bNlG6wcC2%252FInvst%25203.1.jpg%3Falt%3Dmedia%26token%3Dd24b2efc-e710-493a-95e8-406cd0fe8763&width=768&dpr=3&quality=100&sign=2430e458&sv=2) 1. **Filter to identify missing hygiene:** You can apply additional filters such as "Missing Epics," "Missing Assignee," and "Missing Story Points" to identify issues with missing hygiene and ensure they are updated for proper tracking. circle-info All the sections in Investment follow a similar above behaviour of filtering on issuetype, sprints and arriving at the drilldown. #### [hashtag](https://docs.hivel.ai/using-hivel/investment#id-01hywzfvmctbkdjc1x2wn46w6h) **Epic** * This section provides visibility into the volume of tickets and story points at both the Epic and sprint levels. It helps you understand the efforts spent on specific Epics within each sprint. * Similar to the Issue section, you can drill down into issues by clicking on a sprint and filter by selecting a particular Epic from the available options. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FE3M9Be8rSGEJmv5rRY2G%252Fimage.png%3Falt%3Dmedia%26token%3D41b032b4-93c3-4ad7-9adc-d6c9a1c0ae4a&width=768&dpr=3&quality=100&sign=28bb0297&sv=2) #### [hashtag](https://docs.hivel.ai/using-hivel/investment#id-01hywzmp6s17w4s3z0h4ks82cj) **Product and Allocation** Hivel's Products and Allocation sections helps you see where your team's efforts are going. It shows how resources are split across your products through Jira tickets. By mapping your custom Jira labels in Hivel, you can get a clear picture of this distribution and make smarter investment decisions. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FlhdtXMWaM0JtSq7l9qRP%252Fimage.png%3Falt%3Dmedia%26token%3D9d74882b-cdc1-4d58-ace8-6b8a377f1f3a&width=768&dpr=3&quality=100&sign=ae81e7a3&sv=2) _Products section_ ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FYcKm3w7flqxzhOG21pwJ%252FScreenshot%25202024-09-10%2520at%25203.43.25%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D3524d6d8-152d-428d-8c13-cd748629ef6c&width=768&dpr=3&quality=100&sign=c5d6c37e&sv=2) _Allocation section_ For more information on how to set up this functionality, please refer to [this article](https://docs.hivel.ai/using-hivel/investment/how-to-set-up-products-and-allocation-tabs-in-the-investment-screen) . #### [hashtag](https://docs.hivel.ai/using-hivel/investment#id-01hyx089atjhwfc8anp8q73ajw) **Delivery** The **Delivery Accuracy** graphs offer insights into the completion rate of planned efforts within a sprint and highlight any unplanned items that were addressed, as well as any delays encountered. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FexE5QPFZ2d80eofUDdSY%252Fimage.png%3Falt%3Dmedia%26token%3D296c4aae-e06c-434b-be26-2e739480142a&width=768&dpr=3&quality=100&sign=978e04aa&sv=2) The delivery bar chart data is categorized into two main sections: Completed and Spillover. Each section is further divided into Planned and Unplanned. * **Completed** : Issues/Story Points completed before the sprint closes. * **Spillover** : Issues/Story Points not completed by the time the sprint closes. * **Planned** : Issues/Story Points created before the sprint starts. * **Unplanned** : Issues/Story Points created after the sprint starts. **Delivery Trend** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FRcZ2imf7mh9THfJpOkYG%252Fimage.png%3Falt%3Dmedia%26token%3D434ced4e-3f3a-4ead-84ae-eca12a9c439e&width=768&dpr=3&quality=100&sign=32de8b7d&sv=2) #### [hashtag](https://docs.hivel.ai/using-hivel/investment#delivery-trend) Delivery Trend The **Delivery Trend** chart helps you track and evaluate your team’s sprint execution by combining two key metrics: 1\. **Say-Do Ratio** This measures the accuracy of sprint planning by comparing what was **committed at the start of the sprint** to what was **actually delivered**. * **Formula:** `(Work Delivered from Sprint Start / Work Committed at Sprint Start) × 100` * **What it means:** * A **high Say-Do Ratio** (>100%) could indicate **significant ad-hoc work** is being added and completed, possibly reducing focus on planned items. * A **low Say-Do Ratio** (<100%) suggests that the team is **overcommitting** or **facing blockers**, pointing to potential areas where expectations or planning should be adjusted. * * * 2\. **Delivery Rate** This measures how much of the **total work taken up during the sprint -** both planned and ad-hoc - was actually delivered. * **Formula:** `(Total Work Delivered / Total Work Taken Up in Sprint) × 100` * **What it means:** * Always shown as a percentage out of 100%. * A **high Delivery Rate** indicates effective throughput, regardless of how work entered the sprint. * A **low Delivery Rate** may signal capacity issues, scope creep, or blockers mid-sprint. * * * #### [hashtag](https://docs.hivel.ai/using-hivel/investment#why-both-metrics-matter) 🧠 Why Both Metrics Matter When used together, **Say-Do Ratio** and **Delivery Rate** provide a fuller picture of sprint health: * If both metrics are **high**, the team is likely performing well and adapting effectively. * If **Delivery Rate is high but Say-Do Ratio is low**, the team is completing work but not sticking to the original plan (possible unplanned work). * If **both are low**, the team may be overcommitting or facing blockers that need investigation. * If **Say-Do Ratio is high but Delivery Rate is low**, it might indicate too much ad-hoc work was started but not completed. Use these insights to improve sprint planning, manage expectations, and identify areas where the team may need support or process adjustments. * * * ### [hashtag](https://docs.hivel.ai/using-hivel/investment#h_01hzf0crtvgz5rkv4ha91qk0bk) **Filters:** In each of the sections, there are certain filters that can be applied to reflect only the relevant data: * **Boards/Sub boards** : Boards refer to Jira Projects and Sub boards refer to the boards inside a Jira project. You can select only one Board at a time, but you can select any number of Sub boards within that Board. All subsequent filters will apply on the selected Boards/Sub board filter. * **Sprints** _(only for Issue, Epic, and Delivery sections)_ : Use this filter to display data based on specific sprints. By default, the latest 5 sprints will be selected. * **Assignees** _(only for Issue, Epic, and Delivery sections)_ : To filter out data for the Assignees of Jira tickets. * **Tickets/Story Points** : Choose to view the data as either the count of tickets or the sum of story points. * **Date filter** (_only for Product and Allocation sections)_ : Filter the Product and Allocation data for a specified time period. For more information or assistance, please contact our support team at [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#97e4e2e7e7f8e5e3d7fffee1f2fbb9f6fe) . [PreviousMeetings Breakdownchevron-left](https://docs.hivel.ai/using-hivel/cockpit/meetings-breakdown) [NextIssue Agechevron-right](https://docs.hivel.ai/using-hivel/investment/issue-age) Last updated 3 months ago * [Sections:](https://docs.hivel.ai/using-hivel/investment#h_01hyx2e4t4s1edt663bwbjq25b) * [Filters:](https://docs.hivel.ai/using-hivel/investment#h_01hzf0crtvgz5rkv4ha91qk0bk) sun-brightdesktopmoon sun-brightdesktopmoon --- # Comments Categorization | Hivel **Explainer Video:** The "Comments Category" column in the Pull Requests tab is an AI-powered feature that automatically analyzes and categorizes comments into specific labels based on their content. This feature helps you quickly understand the overall sentiment and focus of the comments within each pull request, making it easier to address issues and manage code reviews. **We categorize the Pull request in the below categories:** #### [hashtag](https://docs.hivel.ai/using-hivel/pull-request/comments-categorization#type-1) **Type 1:** * _**LGTM**__:_ PRs that are merged without significant issues or objections i.e. comments indicating approval, positive feedback on the implementation, or minor suggestions that are quickly addressed without major revisions. * _For example, "Great job! This looks perfect and works as expected."_ * _**Refactor**__:_ PRs that need significant changes to improve code quality or structure before they can be merged i.e. comments suggesting extensive changes, restructuring, or optimization of the code. * _For example, "The algorithm here can be optimized for better performance."_ * _**Buggy**__:_ PRs that introduce new bugs or issues into the codebase i.e. comments highlighting bugs, regressions, or issues that break existing functionality. * _For example, "This change breaks the login functionality."_ * _**Controversial**__:_ PRs that generate significant debate or disagreement among reviewers i.e. comments that show differing opinions or disputes on the implementation, approach, or necessity of the changes. * _For example, "I don't think this approach is the best solution."_ #### [hashtag](https://docs.hivel.ai/using-hivel/pull-request/comments-categorization#type-2) **Type 2:** * _**Code Quality**__:_ Comments focused on the overall design, architecture, and cleanliness of the code i.e. feedback related to code organization, modularity, adherence to design patterns, and overall structural improvements. * _For example, "This module should be broken down into smaller, more manageable components."_ * _**Readability**__:_ Comments aimed at improving the readability of the code and the adequacy of its documentation i.e. feedback about code clarity, naming conventions, comments within the code, and the presence and quality of documentation. * _For example, "Variable names should be more descriptive."_ * _**Testing**__:_ Comments that address the sufficiency and quality of tests and error handling mechanisms. Suggestions or concerns regarding unit tests, integration tests, error handling, edge cases, and the robustness of the code against failures. * _For example, "Error handling is not sufficient here; consider adding more checks."_ * _**Compliance**__:_ Comments that ensure the code adheres to industry standards, coding guidelines, and best practices i.e. feedback on adherence to coding standards, security practices, regulatory compliance, and the use of recommended libraries or frameworks. * _For example, "This code doesn't comply with our security guidelines."_ * _**Maintainability:**_ Comments that focus on the long-term maintenance and scalability of the code. Suggestions for making the code easier to maintain, extending its functionality, or improving performance to handle larger scale or more complex operations. * _For example, "This code will be hard to maintain; consider refactoring."_ #### [hashtag](https://docs.hivel.ai/using-hivel/pull-request/comments-categorization#type-3-special-cases-for-categorization) **Type 3: Special Cases for Categorization:** * When a comment consists of a single word, it is categorized as a _"__**One Word Comment**__"_. * If a pull request has no comments, it is categorized as _"__**No Comment**__"_. * When a pull request cannot be categorized based on its comments due to various reasons, it is categorised as _**"No Value"**_. **Wherever applicable, each PR will be categorized into either one or two of the above types. For example -** * "Looks good to me. Well done on keeping the code clean and efficient!" * Categories: _**LGTM, Code Quality**_ * “Consider refactoring this function to reduce its complexity and improve readability.” * Categories: _**Refactor, Readability**_ * “There's a bug in the validation logic. Please fix it before merging” * Categories: _**Buggy**_ * "Looks good to me. Well done on keeping the code clean and efficient!" "Can you add more comments to this section for better understanding?" * Categories: _**LGTM, Readability**_ * "There's a bug in the validation logic. Please fix it before merging." "Make sure to add unit tests to cover this scenario." * Categories: _**Buggy, Testing**_ ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fyl69xDZplcuJ9FcR9y5S%252FScreenshot%25202024-09-10%2520at%25203.56.22%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D20953499-f9a9-4630-a4c5-94f653afba73&width=768&dpr=3&quality=100&sign=9bca0986&sv=2) _Examples_ **Please note:** For this feature to work, we process the metadata through AI. If you cannot see this column in the Pull Request screen, please contact our support team at [\[email protected\]arrow-up-right](https://support@hivel.ai/) [PreviousPull Requestchevron-left](https://docs.hivel.ai/using-hivel/pull-request) [NextReview Cycleschevron-right](https://docs.hivel.ai/using-hivel/pull-request/review-cycles) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Coding | Hivel As we all may agree that engineering productivity cannot be measured by lines of code, it’s important to gain visibility into the percentage of code spent across various categories - **New Work**, **Maintenance**, and **Rework**. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FVfUtnbzlcDWhhcfk8Nqf%252Fimage.png%3Falt%3Dmedia%26token%3D65de74f0-a55f-4907-bd6b-d3145d97e85b&width=768&dpr=3&quality=100&sign=2484e49f&sv=2) ### [hashtag](https://docs.hivel.ai/using-hivel/coding#every-line-of-code-is-classified-into-3-categories-as-explained-below) **Every line of code is classified into 3 categories, as explained below:** #### [hashtag](https://docs.hivel.ai/using-hivel/coding#new-work) New Work New Work is the amount of work newly created, or in other words launching new features. Every new line of code that’s written is called New Work and this measures the innovation percentage spent by the team. **How to use this data on a regular basis?** * When the business is aiming to focus on innovation, watch out this space if the efforts are being put in the right direction * Do you have a complex legacy project and delivering new features is being delayed? This metric can show you to make your strategic move. #### [hashtag](https://docs.hivel.ai/using-hivel/coding#rework) Rework Rework as the name suggests is working on something, and then modifying or deleting it. But, there’s a catch. Anything we build ought to be modified/deleted, but doing so within 30 days of writing the code originally is what’s classified as rework. Why 30 days? Most agile teams have a 2 - 3 week sprint cycle and a code rewritten within 30 days can cover all possible cases of rework listed here. **What are the causes for rework?** * You write it first, and then polish it for performance or ease of maintenance * Fix features based on bugs reported in QA or Prod * Deliver the feature and then learn about changing scope or requirements * Or, something works on your local, but throws errors when integrated with systems While a certain amount of rework is normal for any team, watching out for increased rework in a given time can help address issues earlier in the process. #### [hashtag](https://docs.hivel.ai/using-hivel/coding#maintenance) Maintenance Maintenance or refactoring or tech debt is required for any teams and is classified as code that’s modified/deleted which was originally written prior to 30 days. While most teams take time to work on tech debt, it’s inevitable to modify some old code while building new features. It’s helpful to watch the repos/projects causing most maintenance, monitor ROI of such projects and take up corrective actions. **What are the causes for maintenance?** * Complex architecture can make building new features harder without touching old code * Update applications to newer technologies or changing business requirements * Reduce code-bloat by removing unnecessary features/code that’s not in use anymore. circle-info For a more detailed explanation on how New Work, Rework, and Maintenance work, please refer to [**this article**](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance) . * * * #### [hashtag](https://docs.hivel.ai/using-hivel/coding#how-to-use-this-data-on-a-regular-basis) **How to use this data on a regular basis?** The first step is to baseline the numbers for each team to see the percentage of new work, rework, maintenance and collaboration. And then, monitor for trends to see if the team’s work is reflecting your initiatives and goals. #### [hashtag](https://docs.hivel.ai/using-hivel/coding#what-can-be-a-few-things-to-watch-out-for) **What can be a few things to watch out for?** High maintenance could be a signal for tech debt. High rework can be a signal to demand better requirements. circle-info Refer [here](https://docs.hivel.ai/using-hivel/pull-request/how-to-exclude-outlier-commits-and-prs) to know how to exclude certain PRs and commits from the calculation. [PreviousGoalschevron-left](https://docs.hivel.ai/using-hivel/goals) [NextUnderstanding Rework, New Work, and Maintenancechevron-right](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How are Active Days calculated | Hivel For this calculation, we consider any GIT activity, such as regular commits, merge commits, and PRs opened, reviewed, merged, and declined. The **active day value** indicates, on average, how many days out of a seven-day week a person or team has been active. Weekends are included in the calculation to ensure any work that happens during that time is also accounted for. circle-info If the duration is >= 7 : **Active days** \=(CurrentActiveDays / (Selected time frame) / CurrentActiveAuthors) \* 7 If the duration is < 7 : **Active days** =(CurrentActiveDays / (Selected time frame) / CurrentActiveAuthors) \*1 ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F0WY3zMmIY1kTpZJH0box%252Fimage.png%3Falt%3Dmedia%26token%3Da2a35259-5bc0-4f32-9e39-9d4dd7b20e78&width=768&dpr=3&quality=100&sign=731cd435&sv=2) Active days on Cockpit ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FV0BSWj831wdFlUcFv7El%252Fimage.png%3Falt%3Dmedia%26token%3Dc6582260-062a-4aa0-9a51-06c47cbcdd81&width=768&dpr=3&quality=100&sign=2b50631f&sv=2) Active days on Activity screen **For example:** (Time frame: February 1st - 10th) * If the team worked for 10 days in February, and you have 3 active authors contributing to the work. Active days = (10/10/3) \* 7 = 2.3 * If the team worked for only 5 days in February, and you have 2 active authors contributing. • Active days = (5/10/2) \* 1 = 0.25 [PreviousNew Work%chevron-left](https://docs.hivel.ai/metrics-and-definitions/throughput/new-work) [NextPRs Open, PRs Ready to Review or Mergechevron-right](https://docs.hivel.ai/metrics-and-definitions/throughput/prs-open-prs-ready-to-review-or-merge) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Best Practices | Hivel Unlock the full potential of Hivel’s integrations by following these best practices. This guide is designed to help you streamline your workflows, boost team collaboration, and achieve consistent, impactful results. Whether you're optimizing for efficiency, minimizing errors, or ensuring smooth coordination across tools, these best practices will set your team up for success. Dive in to discover strategies that elevate both your integration experience and your overall productivity. * * * [🎖️Best Practices for Software Development Efficiencychevron-right](https://docs.hivel.ai/best-practices/best-practices-for-software-development-efficiency) [🧹Jira Best Practiceschevron-right](https://docs.hivel.ai/best-practices/jira-best-practices) [message-botBest practices for AI usagechevron-right](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage) [glassesAI usage - PR checklist + Prompt Cookbook + Cursor Ruleschevron-right](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules) [PreviousCode Telemetry FAQschevron-left](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs) [NextBest Practices for Software Development Efficiencychevron-right](https://docs.hivel.ai/best-practices/best-practices-for-software-development-efficiency) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Dev360 | Hivel The Dev360 screen provides a comprehensive monthly view of a developer's activity in terms of GIT activities. This screen is particularly useful for gaining insights into the active days and throughput of a developer, which can be valuable during one-on-one discussions. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fr7FWV3kGCDuV1sNK0xYl%252Fimage.png%3Falt%3Dmedia%26token%3D4ffdc988-323e-4755-84a6-f6a8ccaddd64&width=768&dpr=3&quality=100&sign=21cd7ca2&sv=2) This screen shows the number of days a developer was involved in any GIT activity, such as commits, PRs (Pull Requests) opened, reviewed, merged, or declined. This visibility helps in understanding a developer's engagement and productivity over a given period. **Filtering Activities:** You can filter the view based on specific activities like Commits, PRs Reviewed, etc. **Detailed View:** Clicking on any bubble within the filtered view will provide basic details of that particular activity and a link to it. ### [hashtag](https://docs.hivel.ai/using-hivel/dev360#filters-available-in-dev360) Filters Available in Dev360 #### [hashtag](https://docs.hivel.ai/using-hivel/dev360#general-filters) General Filters * **Teams**: Select the relevant team to filter the developers accordingly. * **Users**: Choose the specific user to view their activities. * **Date**: Set the desired date period to see activities within that timeframe. #### [hashtag](https://docs.hivel.ai/using-hivel/dev360#activity-specific-filters) Activity-Specific Filters * **Commits**: Shows all regular commits done by the user within the selected date period. * **Merge Commits**: Displays merge commits done by the user in the selected date period. * **PRs Open**: Filters out the PRs that were opened by the user within the selected date period. * **PRs Reviewed**: Lists the PRs reviewed by the user during the selected date period. * **PRs Merged**: Shows the PRs merged by the user within the selected date period. * **PRs Declined**: Filters out the PRs that were declined by the user in the selected date period. ### [hashtag](https://docs.hivel.ai/using-hivel/dev360#how-to-get-to-dev-360) How to get to Dev 360 There are 2 ways in which you can access Dev360: 1. Straight from the main Hivel left panel. 2. By selecting one user in Activity or Cockpit. [PreviousTeam Pulsechevron-left](https://docs.hivel.ai/using-hivel/team-pulse) [NextWork Item Breakdownchevron-right](https://docs.hivel.ai/using-hivel/work-item-breakdown) Last updated 6 months ago * [Filters Available in Dev360](https://docs.hivel.ai/using-hivel/dev360#filters-available-in-dev360) * [How to get to Dev 360](https://docs.hivel.ai/using-hivel/dev360#how-to-get-to-dev-360) sun-brightdesktopmoon sun-brightdesktopmoon --- # AI Adoption | Hivel AI Adoption helps you track how actively your teams are using AI coding tools across your organization. Using usage data from tools like GitHub Copilot and Cursor, this section surfaces clear metrics such as who is using AI, how often it is used, and how adoption is trending over time. Use the Copilot and Cursor subarticles to understand exactly what each metric means, how the data is collected, and how to read these views to understand AI adoption across teams. [user-pilot-tieCopilot Adoptionchevron-right](https://docs.hivel.ai/ai-adoption/copilot-adoption) [GitHub Copilot: Expanded Metrics Guidechevron-right](https://docs.hivel.ai/ai-adoption/copilot-adoption/github-copilot-expanded-metrics-guide) [computer-mouse-scrollwheelCursor Adoptionchevron-right](https://docs.hivel.ai/ai-adoption/cursor-adoption) [Cursor: Expanded Metrics Guidechevron-right](https://docs.hivel.ai/ai-adoption/cursor-adoption/cursor-expanded-metrics-guide) [PreviousPRs Open, PRs Ready to Review or Mergechevron-left](https://docs.hivel.ai/metrics-and-definitions/throughput/prs-open-prs-ready-to-review-or-merge) [NextCopilot Adoptionchevron-right](https://docs.hivel.ai/ai-adoption/copilot-adoption) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Goals | Hivel [hashtag](https://docs.hivel.ai/using-hivel/goals#using-goals-in-hivel) 🎯 Using Goals in Hivel ---------------------------------------------------------------------------------------------------- The **Goals** feature in Hivel helps you set clear targets, track progress, and assess performance at both the **organization** and **team** levels. Whether you're aligning teams around strategic objectives or tracking key performance metrics, Goals provides the visibility and accountability to stay on track. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDq4KgWMVM2Xddqep0Wi1%252Fimage.png%3Falt%3Dmedia%26token%3Dfa1a23f9-9558-4764-a366-c6faa4f4fa71&width=768&dpr=3&quality=100&sign=2362ec28&sv=2) * * * ### [hashtag](https://docs.hivel.ai/using-hivel/goals#where-to-find-goals) 📍 Where to Find Goals You can access Goals Pro from the main navigation: > **Overview → Goals (pro)** * * * ### [hashtag](https://docs.hivel.ai/using-hivel/goals#creating-an-organization-level-goal) 🏢 Creating an Organization-Level Goal ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F8Oz4dMD6FJ98L0RxRphm%252Fimage.png%3Falt%3Dmedia%26token%3D4154de90-6d01-4428-8807-a081f06ae2b6&width=768&dpr=3&quality=100&sign=e0828192&sv=2) 1. Navigate to the **Goals (pro)** page. 2. Click **Set Goals**. 3. Select a **frequency**: * Monthly * Quarterly 4. Select the metrics you want to track by clicking on them. 5. Enter your **target value** for each metric. * The initial value will also be available for reference - the initial value of a metric is calculated by taking into account the time period of last completed quarter or last completed month, based on the frequency selected. * If industry benchmark data is available, it will appear here for comparison. 6. Click **Save & Continue**. * * * ### [hashtag](https://docs.hivel.ai/using-hivel/goals#creating-a-team-level-goal) 👥 Creating a Team-Level Goal Follow the same steps as above, with one addition: * **Select the team** the goal applies to. * * * ### [hashtag](https://docs.hivel.ai/using-hivel/goals#viewing-progress) 📊 Viewing Progress ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDq4KgWMVM2Xddqep0Wi1%252Fimage.png%3Falt%3Dmedia%26token%3Dfa1a23f9-9558-4764-a366-c6faa4f4fa71&width=768&dpr=3&quality=100&sign=2362ec28&sv=2) The Goals dashboard displays real-time progress for each metric: * **Metric Name** * **Initial Value** (at the start of the goal) * **Current Value** * **Target Value** * **Progress:** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FkSbDWiqgV560ERveZK0t%252Fimage.png%3Falt%3Dmedia%26token%3D846ea27d-315b-4e3a-a0f1-cfce5a6e8ad7&width=768&dpr=3&quality=100&sign=53b2e675&sv=2) * * * ### [hashtag](https://docs.hivel.ai/using-hivel/goals#modifying-goals) ✏️ Modifying Goals ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F09nNcgwga8SU6s22Wy3l%252Fimage.png%3Falt%3Dmedia%26token%3Da0d64072-3fa1-4f17-9c90-1cd4ec034d90&width=768&dpr=3&quality=100&sign=ca39a522&sv=2) You can update ongoing goals: 1. Open the goal's dashboard. 2. Click **Modify Goal**. 3. Update existing metric values or add new metrics. > ⚠️ **Note:** You cannot change the goal’s duration. * * * ### [hashtag](https://docs.hivel.ai/using-hivel/goals#deleting-goals) 🗑️ Deleting Goals ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FaWO7qLOfWvKP682k1lW7%252FScreenshot%25202025-09-03%2520at%25203.28.45%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Df0362cac-f199-4fe2-8586-367b7a0bd5fd&width=768&dpr=3&quality=100&sign=30ea5562&sv=2) Only **ongoing goals** can be deleted: 1. Open the goal dashboard. 2. Click **Delete Goal**. 3. Confirm deletion when prompted: _“The goal set will be completely deleted and cannot be retrieved. Are you sure you want to proceed?”_ > ⚠️ **Warning:** This action is permanent and will remove all associated metrics. * * * ### [hashtag](https://docs.hivel.ai/using-hivel/goals#view-history-of-the-past-goals-and-performance) ⏳ View History of the past goals and performance ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FBwRJoYnghIYIJGjz2V4C%252Fimage.png%3Falt%3Dmedia%26token%3D01670234-5921-42cc-9f2c-7c3898233178&width=768&dpr=3&quality=100&sign=267871fd&sv=2) Through this, you will be able to see what were the previous months/quarters goals and how much progress was made towards those goals. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FrUjuaCQ2ECnroiCyaBfr%252F03%2520-%2520Visiting%2520History%2520State.png%3Falt%3Dmedia%26token%3D0a051195-91ac-4acd-be6d-8727e528dfdf&width=768&dpr=3&quality=100&sign=8991b7e2&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FTgrr2oDBYMAGj2WnJIWx%252F04%2520-%2520Visiting%2520History%2520State.png%3Falt%3Dmedia%26token%3Db9467beb-0fe6-4a80-ab85-729dd1ab75d5&width=768&dpr=3&quality=100&sign=82bb1b91&sv=2) To download the goals and their progress into an excel, you can do that through the [Download Reports section](https://docs.hivel.ai/using-hivel/cockpit/how-to-download-reports) under Settings. [PreviousProcesschevron-left](https://docs.hivel.ai/using-hivel/process) [NextCodingchevron-right](https://docs.hivel.ai/using-hivel/coding) Last updated 2 months ago * [🎯 Using Goals in Hivel](https://docs.hivel.ai/using-hivel/goals#using-goals-in-hivel) * [📍 Where to Find Goals](https://docs.hivel.ai/using-hivel/goals#where-to-find-goals) * [🏢 Creating an Organization-Level Goal](https://docs.hivel.ai/using-hivel/goals#creating-an-organization-level-goal) * [👥 Creating a Team-Level Goal](https://docs.hivel.ai/using-hivel/goals#creating-a-team-level-goal) * [📊 Viewing Progress](https://docs.hivel.ai/using-hivel/goals#viewing-progress) * [✏️ Modifying Goals](https://docs.hivel.ai/using-hivel/goals#modifying-goals) * [🗑️ Deleting Goals](https://docs.hivel.ai/using-hivel/goals#deleting-goals) * [⏳ View History of the past goals and performance](https://docs.hivel.ai/using-hivel/goals#view-history-of-the-past-goals-and-performance) sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Merge Frequency | Hivel ### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/release-merge-frequency#release-merge-frequency) **Release Merge Frequency** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FyHAsZUF4rPhNEqSqcS2R%252FScreenshot%25202025-11-27%2520at%25206.06.58%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D0521d2a0-7ade-49cd-9d64-5bc8a12bb09f&width=768&dpr=3&quality=100&sign=efc6111e&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/release-merge-frequency#formula) Formula = * Release Merge frequency measures how often code is merged to the main/master branch. Elite Release Merge Frequency represents a stable and healthy delivery. * This metric would help you understand the number of PRs being pushed to production in a given time. This can work independently of your sprint cycle time. You can learn more about them [herearrow-up-right](https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance) . * Too low Release Merge frequency indicates that there may be bottlenecks in review, or requirements, and teams are delivering features at a slower pace. * High Release Merge frequency shows that your team can quickly provide value and react to feedback or changes. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/release-merge-frequency#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FP2DHq5C1WqoLuLsNIud9%252Fimage.png%3Falt%3Dmedia%26token%3Db10d5e6a-9643-45c2-88fa-b1ec03747e61&width=768&dpr=3&quality=100&sign=2517f145&sv=2) [PreviousMerge Timechevron-left](https://docs.hivel.ai/metrics-and-definitions/speed/merge-time) [NextQualitychevron-right](https://docs.hivel.ai/metrics-and-definitions/quality) Last updated 3 months ago sun-brightdesktopmoon Copy (Total number of PRs merged to master or main in that selected time period) / (Total number of days in the time period) sun-brightdesktopmoon --- # Pickup time | Hivel Pickup time refers to the duration between when a PR was opened to when the first comment was done on the PR. This metric is an essential part of understanding a team's responsiveness and efficiency in handling code reviews. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FVBpHI01w1dXvh1QWsXqC%252Fimage.png%3Falt%3Dmedia%26token%3Da9423ec5-51e1-41d1-b239-9cba36c02bc5&width=768&dpr=3&quality=100&sign=70a0a265&sv=2) This metric can also be found in the Process screen and is the average of all PRs with at least 1 comment. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FJxgyLzSI27LpVhoRHETK%252Fimage.png%3Falt%3Dmedia%26token%3D152ecee6-e9de-42d9-a337-d3ec24380e38&width=768&dpr=3&quality=100&sign=5b0f3ef0&sv=2) circle-info For calculation of Pickup time, only the PRs with at least 1 comment are considered. PRs without any comments are excluded. Pickup time measures how quickly team members engage with a new pull request. A shorter pickup time often indicates a more active and responsive development team, which can lead to faster integration of changes. Faster pickup times can lead to shorter cycle times, as the PR spends less time idle, waiting for initial feedback. A focus on Pickup time can lead to a more efficient review process, reducing the overall cycle time and improving the software development lifecycle. The Pickup time can be 0 if there are no comments in the PR. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/pickup-time#related-articles) Related articles [Why is pickup time not included in cycle time?chevron-right](https://docs.hivel.ai/faqs/metrics-and-data-faqs/why-is-pickup-time-not-included-in-cycle-time) [PreviousCoding Timechevron-left](https://docs.hivel.ai/metrics-and-definitions/speed/coding-time) [NextReview Timechevron-right](https://docs.hivel.ai/metrics-and-definitions/speed/review-time) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Coding Time | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FRYVqHaSIWv4N0CcyebLJ%252FScreenshot%25202025-11-27%2520at%25205.33.27%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D96332627-be14-4343-827e-570e06494e86&width=768&dpr=3&quality=100&sign=e4193292&sv=2) **Coding Time is the time it takes from the first commit until a PR is open.** * Short Coding Time represents less context switching by developers, small PR size and clear requirements, and great architecture. * Longer coding time relates to committing large chunks of code, which could lead to a higher blast radius on production issues, longer review cycles, or sometimes even misses the review process due to fatigue. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/coding-time#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FQfawW6fQ7mArxrrUvpPy%252Fimage.png%3Falt%3Dmedia%26token%3Df9364a4f-0ffb-4723-b915-f554a1a7fccd&width=768&dpr=3&quality=100&sign=4c8ef2f6&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/coding-time#related-articles) Related articles [What to do if my Coding Time is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-coding-time-is-high) [Are draft PRs considered for calculation of coding/cycle time?chevron-right](https://docs.hivel.ai/faqs/metrics-and-data-faqs/are-draft-prs-considered-for-calculation-of-coding-cycle-time) [PreviousCycle Timechevron-left](https://docs.hivel.ai/metrics-and-definitions/speed/cycle-time) [NextPickup timechevron-right](https://docs.hivel.ai/metrics-and-definitions/speed/pickup-time) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Speed | Hivel [How to improve Speed?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed) [How to balance speed and quality?chevron-right](https://docs.hivel.ai/improve-performance/how-to-balance-speed-and-quality) [PreviousMetrics & Definitionschevron-left](https://docs.hivel.ai/metrics-and-definitions) [NextCycle Timechevron-right](https://docs.hivel.ai/metrics-and-definitions/speed/cycle-time) Last updated 6 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Review Time | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F34TZkLvb1JJkWn4rzFxc%252FScreenshot%25202025-11-27%2520at%25206.02.26%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D9863f3cb-f3d9-42ff-a9d8-4301e83fee5d&width=768&dpr=3&quality=100&sign=69f74f26&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/review-time#review-time-is-the-time-it-takes-a-pr-to-be-reviewed-since-its-open) Review Time is the time it takes a PR to be reviewed since it's Open. * Low Review Time represents highly collaborative team dynamics, with reviewers moving things faster and delivering higher-quality features to customers. * High review time represents limited reviewers in the team, and every occupied senior engineer not finding time to do code reviews slows down the cycle times. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/review-time#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FuHPRskeI3E6hoI958rU6%252Fimage.png%3Falt%3Dmedia%26token%3Daa6ebf81-044a-41bb-bbef-133aadc57f89&width=768&dpr=3&quality=100&sign=e2f70cac&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/review-time#related-article) Related article [What to do if my Review Time is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-review-time-is-high) [PreviousPickup timechevron-left](https://docs.hivel.ai/metrics-and-definitions/speed/pickup-time) [NextMerge Timechevron-right](https://docs.hivel.ai/metrics-and-definitions/speed/merge-time) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # New Work% | Hivel circle-info [**Understand New Work, Rework, Maintenance through examples**](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance) **Total lines of code added or modified.** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F4PkgeXC2E3M84QjNnO8i%252FScreenshot%25202025-11-28%2520at%252012.57.51%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D5db35edd-4a13-45c3-851e-b6087bb6e200&width=768&dpr=3&quality=100&sign=1c7b2656&sv=2) * Low % of New Work indicates the team is trying to change old code even to build new features, which will impact the implementation of high blast radius and poor solid principles. A **low percentage of New Work** means the team is often changing old code, even when building new features. This can lead to more bugs and make the code harder to manage. It may be a sign that the **architecture needs improvement**. It's a signal to review the architecture. * More New Work, along with slight [Rework](https://docs.hivel.ai/metrics-and-definitions/quality/rework) and [Maintenance](https://docs.hivel.ai/metrics-and-definitions/quality/maintenance) is always a good sign, as it indicates solid practices are in place, and the team can go ship new features at a faster pace as code is isolated. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/throughput/new-work#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FcLHefYkdxX0wkRQVqX4w%252Fimage.png%3Falt%3Dmedia%26token%3D746bd0a7-332d-414e-9916-620546851591&width=768&dpr=3&quality=100&sign=75be6c05&sv=2) [PreviousThroughputchevron-left](https://docs.hivel.ai/metrics-and-definitions/throughput) [NextHow are Active Days calculatedchevron-right](https://docs.hivel.ai/metrics-and-definitions/throughput/how-are-active-days-calculated) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # PRs Open, PRs Ready to Review or Merge | Hivel ### [hashtag](https://docs.hivel.ai/metrics-and-definitions/throughput/prs-open-prs-ready-to-review-or-merge#prs-open) PRs Open circle-info **Definition:** "PRs Open" is a throughput metric that counts the total number of PRs that were opened for review during a specific time period you select. **Time Dependency:** This metric is tied to the selected timeframe. It includes all PRs opened within that period, even if they have already been reviewed and merged. You can find this metric in Cockpit, Dashboards, Activity, Dev360, and set Goals for this metric. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FXLOA6kF5EDKwKuOTQ7CJ%252Fimage.png%3Falt%3Dmedia%26token%3Ddfb8c473-304f-4a6b-9210-5da64fc3b679&width=768&dpr=3&quality=100&sign=f42274b2&sv=2) ### [hashtag](https://docs.hivel.ai/metrics-and-definitions/throughput/prs-open-prs-ready-to-review-or-merge#prs-ready-to-merge-or-review) PRs Ready to Merge or Review circle-info **Definition:** "Ready to Review" and "Ready to Merge" are filters used on the Pull Request screen to display only those PRs that are currently open, meaning they have not yet been reviewed or merged. **Independent of time filters:** These filters are not bound by any timeframe. It dynamically shows all PRs still awaiting review or merge as of now, regardless of when they were created. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FE3Sx8Q35ig43hSJS3Dnw%252FScreenshot%25202025-11-28%2520at%25201.02.15%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D816b8295-6641-4c2c-8a62-75d73fa8ce9e&width=768&dpr=3&quality=100&sign=76db3d10&sv=2) [PreviousHow are Active Days calculatedchevron-left](https://docs.hivel.ai/metrics-and-definitions/throughput/how-are-active-days-calculated) [NextAI Adoptionchevron-right](https://docs.hivel.ai/ai-adoption) Last updated 1 month ago * [PRs Open](https://docs.hivel.ai/metrics-and-definitions/throughput/prs-open-prs-ready-to-review-or-merge#prs-open) * [PRs Ready to Merge or Review](https://docs.hivel.ai/metrics-and-definitions/throughput/prs-open-prs-ready-to-review-or-merge#prs-ready-to-merge-or-review) sun-brightdesktopmoon sun-brightdesktopmoon --- # Best Practices for Software Development Efficiency | Hivel Streamlining your software development process isn't just about writing code; it's about creating a cohesive, efficient workflow. By adhering to these best practices, you'll not only enhance code quality and team collaboration but also achieve the most insightful visualizations on Hivel, ensuring your projects stay on track and transparent. 1. **Keep it Bite-Sized:** Aim for code chunks under 400 lines. Smaller segments are your friends—they're easier to digest, test, and keep bug-free. Few companies go as low as 80 lines per PR. 2. **Kick Off with Commits**: Create a separate branch for each feature development task. As soon as you have a logical conclusion, do a commit - commit early and often. Avoid bundling all changes into a single, large pull request at the end of development. 3. **Peer-Reviews:** Implement a review branch configuration to ensure all PRs are reviewed by someone other than the author before merging. This process helps catch errors, improve code quality, and maintain consistency. Dedicate focused time to PR reviews, especially for larger changes, as thorough reviews are crucial for preventing production bugs and reducing technical debt. Aim for 100% PR review coverage, prioritizing quality over speed to maintain high code standards. 4. **Quality Over Speed:** When reviewing PRs, take your time, especially with the larger ones. A thorough review today saves a headache (and a bug) tomorrow. Avoid flashy reviews (reviewing large chunks of code in few minutes). 5. **Track and Plan:** Always use story points, assignees, and epics in your Jira tickets. It's not just paperwork; it's about making your work visible and planning effectively. No story points for tickets means reduced velocity for work being done, which is like getting no credit for your hard work. 6. **Connect the dots:** Include the Jira ticket ID in your commits and Pull Requests. It creates a clear trail linking your code changes to specific tasks, making it easier to understand the context and purpose of modifications. This practice ensures all your work is properly documented and accounted for, enhancing traceability and project management. 7. **Merge over Squash**: Use merge commits when integrating changes to maintain a clear history, preserving the context of individual modifications and making it easier to track the evolution of features over time. 8. **Embrace Testing:** Write tests for your code, including unit, integration, and end-to-end tests. Testing ensures your code does what it's supposed to do and helps catch issues early. While it may sound like slowing down, it actually will speed up the overall process. 9. **Keep It Clean:** When building new features, refactor surrounding code to improve readability and maintainability. Pay special attention to areas or repositories experiencing frequent rework, as these are prime candidates for refactoring. Regular refactoring keeps your codebase clean, reduces technical debt, and makes development more efficient in the long run. 10. **Document Wisely:** Write clear, concise documentation for your code and features. Good documentation helps others understand your work and saves time when revisiting old code. 11. **Engage in Dialogue:** Leaving comments on the PR is a good practice that encourages open discussion, provides clarity on decisions made, and creates a record of the thought process behind the code changes. 12. **Tag that hotfix!** Implement a systematic approach to differentiate hotfix PRs from regular ones. We suggest using 'hotfix'-related keywords in branch names or adding specific labels to hotfix PRs for easy identification later on. 13. **Sprint Ready: Plan, Tag, and Launch!** Before kicking off any sprint, aim to plan and tag most work to sprints. This gives developers clear visibility into upcoming tasks, allowing them to hit the ground running when the sprint starts. 14. **Distinguish production vs. non-production bugs:** Establish a way to distinguish between production issues and in-sprint issues to improve prioritization and resolution. Common approaches include using a field to tag whether an issue is a production or in-sprint issue, or using separate issue types for each. [PreviousBest Practiceschevron-left](https://docs.hivel.ai/best-practices) [NextJira Best Practiceschevron-right](https://docs.hivel.ai/best-practices/jira-best-practices) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Throughput | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FCVBV3lQktVGIeDQpnP34%252FHivel%2520-%2520Throughput%2520Board%2520%281%29.png%3Falt%3Dmedia%26token%3D19c977b4-3b2d-4b1c-b894-fa7a4bc8d0b8&width=768&dpr=3&quality=100&sign=ba11c3d1&sv=2) Throughput screen measures volume of work #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/throughput#these-are-the-metrics-present-in-this-section) These are the metrics present in this section: * **Average PR size** : Average number of lines modified during a selected time period * **Commits**: Number of commits pushed. * **PRs Open**: Pull Requests (PR) opened during the selected time period. * **PRs Merged**: The number of PR merged in the selected time period. * [**New Work%**](https://docs.hivel.ai/metrics-and-definitions/throughput/new-work) : It shows the total lines of code added or modified. * **Closed Issue Count** : Number of issues closed * **Completed story points : Number of** story points completed * [**Active Days**](https://docs.hivel.ai/metrics-and-definitions/throughput/how-are-active-days-calculated) : Average number of days in a week that a user/team is active on GIT. * **Codebase Changes** : The lines of code that were added , removed or modified. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/throughput#related-articles) Related articles [How to improve planning and throughputchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-planning-and-throughput) [How to track, manage, and reduce technical debt?chevron-right](https://docs.hivel.ai/improve-performance/how-to-track-manage-and-reduce-technical-debt) [Why do some metrics like PRs reviewed or merged have more than 100%?chevron-right](https://docs.hivel.ai/faqs/metrics-and-data-faqs/why-do-some-metrics-like-prs-reviewed-or-merged-have-more-than-100) [PreviousPRs > 400 LoCchevron-left](https://docs.hivel.ai/metrics-and-definitions/quality/prs-greater-than-400-loc) [NextNew Work%chevron-right](https://docs.hivel.ai/metrics-and-definitions/throughput/new-work) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Team Pulse | Hivel Make your standup calls more effective, data-driven, and short - saving time for everyone on the call. If you can save 15 mins of your standup call with a team of 8, that’s the bandwidth of an extra full resource to build your next big thing. This screen gives you a bird’s eye view of all the activity by your team, allowing you to see any traces of burnout or disproportionate workloads, anticipate risks like disengagement signals, by the amount of activity done, and see patterns based on previous weeks. #### [hashtag](https://docs.hivel.ai/using-hivel/team-pulse#you-can-use-data-on-this-screen-to) **You can use data on this screen to:** * Make your stand up calls more effective by seeing what happened already, rather than asking the team during the call * Make your retros more data driven by identifying patterns like burnout, idle time waiting for requirements or QA reports * Monitor your average commits per week to get a sense of trends * Monitor active engineer days to identify their flow zones and peak days #### [hashtag](https://docs.hivel.ai/using-hivel/team-pulse#metrics-and-what-they-mean) **Metrics and what they mean** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FMAabreUDPoOKZH72GjAr%252Fimage.png%3Falt%3Dmedia%26token%3D7a1a8095-78c1-48cd-9073-7a3d81382fa4&width=768&dpr=3&quality=100&sign=219e29ee&sv=2) * **Active Days** is a good metric to see how many days per week your team is actively engaged in commits or PR-related activities. Engineers without any activity are excluded from this metric and shown separately. * Refer [**here**](https://docs.hivel.ai/metrics-and-definitions/throughput/how-are-active-days-calculated) for calculation of active days. * **Avg. commits** filters out only the commits and shows the trend and patterns in workload. * **Inactive Engineers** can clearly show if any engineers are working on non-programming activities like design, architecture, or off from work for that duration. * **Commits**: Shows all regular commits done by the user within the selected date period. * **Merge Commits**: Displays merge commits done by the user in the selected date period. * **PRs Open**: Filters out the PRs that were opened by the user within the selected date period. * **PRs Reviewed**: Lists the PRs reviewed by the user during the selected date period. * **PRs Merged**: Shows the PRs merged by the user within the selected date period. * **PRs Declined**: Filters out the PRs that were declined by the user in the selected date period. [PreviousUnderstanding Rework, New Work, and Maintenancechevron-left](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance) [NextDev360chevron-right](https://docs.hivel.ai/using-hivel/dev360) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Configurations | Hivel The Configurations screen in Hivel provides the flexibility to adjust various settings, ensuring that metrics are calculated accurately according to your organization's practices. Here are the sections in Configurations screen: [](https://docs.hivel.ai/configurations/branch-configurations) Branch Configurations [](https://docs.hivel.ai/configurations/general-configurations) General Configurations [](https://docs.hivel.ai/configurations/hotfix-configurations) Hotfix Configurations [](https://docs.hivel.ai/configurations/metric-behaviour) Metric Behaviour [](https://docs.hivel.ai/configurations/exclusions) Exclusions [](https://docs.hivel.ai/configurations/investment-configurations) Investment Configurations Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Set Up | Hivel [Sign Upchevron-right](https://docs.hivel.ai/set-up/sign-up) [Userschevron-right](https://docs.hivel.ai/set-up/users) [Teamschevron-right](https://docs.hivel.ai/set-up/teams) [Access Managementchevron-right](https://docs.hivel.ai/set-up/access-management) [Labelschevron-right](https://docs.hivel.ai/set-up/labels) [Team Versioningchevron-right](https://docs.hivel.ai/set-up/team-versioning) [PreviousRepositorieschevron-left](https://docs.hivel.ai/configurations/repositories) [NextSign Upchevron-right](https://docs.hivel.ai/set-up/sign-up) sun-brightdesktopmoon sun-brightdesktopmoon --- # GitHub Copilot: Expanded Metrics Guide | Hivel GitHub Copilot offers insights into user activity through its **Copilot Metrics API**, which aggregates telemetry data from the IDE. These metrics are provided by GitHub, and Hivel’s platform visualizes them. Below is a guide to understanding these metrics and their key definitions. * * * #### [hashtag](https://docs.hivel.ai/ai-adoption/copilot-adoption/github-copilot-expanded-metrics-guide#metric-categories) 🔍 **Metric Categories** These categories break down how Copilot metrics are measured: **Area** **Metrics Covered** **Adoption** Assigned seats, Active users **Engagement** Suggestions shown, Suggestions accepted, Active days per user **Effectiveness** Acceptance rate (lines accepted vs suggested), Total lines suggested/accepted **Usage Depth** IDE vs Chat completions, average usage per day * * * #### [hashtag](https://docs.hivel.ai/ai-adoption/copilot-adoption/github-copilot-expanded-metrics-guide#key-metric-definitions) 🧮 **Key Metric Definitions** **✅ Total Lines Suggested** * **Definition**: The total number of lines suggested by GitHub Copilot, including inline, block, or multi-line completions. * **Tracked Per**: User, per day **✅ Total Lines Accepted** * **Definition**: The lines from Copilot suggestions that the user accepts explicitly via IDE interactions (e.g., pressing Tab or Enter). * **Tracked Per**: User, per day * **Notes**: Even if the accepted suggestion is later deleted, it is still logged. **✅ Acceptance Rate** * **Formula**: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FiHlKK6eG12CqqMY7Puwv%252Fimage.png%3Falt%3Dmedia%26token%3Df95647da-d80b-443f-893b-f232fb064a43&width=768&dpr=3&quality=100&sign=d80a8820&sv=2) * **Definition**: The percentage of suggested lines that were accepted. This metric is a measure of adoption, not quality. * **Implications**: A higher acceptance rate may indicate better alignment with developer intent or greater usability. * * * #### [hashtag](https://docs.hivel.ai/ai-adoption/copilot-adoption/github-copilot-expanded-metrics-guide#user-classification) 👥 **User Classification** **✅ Active Users** * **Definition**: A user who has received at least one suggestion or has interacted with Copilot Chat on that day. **⚠️ No formal “Passive” User Metric** * **How to Identify**: You can estimate passive behavior by checking for: * A seat is assigned but no suggestions received or accepted in the last X days. * No threshold (e.g., 10 lines/day) is explicitly set for activity. * * * #### [hashtag](https://docs.hivel.ai/ai-adoption/copilot-adoption/github-copilot-expanded-metrics-guide#technical-foundations) 🧱 **Technical Foundations** * **Telemetry**: GitHub tracks usage metrics using telemetry from the user’s IDE (with opt-in). * **Finalization**: Metrics are finalized at the end of each UTC day and have a 1-day lag. * **Rolling Window**: Data is available for up to 28 days of history. **⚠️ Known Limitations** **Scenario** **Counted in Metrics?** **Notes** **Full suggestion accepted via Tab/Enter** ✅ Yes Counts as accepted lines. **Partially accepted suggestions (some lines only)** ✅ Yes (partial) Only the accepted lines are logged. **Copy-pasting suggestion content (manual)** ❌ No Only interactions via IDE UI are counted. **Rewriting code based on AI inspiration** ❌ No GitHub does not capture intent through telemetry. **Accepting a suggestion, then deleting it soon after** ✅ Yes The deletion may not be fully filtered out, possibly inflating adoption slightly. **Using Copilot in offline mode** ❌ No No telemetry is captured, so no metrics are logged. **Chat suggestion used but edited before insertion** ❌/⚠️ Ambiguous Depends on how the chat event was logged in the system. **Summary**: Copilot metrics may not capture the full extent of AI influence, as partial usage, copy-pasting, and inspiration-driven code revisions are not tracked. * * * #### [hashtag](https://docs.hivel.ai/ai-adoption/copilot-adoption/github-copilot-expanded-metrics-guide#sample-copilot-api-payload) 📦 **Sample Copilot API Payload** Here’s an example of a typical API payload with metrics: In this example: * **21 active users** interacted with Copilot. * **5,800 lines** were suggested in total. * **1,640 lines** were accepted. * The **acceptance rate** is **28.27%**. * * * This guide provides an overview of the key metrics available via GitHub Copilot. By understanding these metrics, you can better track adoption, engagement, effectiveness, and usage depth of Copilot in your development environment. [PreviousCopilot Adoptionchevron-left](https://docs.hivel.ai/ai-adoption/copilot-adoption) [NextCursor Adoptionchevron-right](https://docs.hivel.ai/ai-adoption/cursor-adoption) Last updated 7 months ago sun-brightdesktopmoon Copy jsonCopy{ "timestamp": "2025-07-29", "active_users": 21, "total_code_lines_suggested": 5800, "total_code_lines_accepted": 1640, "acceptance_rate": 28.27 } sun-brightdesktopmoon --- # Copilot Adoption | Hivel circle-info Follow [these steps](https://docs.hivel.ai/integrations/ai-tools/github-copilot-integration) for integrating Copilot The **Copilot Adoption** feature in Hivel provides you with valuable insights into the usage and effectiveness of GitHub Copilot within your organization. It helps you track how teams are interacting with Copilot, whether it is being used actively, and whether it is adding tangible value to your development. [hashtag](https://docs.hivel.ai/ai-adoption/copilot-adoption#usage-activity) **Usage Activity** ---------------------------------------------------------------------------------------------------- This section helps you track the overall interaction with GitHub Copilot, segmented into two categories: * **Active Users**: These are users who have interacted directly with Copilot by providing at least one instruction or input (e.g., typing a request or command for Copilot to process). * **Passive Users**: These users have not directly interacted with Copilot by providing input, but they have accepted at least one suggestion from Copilot (e.g., using an auto-completion suggestion without actively prompting Copilot). ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FJPPCnLtuPBTggTSOHOUU%252Fimage.png%3Falt%3Dmedia%26token%3D34e74b45-6861-4d06-8f54-8891d9a7c377&width=768&dpr=3&quality=100&sign=3d80a84e&sv=2) **Graph:** * The **Usage Activity** graph shows a daily trend for both **Active** and **Passive** users. * The graph helps you track the **adoption rate** of GitHub Copilot across the organization. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FVEbtUHjqyyBiDJQ2LoKV%252Fimage.png%3Falt%3Dmedia%26token%3D87f116ba-4ecd-44d9-8ec0-6a9300a183db&width=768&dpr=3&quality=100&sign=986f651c&sv=2) **Average Users:** By examining the Average Active and Passive users, you get a clear picture of how many people are actively or passively engaging with Copilot. * * * [hashtag](https://docs.hivel.ai/ai-adoption/copilot-adoption#suggestions-acceptance) **Suggestions Acceptance** -------------------------------------------------------------------------------------------------------------------- This section provides insights into the acceptance of Copilot suggestions by developers. It answers key questions like: * How many suggestions are actually being accepted? * Which programming languages are seeing the most value from Copilot? **Graph:** * The graph breaks down suggestion acceptance rates by **programming language**. * You can view the acceptance data in two formats: * **Percentage**: The acceptance rate of suggestions in each language. * **Raw Numbers**: This could be either the **number of suggestions** accepted or the **number of lines** of code that have been auto-completed by Copilot. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FAQN9oL4LE6wcTIDZVUS7%252Fimage.png%3Falt%3Dmedia%26token%3Db23d7b8a-fa72-495e-9239-698f8927a14f&width=768&dpr=3&quality=100&sign=38a8a303&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FkqXAjohDTIk5VPZQXvvJ%252Fimage.png%3Falt%3Dmedia%26token%3D1b62a3eb-9455-4a7c-9c82-f4c939e340e9&width=768&dpr=3&quality=100&sign=532f4b4e&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fb9jIlOhlwcKixmgq0xva%252Fimage.png%3Falt%3Dmedia%26token%3D83500a0b-9fb0-43d0-827f-c49914d8ac5a&width=768&dpr=3&quality=100&sign=7d7c1cab&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F9JRmSqHpSf1X9HLRKC6a%252Fimage.png%3Falt%3Dmedia%26token%3D97335987-153a-4a23-affd-f74a1ff92f17&width=768&dpr=3&quality=100&sign=a893e9b2&sv=2) **Languages:** * By default, the top **10 languages** (based on suggestion volume) are displayed in the graph. However, you can adjust the filter to view suggestions for specific languages or to focus on different parameters. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F1nrKob0jJTpmWVgxDseQ%252Fimage.png%3Falt%3Dmedia%26token%3D33277c83-4c62-4aa2-bf80-641c11282c5a&width=768&dpr=3&quality=100&sign=c3679987&sv=2) * * * circle-info **Why this matters** This data helps you make informed decisions about whether to encourage further Copilot adoption or provide training and support to improve usage across teams. [PreviousAI Adoptionchevron-left](https://docs.hivel.ai/ai-adoption) [NextGitHub Copilot: Expanded Metrics Guidechevron-right](https://docs.hivel.ai/ai-adoption/copilot-adoption/github-copilot-expanded-metrics-guide) Last updated 10 months ago * [Usage Activity](https://docs.hivel.ai/ai-adoption/copilot-adoption#usage-activity) * [Suggestions Acceptance](https://docs.hivel.ai/ai-adoption/copilot-adoption#suggestions-acceptance) sun-brightdesktopmoon sun-brightdesktopmoon --- # Hivel AI Impact Screen: Overview & Insights | Hivel ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#overview) Overview Hivel’s **AI Impact** helps give teams a clear and practical signal to reason about AI usage over time. It is designed to help teams see patterns and trends in shipped code. While tools like Cursor and Copilot track AI usage (e.g., code suggestions or completions), they don’t measure whether the AI-generated code actually reaches **production**. In contrast, **Hivel’s Code Telemetry** tracks AI-generated code that is **merged and shipped** to production, providing a real-world measure of AI adoption and its impact on developer productivity. ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#ai-impact) AI Impact The **AI Impact** view provides a directional measure of AI contribution by analyzing code changes and classifying code blocks as **AI-generated** or **human-written**. #### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#what-youll-see) What you’ll see * **AI vs. human classification** for code at a PR level * **Confidence score** for the classification * **Aggregated trends** for a clearer team-level view ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FEC6fTJTNjPVsvvfhKClK%252Fadasdsadds.png%3Falt%3Dmedia%26token%3Db8300a07-01a3-48ef-81c9-4408f2aee772&width=768&dpr=3&quality=100&sign=39924716&sv=2) ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#why-teams-use-this-view) Why teams use this view Many AI dashboards measure tool activity. Hivel goes a step further by measuring **production outcomes** by focusing on code that has moved through review and been merged. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FcUnotBMrGLv8nGTmhhJH%252Fijn.png%3Falt%3Dmedia%26token%3Da6ffd323-4b22-41a6-b159-52a87f1af616&width=768&dpr=3&quality=100&sign=e90f34bd&sv=2) ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#user-adoption-categories) User adoption categories To help you quickly understand adoption at the individual level, Hivel groups users into categories based on AI usage within the selected time range. * **Inactive**: 0% * **Occasional**: 1–30% * **Moderate**: 31–70% * **Heavy**: 71–100% By default, the analysis covers the **last 2 days**, with an option to run a **historical sync** to understand past trends. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FBqyjBESpLi1Ze5A0Rze1%252Fhbhh.png%3Falt%3Dmedia%26token%3D02a5409c-cc1c-4748-8054-8c0d9888fccb&width=768&dpr=3&quality=100&sign=d3700f24&sv=2) ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#trends-over-time) Trends over time The screen also highlights how adoption changes over time. * **Team AI usage trends**: understand which teams are leading adoption and where additional enablement may help. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FARyw5Lk5SzJN7xIbacwh%252Fiojp.png%3Falt%3Dmedia%26token%3Dfc067d0c-5bab-4ef7-b103-16bdaa773b63&width=768&dpr=3&quality=100&sign=4db33f29&sv=2) * **Developer distribution trends**: see how usage is distributed across developers and how it shifts over time. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FxiZlU0WkDdQY9YKmbowD%252Fvggvg.png%3Falt%3Dmedia%26token%3D1bd8957b-0993-47dd-ae1b-90422e687294&width=768&dpr=3&quality=100&sign=1dbb47b7&sv=2) ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#common-questions) Common questions #### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#why-might-hivel-show-lower-ai-usage-than-other-dashboards) Why might Hivel show lower AI usage than other dashboards? In most cases, discrepancies are caused by one of the following: 1. **Unmerged pull requests** (only merged code is included). 2. **Processing delays** for very large PRs. 3. **Commits details have not been processed for some reason**, which blocks telemetry collection. 4. **Historic data has not been synced**, which can limit comparisons. ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#how-the-confidence-score-is-summarized) How the confidence score is summarized * Code blocks within a PR are analyzed individually. * At the PR level, the confidence score generally scales with the amount of code in the PR. In practice, larger PRs tend to yield higher confidence, while smaller PRs tend to yield lower confidence. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FGueQbT0yEwDBbYE7YWUQ%252Fqwqw.png%3Falt%3Dmedia%26token%3D579dd9a8-42d9-4b60-bd91-1c1c5d119530&width=768&dpr=3&quality=100&sign=b22ad4af&sv=2) ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#conclusion) Conclusion Hivel’s AI Impact Screen provides a practical, production-focused way to understand AI usage across teams and developers, so you can scale AI tooling with clarity and confidence. [PreviousCursor: Expanded Metrics Guidechevron-left](https://docs.hivel.ai/ai-adoption/cursor-adoption/cursor-expanded-metrics-guide) [NextCode Telemetry FAQschevron-right](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs) Last updated 1 month ago * [Overview](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#overview) * [AI Impact](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#ai-impact) * [Why teams use this view](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#why-teams-use-this-view) * [User adoption categories](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#user-adoption-categories) * [Trends over time](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#trends-over-time) * [Common questions](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#common-questions) * [How the confidence score is summarized](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#how-the-confidence-score-is-summarized) * [Conclusion](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights#conclusion) sun-brightdesktopmoon sun-brightdesktopmoon --- # Understanding Rework, New Work, and Maintenance | Hivel First let us understand what does each of the metric mean: #### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#maintenance) **Maintenance**: Maintenance is the lines of code modified that were written before the last 30 days. This is also synonymous with Refactor or Tech Debt. Copy Maintenance Percentage = (lines of code modified that were written prior to 30 days) / (total lines of code added or modified) * It is 30 days by default but is configurable in the settings page. #### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#rework) **Rework**: Rework refers to the changes made to code that was initially written within the last 30 days. It provides insights into the stability and quality of recent code changes. This can usually happen due to developer fixing QA bugs or responding to PR review feedback. Copy Rework Percentage = (lines of code modified that were written in the last 30 days) / (total lines of code added or modified) #### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#new-work) **New Work**: It shows the total lines of code added or modified. Copy New Work Percentage = (lines of code that were written in the specified duration) / (total lines of code added or modified) ### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#here-are-some-scenarios-to-help-you-understand-the-differences-between-rework-new-work-and-maintenan) Here are some scenarios to help you understand the differences between Rework, New Work, and Maintenance (for the examples we will consider "T" as today): ### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4dqp1y4x0eje94b53x3v07) **Scenario 1:** 2 lines of code were removed and replaced by 5 lines **Before: T** **After: T + 10** **Rework** : **2**, since the lines were deleted/modified within 10 days **New Work** : **5**, since in total 5 lines were added to the code **Maintenance** : **0** ### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4f1q3cfdemgyeh7vzw64p9) **Scenario 2:** 3 lines are added in before 1 line (the original 1 line is moved to last) **Before: T** **After: T + 60** **Rework** : **0**, since there are no modifications in the existing lines of code **Maintenance** : **0**, since there are no modifications in the existing lines of code **New Work** : **3**, these are fresh lines of code and no changes were made to the existing lines, it will only be considered in New Work and not Rework or Maintenance. ### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4f3g1bc8z1k9hs0qp4r6xk) **Scenario 3:** _**Case 1: Five lines of code were written 5 months ago and were modified today.**_ _**Case 2: Additional changes will be made to the same lines 10 days from now.**_ * For the first case, since the original code was written 5 months ago, it will be considered as Maintenance. * For the second case, since it is an updated version of the code and changes were done >10 days ago, it will be considered as Rework. ### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4swzvwrph0fdx0d08gqbzn) **Scenario 4:** A whitespace was added to one line, and the code was indented on another line **Before: T** **After: T + 80** **Rework** : **0**, whitespaces and indentations do not get considered as change **Maintenance** : **0**, whitespaces and indentations do not get considered as change **New Work** : **0**, since there were no additions to the lines ### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4t84g0wgrdwqfaaxbq27n6) **Scenario 5:** I made some changes in .settings file, will those also be tracked in calculation? * For our processing and calculations, we automatically exclude files and directories that start or end with the following: `.settings`, `dist`, `tmp`, `out-tsc`, `node_modules`, `bower_components`, `.idea`, `typings`, `.vscode`, `vendor/`, `coverage`. * Additionally, if any files contain the following in their paths, they are also excluded: `src`, `assets`, `images`. * All of these options can be adjusted on the settings page, where you can also specify additional files to be excluded. ### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#h_01hz4brgza025dfbjhbgdbhq0j) **Scenario 6:** 1 word from 1 line was deleted **Before: T** **After: T + 20** **Rework** : **1**, since modification was made to code within 20 days **New Work** : **1**, since any change other than a complete line deletion is considered an edit **Maintenance** : **0** ### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4d53q9h8pdw61zhfvw3dmf) **Scenario 7:** 1 word from 1 line was deleted and replaced with another 1 word **Before: T** **After: T + 60** **Rework** : **0**, since no modifications were made within Rework period **Maintenance** : **1**, since modifications were made to code post the Rework period of 30 days **New Work** : **1**, since each character replaced or added in any line of code is considered as New Work ### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4dchyakhr9r41defvf0fnz) **Scenario 8:** 2 words from 1 line were deleted and replaced by 1 word **Before: T** **After: T + 5** **Rework : 1** * since modifications were made to the code within the Rework period of 30 days * the LoC changed is 1 since we only consider the lines of code where changes were made, not the number of characters **New Work** : **1**, since something was added to the line of code **Maintenance : 0** ### [hashtag](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4dfqx1qn71x5jryhzcgjrg) **Scenario 9:** 3 words were added towards the end of 1 existing line of code **Before: T** **After: T + 90** **Maintenance** : **1** * since modifications were made to the code post the Rework period * even though the code was added at the end, it is still part of a line of code and therefore will be considered as a change. **New Work** : **1**, since something was added to the line of code **Rework : 0** For more information or assistance, please contact our support team at [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#f98a8c8989968b8db991908f9c95d79890) . [PreviousCodingchevron-left](https://docs.hivel.ai/using-hivel/coding) [NextTeam Pulsechevron-right](https://docs.hivel.ai/using-hivel/team-pulse) Last updated 1 month ago * [Here are some scenarios to help you understand the differences between Rework, New Work, and Maintenance (for the examples we will consider "T" as today):](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#here-are-some-scenarios-to-help-you-understand-the-differences-between-rework-new-work-and-maintenan) * [Scenario 1: 2 lines of code were removed and replaced by 5 lines](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4dqp1y4x0eje94b53x3v07) * [Scenario 2: 3 lines are added in before 1 line (the original 1 line is moved to last)](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4f1q3cfdemgyeh7vzw64p9) * [Scenario 3:](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4f3g1bc8z1k9hs0qp4r6xk) * [Scenario 4: A whitespace was added to one line, and the code was indented on another line](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4swzvwrph0fdx0d08gqbzn) * [Scenario 5: I made some changes in .settings file, will those also be tracked in calculation?](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4t84g0wgrdwqfaaxbq27n6) * [Scenario 6: 1 word from 1 line was deleted](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#h_01hz4brgza025dfbjhbgdbhq0j) * [Scenario 7: 1 word from 1 line was deleted and replaced with another 1 word](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4d53q9h8pdw61zhfvw3dmf) * [Scenario 8: 2 words from 1 line were deleted and replaced by 1 word](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4dchyakhr9r41defvf0fnz) * [Scenario 9: 3 words were added towards the end of 1 existing line of code](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance#id-01hz4dfqx1qn71x5jryhzcgjrg) sun-brightdesktopmoon Copy let a = 10; let b = a * 2; Copy let a = 10; let b = 0; if (a > 0) b = a * 2; else b = 1; Copy let total = 100; Copy let discount = 10; let tax = 5; let subtotal = 90; let total = 100; Copy if(a > b){ return a; } Copy if (a > b) { // Added a whitespace between 'if' and the parenthesis return a; // Indented this line by an extra tab } Copy let greeting = "Hello, World!"; Copy let greeting = "Hello!"; Copy let greeting = "Hello, World!"; Copy let greeting = "Hello, Everyone!"; Copy let status = "Task is pending"; Copy let status = "Pending"; Copy let message = "Hello"; Copy let message = "Hello, how are you"; sun-brightdesktopmoon --- # Work Item Breakdown | Hivel The Work Item Breakdown enables engineering leaders, managers, and teams to analyze issue creation patterns across multiple Jira projects in one unified view. Unlike the traditional single-project issue tab, this dashboard gives users the flexibility to select multiple Jira projects, filter by issue types, and group the data over time (weekly, monthly, quarterly) - all while offering insights in both graphical and tabular formats. #### [hashtag](https://docs.hivel.ai/using-hivel/work-item-breakdown#you-can-either-group-by-duration) You can either group by duration: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FOHb4BusGlfI6sYr6gXIT%252Fimage.png%3Falt%3Dmedia%26token%3Dd139c3a6-4a33-4f33-a1e5-126ce16fe44c&width=768&dpr=3&quality=100&sign=b63d80fe&sv=2) #### [hashtag](https://docs.hivel.ai/using-hivel/work-item-breakdown#or-group-by-projects) Or group by projects: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FCPItS7vi1Tb4gvVfWyz9%252Fimage.png%3Falt%3Dmedia%26token%3D36795c15-cbcc-4ada-b599-f823bb8549dd&width=768&dpr=3&quality=100&sign=bcea430a&sv=2) [hashtag](https://docs.hivel.ai/using-hivel/work-item-breakdown#how-it-helps-teams) 🔍 How It Helps Teams -------------------------------------------------------------------------------------------------------------- * Spot Workload Trends * Track how issue volume changes over time * Identify spikes is specific during key releases * Compare Projects * View issue distribution across multiple Jira projects * Detect teams with high bug-to-feature ratios * Identify Quality Issues * Focus only on bugs to catch recurring or post-release problems * Monitor bug inflow vs. resolution pace [PreviousDev360chevron-left](https://docs.hivel.ai/using-hivel/dev360) [NextCoding Hotspotschevron-right](https://docs.hivel.ai/using-hivel/coding-hotspots) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Performance Appraisal | Hivel The Performance Appraisal screen in Hivel is a powerful tool that allows you to compare the performance of developers or teams using various key metrics. This feature helps you quickly identify where each individual or team stands and if there are any bottlenecks in specific areas. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FiFaEOmGwvdLW8IKTbCvP%252FGIF%2520Recording%2520Feb%252011%25202025.gif%3Falt%3Dmedia%26token%3D8afc030e-a0b5-4247-8507-e7bde968a911&width=768&dpr=3&quality=100&sign=93efeda3&sv=2) * **Compare Multiple Users**: Evaluate the performance of multiple users to understand individual contributions and identify areas for improvement. * **Compare Multiple Teams**: Assess the performance of different teams to recognize overall team productivity and collaboration effectiveness. * **Compare Users and Teams**: Compare the performance of individual users against their respective teams to see how each individual stacks up against the team's performance. #### [hashtag](https://docs.hivel.ai/using-hivel/performance-appraisal#with-this-visibility-you-can) With this visibility you can: * **Identify Bottlenecks:** Quickly spot areas where developers or teams might be facing challenges. * **Promote Fair Evaluation**: Ensure fair and comprehensive performance evaluations by comparing relevant metrics. #### [hashtag](https://docs.hivel.ai/using-hivel/performance-appraisal#the-performance-appraisal-screen-uses-the-following-metrics-to-provide-a-comprehensive-view-of-perfo) The Performance Appraisal screen uses the following metrics to provide a comprehensive view of performance: `**PR Open**` | `**Cycle Time**` | `**Commits**` | `**Coding Time**` | `**Merge Time**` | `**Review Time**` [PreviousHivel Quadrantchevron-left](https://docs.hivel.ai/using-hivel/hivel-quadrant) [NextAlerts in Hivelchevron-right](https://docs.hivel.ai/using-hivel/alerts-in-hivel) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Hotfix Rate | Hivel Hotfix Rate is defined as the percentage of changes to a production or live environment to fix any degraded service. In other words, hotfixes to address production bugs. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FukEFBYEaZjPlVQ6bXQqK%252FScreenshot%25202025-11-28%2520at%252012.20.45%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Dbebb6671-316f-4b78-91b2-7cfcf7c991f9&width=768&dpr=3&quality=100&sign=2e6ed297&sv=2) The way Hivel identifies the PRs to be considered for CFR is through the configurations - through pull request patterns, JIRA issue types, or by patch version pattern. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FjOffWADVoRNnFFp4K6g1%252Fimage.png%3Falt%3Dmedia%26token%3D68e9d953-655f-4019-b318-95bd926fa5d7&width=768&dpr=3&quality=100&sign=6dd5f5cc&sv=2) circle-info Please note: **the PRs considered for Hotfix Rate are a subset of the total PRs deployed to release branches.** Know more about how to setup the configurations [herearrow-up-right](https://hivel.gitbook.io/knowlegebase/setup/configurations-explained/hotfix-configurations) . #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/hotfix-rate#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FLiFM8rojWkMq474nIHxk%252Fimage.png%3Falt%3Dmedia%26token%3D49054fc8-b52d-40cb-8477-fc6084db8775&width=768&dpr=3&quality=100&sign=c51fc37b&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/hotfix-rate#related-article) Related article [How to identify root cases of high change failure rates?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/how-to-identify-root-cases-of-high-change-failure-rates) [Building a feedback loop for continuous code improvementchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/building-a-feedback-loop-for-continuous-code-improvement) [PreviousQualitychevron-left](https://docs.hivel.ai/metrics-and-definitions/quality) [NextHotfix Resolution Timechevron-right](https://docs.hivel.ai/metrics-and-definitions/quality/hotfix-resolution-time) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # PRs > 400 LoC | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FbRKYEAoD88K4jwJXfs5w%252FScreenshot%25202025-11-28%2520at%252012.54.47%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D53da18ff-b74f-429e-b76e-9a3ace5957e9&width=768&dpr=3&quality=100&sign=9ba403b6&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/prs-greater-than-400-loc#if-the-number-of-lines-added-and-modified-in-a-pr-exceeds-400-its-classified-as-prs-greater-than-400) If the number of lines added and modified in a PR exceeds 400, it's classified as PRs > 400 LoC. * PRs > 400 LoC take longer to review, are harder to roll back, and can cause more merge conflict issues. Developers are encouraged to keep PRs smaller, which can move things faster in the pipeline. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/prs-greater-than-400-loc#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fy3zrUcREvbV7rlefDcXp%252Fimage.png%3Falt%3Dmedia%26token%3D1e7d4d76-b63a-4a59-8afa-507e67828fe7&width=768&dpr=3&quality=100&sign=e655535b&sv=2) [PreviousFlashy Reviewschevron-left](https://docs.hivel.ai/metrics-and-definitions/quality/flashy-reviews) [NextThroughputchevron-right](https://docs.hivel.ai/metrics-and-definitions/throughput) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Sign Up | Hivel [How to sign up to Hivel?chevron-right](https://docs.hivel.ai/set-up/sign-up/how-to-sign-up-to-hivel) [PreviousSet Upchevron-left](https://docs.hivel.ai/set-up) [NextHow to sign up to Hivel?chevron-right](https://docs.hivel.ai/set-up/sign-up/how-to-sign-up-to-hivel) sun-brightdesktopmoon sun-brightdesktopmoon --- # Cycle Time | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F1M5VUREkLxoWedGo26FN%252FScreenshot%25202025-11-27%2520at%25205.23.57%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Ddb953d9d-0d1f-47a1-a735-6e990e3b66cc&width=768&dpr=3&quality=100&sign=cfb72d75&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/cycle-time#cycle-time-is-the-time-it-takes-from-the-first-commit-to-pr-merged) Cycle time is the time it takes from the first commit to PR merged. * If things are taking too long to release, it can impact the competitiveness of the product in the market, and customers may be waiting too long for requests. * With the very smooth delivery system in place, things are moving rapidly. At this pace, even if we see production issues, things can be fixed faster, which is great for teams experimenting with new ideas. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/cycle-time#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FbV7bBqdWDai0mWLwCTW1%252Fimage.png%3Falt%3Dmedia%26token%3D28ff67f2-88fa-4f36-b900-79c8807feaed&width=768&dpr=3&quality=100&sign=1452f8fa&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/cycle-time#related-articles) Related articles [What to do if my Cycle Time is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high) [Are draft PRs considered for calculation of coding/cycle time?chevron-right](https://docs.hivel.ai/faqs/metrics-and-data-faqs/are-draft-prs-considered-for-calculation-of-coding-cycle-time) [Why is there an abnormal spike in Cycle Time?chevron-right](https://docs.hivel.ai/faqs/metrics-and-data-faqs/why-is-there-an-abnormal-spike-in-cycle-time) [Why cannot I see cycle time against developers even though they have commits?chevron-right](https://docs.hivel.ai/faqs/metrics-and-data-faqs/why-cannot-i-see-cycle-time-against-developers-even-though-they-have-commits) [PreviousSpeedchevron-left](https://docs.hivel.ai/metrics-and-definitions/speed) [NextCoding Timechevron-right](https://docs.hivel.ai/metrics-and-definitions/speed/coding-time) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Flashy Reviews | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FEUV9HkL3UY5ZCxRBWNOt%252FScreenshot%25202025-11-28%2520at%252012.53.46%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3De3b31d06-2f34-4d29-8b31-d9c759b7b889&width=768&dpr=3&quality=100&sign=6f8042a1&sv=2) Flashy Reviews % shows the percentage of Pull Requests larger than 200 Lines of Code merged with less than 5 minutes of review time. circle-info This threshold is [configurablearrow-up-right](https://hivel.gitbook.io/knowlegebase/setup/configurations-explained/branch-configurations#flashy-review) in the Settings screen. The more flashy reviews there are, the higher the chance of production bugs in the future because large PRs needed to be reviewed thoroughly before being merged. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/flashy-reviews#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FGEyt0d3fcmSmvZ3B6MSr%252Fimage.png%3Falt%3Dmedia%26token%3D87beb365-fcb3-447c-b777-293350f28d7e&width=768&dpr=3&quality=100&sign=5c00acac&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/flashy-reviews#related-article) Related article [What happens if there are too many Flashy Reviews and how to prevent them?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-happens-if-there-are-too-many-flashy-reviews-and-how-to-prevent-them) [PreviousPR Reviewedchevron-left](https://docs.hivel.ai/metrics-and-definitions/quality/pr-reviewed) [NextPRs > 400 LoCchevron-right](https://docs.hivel.ai/metrics-and-definitions/quality/prs-greater-than-400-loc) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Branch Configurations | Hivel The Branch Configuration page in Hivel allows you to fine-tune various aspects of your branch management, ensuring accurate tracking and reporting of your development activities. Here's a detailed guide on configuring your release branches, review branches, flashy review thresholds, and PR exclusions. #### [hashtag](https://docs.hivel.ai/configurations/branch-configurations#release-branch) Release Branch The Release Branch section lets you specify the main branches to be tracked for deployment frequency, change failure rate, and mean time to restore calculations. Ideally, these release branches represent the ones where pull requests are merged before being deployed to production - meaning any PR merged into these branches will eventually reach your live environment. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FYPTA0WR8o7Q1FfioEEvQ%252Fimage.png%3Falt%3Dmedia%26token%3D3a0d9a07-f98f-4a02-8314-7206ada54e37&width=768&dpr=3&quality=100&sign=a248b77a&sv=2) #### [hashtag](https://docs.hivel.ai/configurations/branch-configurations#review-branch) Review Branch The Review Branch section is where you designate branches that are usually used for review activites. These branches are where it is usually expected for the reviewers to approve the PRs after review. Only the PRs merged into these branches will be considered for metrics around reviews like PRs reviewed/unreviewed and Flashy Reviews. [PreviousConfigurationschevron-left](https://docs.hivel.ai/configurations) [NextGeneral Configurationschevron-right](https://docs.hivel.ai/configurations/general-configurations) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Maintenance | Hivel circle-info [**Understand New Work, Rework, Maintenance through examples**](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance) ### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/maintenance#maintenance) **Maintenance %** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FeUt0qYTm57WKq5HSgAYd%252Fimage.png%3Falt%3Dmedia%26token%3D5c3af87f-9402-46a2-82b7-489445ca3aea&width=768&dpr=3&quality=100&sign=e5c13ddd&sv=2) **Maintenance** refers to the lines of code modified that were written before the last 30 days / total lines of code added or modified. * Less maintenance means that engineers write a very well-maintainable piece of code as the team builds new features. * Higher maintenance represents a longer time to build new features or testing fatigue. When maintenance is high, estimates are usually off, as it's hard to account for maintenance during estimates. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/maintenance#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FgjnTDeB51mW7Cdgt3VrC%252Fimage.png%3Falt%3Dmedia%26token%3De9e35629-ec07-491f-9e3c-0420567967aa&width=768&dpr=3&quality=100&sign=c44b9298&sv=2) [PreviousHotfix Resolution Timechevron-left](https://docs.hivel.ai/metrics-and-definitions/quality/hotfix-resolution-time) [NextReworkchevron-right](https://docs.hivel.ai/metrics-and-definitions/quality/rework) Last updated 6 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Repositories | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDTZWDqM8bx7RVB2YZhEy%252Fimage.png%3Falt%3Dmedia%26token%3D85eec45d-4f63-4c4b-b3c7-9adfb910bc1b&width=768&dpr=3&quality=100&sign=4ae76e49&sv=2) On this configuration screen, you can control whether newly added repositories in your workspace are automatically processed and synced. You can also define repository patterns to exclude from processing. Instead of listing exact repository names, you may specify unique keywords with a wildcard character (\*) before or after the keyword. Any repository matching these patterns will be excluded on an ongoing basis. This approach is particularly useful when you need to exclude a large or frequently changing set of repositories without managing individual names manually. [PreviousInvestment Configurationschevron-left](https://docs.hivel.ai/configurations/investment-configurations) [NextSet Upchevron-right](https://docs.hivel.ai/set-up) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Quality | Hivel [How to improve Qualitychevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality) [How to balance speed and quality?chevron-right](https://docs.hivel.ai/improve-performance/how-to-balance-speed-and-quality) [PreviousRelease Merge Frequencychevron-left](https://docs.hivel.ai/metrics-and-definitions/speed/release-merge-frequency) [NextHotfix Ratechevron-right](https://docs.hivel.ai/metrics-and-definitions/quality/hotfix-rate) Last updated 6 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Hotfix Resolution Time | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FBrQn6Tg6eYJv8YTvy08c%252FScreenshot%25202025-11-28%2520at%252012.24.15%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Dbe433cac-7047-4ab3-a95b-0a59d494a7b0&width=768&dpr=3&quality=100&sign=7f861f65&sv=2) **Hotfix Resolution Time** is the average time taken to recover from a failure in production. On Hivel, it is measured as the **average cycle time of a Pull Request (PR) labeled as a hotfix**. In other words, the time taken for a hotfix PR from the first commit to when it is merged to the release branch. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/hotfix-resolution-time#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FXnQeU2Fzr1DLaskWeiyO%252Fimage.png%3Falt%3Dmedia%26token%3D0a9daee2-2c69-4e8a-8e27-760527be8c33&width=768&dpr=3&quality=100&sign=a99fdec6&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/hotfix-resolution-time#related-article) Related article [Strategies to Reduce Hotfix Resolution Timechevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time) [Building a feedback loop for continuous code improvementchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/building-a-feedback-loop-for-continuous-code-improvement) [PreviousHotfix Ratechevron-left](https://docs.hivel.ai/metrics-and-definitions/quality/hotfix-rate) [NextMaintenancechevron-right](https://docs.hivel.ai/metrics-and-definitions/quality/maintenance) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Merge Time | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FOrlFsC1ueR5SHH6e0RkD%252FScreenshot%25202025-11-27%2520at%25206.03.42%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D3a3c2ff0-0e1d-452c-8c46-bad21480be60&width=768&dpr=3&quality=100&sign=61622a66&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/merge-time#merge-time-is-the-duration-between-when-a-pull-request-is-reviewed-and-when-it-is-merged) Merge time is the duration between when a pull request is reviewed and when it is merged. * Faster merge (lower number) times represent efficient release processes. * Longer merge time could be due to inefficient CI/CD processes. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/merge-time#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FjUpS9vE2XcX2qjja79PI%252Fimage.png%3Falt%3Dmedia%26token%3D2ca5f611-5b2d-48b6-8c3b-c8bc2070a856&width=768&dpr=3&quality=100&sign=334c6131&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/speed/merge-time#related-article) Related article [What to do if my Merge Time is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-merge-time-is-high) [PreviousReview Timechevron-left](https://docs.hivel.ai/metrics-and-definitions/speed/review-time) [NextRelease Merge Frequencychevron-right](https://docs.hivel.ai/metrics-and-definitions/speed/release-merge-frequency) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Track hotfixes via patch version pattern | Hivel Any merged Pull Requests (PRs) with a PR title, Source branch, or PR tags containing a version number in the format **a.b.c...z** (where **z > 0**) can be identified as a hotfix. #### [hashtag](https://docs.hivel.ai/configurations/hotfix-configurations/track-hotfixes-via-patch-version-pattern#example) Example * `1.2.3 →` last number = 3 → hotfix * `2.0.0.0 →` last number = 0 → not a hotfix * `5.4.1.0.6 →` last number = 6 → hotfix ### [hashtag](https://docs.hivel.ai/configurations/hotfix-configurations/track-hotfixes-via-patch-version-pattern#h_01hywpdm3j2gk2m1v3k6scx17a) **Steps to Enable the Hotfix Flag** To start using this new hotfix pattern, you need to enable the corresponding flag in your organization's configuration settings. Follow these steps: 1. Navigate to the Configurations page within your Hivel dashboard. 2. Find the flag related to the new hotfix pattern. It will be listed among the available configuration options. 3. Switch the flag to "On" to enable the new hotfix pattern. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FqJ02OrS90hw5I7RRxnWU%252Fimage.png%3Falt%3Dmedia%26token%3D3ce15b40-8b0c-44ba-b173-c077eb9957b4&width=768&dpr=3&quality=100&sign=4ac12828&sv=2) Once the flag is enabled, the system will automatically recognize any merged PRs with a version number in the format as hotfixes. All current hotfix patterns will continue to function without interruption. Both the new and existing hotfix patterns will be recognized for calculation of "Hotfifx Rate" and "Hotfix Resolution Rate" metrics. For any further assistance or if you encounter issues, please contact our support team at [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#f2818782829d8086b29a9b84979edc939b) . [PreviousHotfix Configurationschevron-left](https://docs.hivel.ai/configurations/hotfix-configurations) [NextMetric Behaviourchevron-right](https://docs.hivel.ai/configurations/metric-behaviour) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Rework | Hivel circle-info [**Understand New Work, Rework, Maintenance through examples**](https://docs.hivel.ai/using-hivel/coding/understanding-rework-new-work-and-maintenance) ### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/rework#rework) **Rework %** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FUNznhGM7GO9JHrangXRH%252Fimage.png%3Falt%3Dmedia%26token%3D4bf521b3-7b6a-4d33-bf81-fe65d3d8cb09&width=768&dpr=3&quality=100&sign=8001a8ee&sv=2) **Rework %** measures the number of changes made to code in the last 30 days. If the change is made to a code older than 30 days, it is automatically classified as [maintenance](https://docs.hivel.ai/metrics-and-definitions/quality/maintenance) . (30 days is the default setting, you can configure it based on your internal process by going to **Settings -> Configuration**) * Low rework means the code changes aren't done after the initial work, which indicates that the developers are pushing high-quality code the first time. * High rework rates are caused by PR feedback, QA feedback, or an engineer trying to improve the code after committing. Too many changes. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/rework#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FAa9vzXT4xQnoatLQ2gw9%252Fimage.png%3Falt%3Dmedia%26token%3Da39ac163-0d2e-4cd0-afb4-46da8e093459&width=768&dpr=3&quality=100&sign=274b107c&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/rework#related-article) Related article [What to do if my Rework is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high) [PreviousMaintenancechevron-left](https://docs.hivel.ai/metrics-and-definitions/quality/maintenance) [NextUnreviewed PRschevron-right](https://docs.hivel.ai/metrics-and-definitions/quality/unreviewed-prs) Last updated 6 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Hotfix Configurations | Hivel In Hotfix configurations section you can specify the aspects of your SCM or project management tool based on which PRs should be considered for hotfix. These configurations majorly affect the calculations of Change Failure Rate and MTTR. #### [hashtag](https://docs.hivel.ai/configurations/hotfix-configurations#pull-request-pattern) Pull Request Pattern You can specify some patterns based on which PRs will be classified as hotfixes. These patterns can be enabled to be identified in any of the attributes such as PR labels, titles, descriptions, branches, tags. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F7CVmKaJIcPHUy6E2vhTa%252Fimage.png%3Falt%3Dmedia%26token%3D6afc1736-9fbb-49fa-8cd1-09c7c4683a0c&width=768&dpr=3&quality=100&sign=8e90097c&sv=2) #### [hashtag](https://docs.hivel.ai/configurations/hotfix-configurations#work-item-types) Work Item Types You can specify work item types that represent hotfixes. The PRs associated with these work items will be considered as hotfixes. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FE0aOnnrZsR9px9GHyHvP%252Fimage.png%3Falt%3Dmedia%26token%3Dcafbbde4-c0ad-4dde-97e8-4d5f5504a7dd&width=768&dpr=3&quality=100&sign=f66b4f7c&sv=2) #### [hashtag](https://docs.hivel.ai/configurations/hotfix-configurations#patch-version-pattern) Patch version pattern Any merged Pull Requests (PRs) with a PR title, Source branch, or PR tags containing a version number in the format x.y.z (where z > 0) can be identified as a hotfix. [Learn more about it](https://docs.hivel.ai/configurations/hotfix-configurations/track-hotfixes-via-patch-version-pattern) . [PreviousGeneral Configurationschevron-left](https://docs.hivel.ai/configurations/general-configurations) [NextTrack hotfixes via patch version patternchevron-right](https://docs.hivel.ai/configurations/hotfix-configurations/track-hotfixes-via-patch-version-pattern) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # General Configurations | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FscQuru28ULjFvRQX0bKZ%252Fimage.png%3Falt%3Dmedia%26token%3D386e3b12-99eb-4c1b-b686-2a91085c5b98&width=768&dpr=3&quality=100&sign=38404a3c&sv=2) #### [hashtag](https://docs.hivel.ai/configurations/general-configurations#benchmarking) Benchmarking This toggle enables the industry benchmarking for metrics to show up in the dashboard cards. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FzsQNf6YJfTY1aHchWo5R%252FGIF%2520Recording%2520July%252025%2520%281%29.gif%3Falt%3Dmedia%26token%3Db72a7804-9980-48d9-99a6-372a34cb4ea7&width=768&dpr=3&quality=100&sign=33b1cf37&sv=2) #### [hashtag](https://docs.hivel.ai/configurations/general-configurations#workspaces) Workspaces You can configure a bunch of repositories together to replicate the structure you have in your SCM. Once this is enabled, you will get an additional section of "Workspaces" where you can configure the repositories that should be considered for a workspace. Post this, you will be able to filter according to workspaces. #### [hashtag](https://docs.hivel.ai/configurations/general-configurations#landing-page) Landing Page Here, you can set the default landing page for the different roles. By default, if nothing is configured, everyone will land on the Cockpit when they log in. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FcgsFBna1dZQzwDtSVNBB%252Fimage.png%3Falt%3Dmedia%26token%3D26b295ed-1025-473e-94c0-5aa619661cbd&width=768&dpr=3&quality=100&sign=66c903f3&sv=2) [PreviousBranch Configurationschevron-left](https://docs.hivel.ai/configurations/branch-configurations) [NextHotfix Configurationschevron-right](https://docs.hivel.ai/configurations/hotfix-configurations) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Best practices for adopting Story Points | Hivel For a thoughtful perspective from Ron Jeffries, the originator of story points, you can read his take here: [**Ron Jeffries on Story Points**arrow-up-right](https://ronjeffries.com/articles/019-01ff/story-points/Index.html) chevron-right**What story points are (and what they are not)**[hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/best-practices-for-adopting-story-points#what-story-points-are-and-what-they-are-not) Before jumping into best practices, some important things to note: * Story points measure **relative effort, complexity, risk, and uncertainty**, not just time. * Over time, your team will build a velocity (story points completed per sprint) which helps you plan how much work to pull into future sprints. * Capacity is how much your team _can_ handle in a sprint, considering availability, meetings, maintenance/support overhead, etc. Story points + velocity allow you to map what your capacity looks like. Story Points embrace the idea of true Agile where teams accept that they must iterate quickly and adapt to unforeseen circumstances. It is important to remember that story points should never be rigidly linked to specific time values. They are and should always remain an estimate of **how large a task is and how risky it might be** - capturing complexity, uncertainty, and effort in a relative sense. 👉 That said, if at any point you notice that following strict story point hygiene is creating friction, feels complicated, or is not truly benefitting your team in representing effort, don’t hesitate to revert back to basics. In our journey, we have seen customers move fluidly between different approaches: from story points to time-based estimates, switching to T-shirt sizing, adopting Kanban tracking even while running internal sprints, or even dropping Jira entirely in favor of good old spreadsheets. The lesson here: **try not to force teams to use story points where they may not make sense.** Often the simplest and most effective practice is to break work down into deliverables small enough (1-3 days in size) that detailed estimation becomes unnecessary. * * * With that context in mind, the following sections outline **best practices to consider when moving to a story points-based development process** ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/best-practices-for-adopting-story-points#best-practices-recommendations-for-assigning-story-points-based-on-capacity) Best Practices / Recommendations for Assigning Story Points Based on Capacity Practice Recommendation Why it helps **Use a non-linear scale** (e.g. Fibonacci or modified Fibonacci) Use a sequence like 1, 2, 3, 5, 8, 13, 20 etc. You can cap or modify the higher numbers for your context. Non-linear increases acknowledge that as stories grow in size, uncertainty/risk tends to increase. It makes distinguishing large vs medium tasks more meaningful. [_A good related read_arrow-up-right](https://www.mountaingoatsoftware.com/blog/why-the-fibonacci-sequence-works-well-for-estimating) **Establish a baseline “reference story”** Pick a simple story (e.g. bug fix or small feature) that everyone agrees is “1 point.” Use that as anchor/reference. Compare all other stories relative to that. Helps calibrate what “1 point” actually means for your team. Without this, one person’s “3” may be another person’s “1”, making planning unreliable. This is widely recommended in agile estimation literature. **Use velocity (average over past 3-5 sprints) to determine capacity** Don’t guess how many points you’ll do; use past performance (velocity) to decide how much to commit. Adjust for holidays, support work, known overhead. It gives realistic limits; teams that do this avoid over-committing and burnout. **Factor in non-development/overhead work** Include time for meetings, code reviews, production support, maintenance, etc. That reduces your usable capacity. For example, if someone is allocated 30% support work, the rest should be for new stories. Without including these, estimates tend to assume 100% dev time, leading to overcommitment. Scrum / Agile coaches often mention treating these as explicit "non-story" work in sprint planning. **Limit story size; split large stories** If a story seems too big (e.g. takes more than half a sprint), break it down. Ensure most stories can be completed in a small number of days (1-3). Smaller stories are easier to estimate, reduce risk, reduce rollback. **Use Planning Poker or group estimation** Multiple team members estimate, discuss discrepancies, converge on a consensus. Helps uncover risks / unknowns. This is a standard practice: helps with shared understanding, surfacing hidden complexity. **Don’t map story points directly to hours** (or at least don’t rigidly enforce it) While some teams map approximate hours to small point values for planning (e.g. “1 story point ~ 2 hours”), these mappings should be loose and revisited. Strict time mapping defeats some of the purpose of story points (dealing with uncertainty). Many sources caution that hour-based equals can be misleading. **Use sprints as feedback loops** After each sprint, compare estimated vs actual performance. Review stories that took much longer than estimated to see what went wrong. Use those lessons to recalibrate future estimates. Improves estimation accuracy over time; reduces mismatch of expectations. **Don’t use points to measure individual performance** Measure team delivery: the team’s velocity and capacity vs commitments. Avoid attributing individual productivity to story points. If individuals are held to “X points per sprint,” it leads to gaming, splitting stories, inflating estimates. Several agile discussions and forums warn against this. **Adjust for new teams / changing context** New teams may not have reliable velocity. Projects with new domain or unknown tech will have extra uncertainty. Adjust your expectations (lower velocity, buffer) until data builds up. Helps avoid overcommitment early and burn-out. Also ensures planning doesn’t assume “steady state” when many variables are uncertain. ✌️Keep buzzing, keep building - one sprint at a time. [PreviousHotfix & Jira Integration - Best Practiceschevron-left](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices) [NextHow to Encourage Jira Hygiene Without Creating Frictionchevron-right](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction) Last updated 6 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Investment Configurations | Hivel #### [hashtag](https://docs.hivel.ai/configurations/investment-configurations#product-and-allocation-mapping) Product and Allocation Mapping This is where the fields for Product and Allocation can be set. Read more about the feature [here](https://docs.hivel.ai/using-hivel/investment/how-to-set-up-products-and-allocation-tabs-in-the-investment-screen) . ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FkD3Xuqlm1eL1ajatywRY%252Fimage.png%3Falt%3Dmedia%26token%3D99b193e7-a47d-4980-9dd0-b6e94068a4c5&width=768&dpr=3&quality=100&sign=7b402bc1&sv=2) #### [hashtag](https://docs.hivel.ai/configurations/investment-configurations#effort-data-type) Effort Data Type Define the effort type that is being used in your team. This will enable the metrics related to these to be calculated accordingly. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FIG37k9iZhmivBdyjpdV3%252Fimage.png%3Falt%3Dmedia%26token%3D96a072af-fc0b-4d8c-87f2-f86b1cbfe88a&width=768&dpr=3&quality=100&sign=e213c942&sv=2) [PreviousExclusionschevron-left](https://docs.hivel.ai/configurations/exclusions) [NextRepositorieschevron-right](https://docs.hivel.ai/configurations/repositories) Last updated 5 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Exclusions | Hivel These configurations enable you to auto exclude PRs and Commits from the metrics, based on certain conditions. #### [hashtag](https://docs.hivel.ai/configurations/exclusions#auto-exclude-prs-by-cycle-time) Auto Exclude PRs by Cycle Time Here you can set a threshold of cycle time days, and PRs having cycle time more than this will be excluded from all metrics. #### [hashtag](https://docs.hivel.ai/configurations/exclusions#auto-exclude-prs-by-pr-size) Auto Exclude PRs by PR Size Here you can set a threshold of PR size, and PRs having LoC more than this will be excluded from all metrics. #### [hashtag](https://docs.hivel.ai/configurations/exclusions#auto-exclude-prs-by-keywords) Auto Exclude PRs by Keywords Here you can set a keywords which will be searched in certain attributes of the Pull Request - Title, Description, Label - any PRs matching these criteria will be excluded from all metrics. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FNH4AVRVhPnG3SB1ZL3sJ%252Fimage.png%3Falt%3Dmedia%26token%3D32b146a8-f9fd-49b6-990a-c5106aa7c011&width=768&dpr=3&quality=100&sign=e3b93c72&sv=2) #### [hashtag](https://docs.hivel.ai/configurations/exclusions#auto-exclude-prs-by-branches) Auto Exclude PRs by Branches By setting branch patterns, you can configure that all PRs following the set path of source and destination branches will be auto excluded from all metrics. This can be done via 2 methods: * Many to Many mapping * One to One mapping ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FoJovcgZvdkWGU2tcEKRN%252FScreenshot%25202025-10-10%2520at%25205.20.01%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Dc0811113-624d-47a7-8250-50bb61f4fb58&width=768&dpr=3&quality=100&sign=c016921c&sv=2) #### [hashtag](https://docs.hivel.ai/configurations/exclusions#auto-exclude-commits-from-metrics) Auto Exclude Commits from Metrics Commits with these keywords will not be counted towards metrics. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FVXUNBeiz9Lp9BF4JH5zx%252Fimage.png%3Falt%3Dmedia%26token%3De4bd7429-0f65-4b14-85d9-ef964dd3606b&width=768&dpr=3&quality=100&sign=ddbf7f38&sv=2) > For any exclusions, only the ongoing data will reflect the changes, previous data will remain unchanged. [PreviousEnabling Hivel's AI-Powered Featureschevron-left](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features) [NextInvestment Configurationschevron-right](https://docs.hivel.ai/configurations/investment-configurations) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Coding Hotspots | Hivel ### [hashtag](https://docs.hivel.ai/using-hivel/coding-hotspots#what-is-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. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FnBmlyZPaLLMaVYWcxD68%252Fimage.png%3Falt%3Dmedia%26token%3Dd688cbf2-2b5b-4014-822a-c93481d405b4&width=768&dpr=3&quality=100&sign=5c98b3cd&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FpU50tC3cGSC4Q6NsLs79%252Fimage.png%3Falt%3Dmedia%26token%3D238995c4-73c0-451a-9cfa-fc0528d76219&width=768&dpr=3&quality=100&sign=e06c6354&sv=2) ### [hashtag](https://docs.hivel.ai/using-hivel/coding-hotspots#how-it-works) **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. ### [hashtag](https://docs.hivel.ai/using-hivel/coding-hotspots#how-to-use-coding-hotspots) How to Use Coding Hotspots * View repositories with the highest bug-related modifications. * Drill down into specific files to analyze patterns. #### [hashtag](https://docs.hivel.ai/using-hivel/coding-hotspots#drill-down-levels) 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. ### [hashtag](https://docs.hivel.ai/using-hivel/coding-hotspots#key-insights) 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. [PreviousWork Item Breakdownchevron-left](https://docs.hivel.ai/using-hivel/work-item-breakdown) [NextHivel Quadrantchevron-right](https://docs.hivel.ai/using-hivel/hivel-quadrant) Last updated 6 months ago * [What is Coding Hotspots?](https://docs.hivel.ai/using-hivel/coding-hotspots#what-is-coding-hotspots) * [How It Works](https://docs.hivel.ai/using-hivel/coding-hotspots#how-it-works) * [How to Use Coding Hotspots](https://docs.hivel.ai/using-hivel/coding-hotspots#how-to-use-coding-hotspots) * [Key Insights](https://docs.hivel.ai/using-hivel/coding-hotspots#key-insights) sun-brightdesktopmoon sun-brightdesktopmoon --- # Unreviewed PRs | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FzoCskm6csRVbD8RKh0ae%252FScreenshot%25202025-11-28%2520at%252012.28.49%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D71d7b643-edc1-401e-9f4f-6bf7233c5068&width=768&dpr=3&quality=100&sign=bcae9947&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/unreviewed-prs#all-merged-prs-that-do-not-have-a-review-state-are-prs-merged-without-review) All merged PRs that do not have a review state are PRs merged without review. * Reviewing every PR saves a lot of post-production issues and can keep higher quality across. * Merging PRs without review is a symptom of production issues or poor-quality code that could lead to higher maintenance issues in the future. Also, junior engineers miss out on learning opportunities. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/unreviewed-prs#industry-benchmarking) Industry Benchmarking ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FHcUOpTST4yG3BaJlk5ON%252Fimage.png%3Falt%3Dmedia%26token%3Da7463288-0cc6-4847-972f-5d975c75fc6e&width=768&dpr=3&quality=100&sign=8f5f3f80&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/unreviewed-prs#related-article) Related article [Best Practices for Ensuring Strong Pull Request Review Coveragechevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage) [Best Practices for Team Ownership in Code Reviewchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review) [PreviousReworkchevron-left](https://docs.hivel.ai/metrics-and-definitions/quality/rework) [NextPR Reviewedchevron-right](https://docs.hivel.ai/metrics-and-definitions/quality/pr-reviewed) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # PR Reviewed | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FlRyeK9kWgoYKgX6CCy6L%252FScreenshot%25202025-11-28%2520at%252012.30.02%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D38fd01cd-7011-4367-b362-5ff143de9aa6&width=768&dpr=3&quality=100&sign=2c328b0&sv=2) #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/pr-reviewed#pr-reviewed-percentage-measures-the-proportion-of-pull-requests-prs-that-have-been-reviewed-irrespec) PR reviewed percentage measures the proportion of pull requests (PRs) that have been reviewed (irrespective of who reviewed) compared to the total number of PRs merged during a specific time period. This percentage is calculated using all PRs merged within that period. For the selected teams, it only includes PRs created by team members. #### [hashtag](https://docs.hivel.ai/metrics-and-definitions/quality/pr-reviewed#related-article) Related article [Best Practices for Ensuring Strong Pull Request Review Coveragechevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage) [Best Practices for Team Ownership in Code Reviewchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review) [Why do some metrics like PRs reviewed or merged have more than 100%?chevron-right](https://docs.hivel.ai/faqs/metrics-and-data-faqs/why-do-some-metrics-like-prs-reviewed-or-merged-have-more-than-100) [PreviousUnreviewed PRschevron-left](https://docs.hivel.ai/metrics-and-definitions/quality/unreviewed-prs) [NextFlashy Reviewschevron-right](https://docs.hivel.ai/metrics-and-definitions/quality/flashy-reviews) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to sign up to Hivel? | Hivel #### [hashtag](https://docs.hivel.ai/set-up/sign-up/how-to-sign-up-to-hivel#h_01hyn18vz1hz8swcba4yx5s5mw) **You can sign up to Hivel using two methods:** **1\. Sign up for the platform using the invite link sent via email:** * If an admin from your organization has invited you to join, you will receive an email to sign up for the platform. * Simply follow the steps outlined in the email, and you'll be all set! * If you are an admin, please refer to this article on [how to invite users to the platform](https://docs.hivel.ai/set-up/users/how-to-invite-more-users-to-use-hivel) . ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F24QqWKHGebRuLoP2BhP1%252Fimage.png%3Falt%3Dmedia%26token%3De8c2b536-b7cd-4c41-921a-79affe333f19&width=768&dpr=3&quality=100&sign=4ce8f5b3&sv=2) **2\. Sign up on the website using either Single Sign-On (SSO) or by creating an email ID and password:** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F5X7feIFy9crGmU2i2NyS%252Fimage.png%3Falt%3Dmedia%26token%3D4d7b2ffd-6d84-4ff8-ace3-23cb76f29f3f&width=768&dpr=3&quality=100&sign=d5d38d65&sv=2) * If you are signing up using your organization mail ID, an admin in your organization will have to approve your request. **Troubleshooting:** * **Didn't receive an email?** Check your spam or junk folder. * **Issues with the invite link?** Ensure you are clicking the correct link and that your internet connection is stable. * **Problems with SSO?** Contact your organization's IT support for assistance. If you are still facing issues and are not able to sign up to the platform, please reach out to [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#ee9d9b9e9e819c9aae8687988b82c08f87) [PreviousSign Upchevron-left](https://docs.hivel.ai/set-up/sign-up) [NextUserschevron-right](https://docs.hivel.ai/set-up/users) Last updated 4 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Code Telemetry FAQs | Hivel How to Understand AI Written Code, With the Right Expectations ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#why-code-telemetry-exists) Why Code Telemetry exists AI assisted coding is now part of everyday development, but most teams struggle to answer one core question with confidence: **How much of the code that actually ships is written by AI, and what does that mean for delivery?** Code Telemetry exists to give teams a **clear and practical signal** to reason about AI usage over time. It is not designed to prove authorship or establish facts. It is designed to help teams see patterns and trends in shipped code. * * * ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#what-code-telemetry-shows-and-what-it-intentionally-does-not) What Code Telemetry shows, and what it intentionally does not Code Telemetry provides a **directional estimate** of: * Approximately how much merged code is AI written * Approximately how much is human written This analysis is done on **pull request diffs of code that is merged and shipped**, not on editor activity or AI suggestions. Just as important is what Code Telemetry does _not_ claim. It is not: * A factual determination of who wrote a specific line of code * A developer monitoring or enforcement tool * A benchmarking metric across teams or organizations * A one to one causal measure AI models themselves are probabilistic and opaque. Any system analyzing their output must work on signals, not certainty. Code Telemetry is designed with that reality upfront, not hidden behind precise looking numbers. * * * ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#confidence-score-and-what-it-really-means) Confidence Score and what it really means Alongside AI and human percentages, Code Telemetry surfaces a **confidence score**. This score reflects how confident our algorithm is in the classification it has made for a given PR diff. * Higher confidence means stronger and clearer authorship signals were detected * Lower confidence means signals were weaker, mixed, or ambiguous Even at very high confidence, the result represents our algorithm’s **best judgement**, not an absolute truth. We show confidence explicitly so teams can understand reliability instead of assuming certainty. * * * ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#how-code-telemetry-differs-from-cursor-or-copilot-metrics) How Code Telemetry differs from Cursor or Copilot metrics Many tools like Cursor or Copilot provide AI usage metrics, but they answer a different question. IDE level metrics: * Track AI usage inside a specific tool * Measure suggestions generated or accepted * Only capture activity within that environment * Do not account for copy paste or code generated elsewhere Code Telemetry is different by design: * It is **tool agnostic** * It does not depend on IDE or assistant telemetry, and it does not assess which LLM or model is used to generate code * It analyzes the **code that actually reaches production** * It captures AI usage regardless of how or where the code was generated In simple terms, IDE metrics show **AI usage in the editor**, while Code Telemetry shows **AI impact in shipped code**. Over time, we plan to incorporate available IDE level signals, such as Cursor’s own metrics, to further improve accuracy. Code Telemetry will always remain independent and focused on production reality. * * * ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#how-to-read-code-telemetry-correctly) How to read Code Telemetry correctly The right way to use Code Telemetry is to look at **trends over time**, not isolated numbers. It helps answer questions like: * Is AI usage increasing or stabilizing across teams? * How does increased AI usage align with delivery metrics? * Is AI adoption translating into faster or smoother shipping? **Example**: A team moves from: * 7 day cycle time with ~20 percent AI written code To: * 5 day cycle time with ~40 percent AI written code over a few months This does not prove causation. But it is a **credible directional signal** that increased AI usage may be contributing to faster delivery. That is the level of insight Code Telemetry is designed to support. * * * ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#how-not-to-use-code-telemetry) How not to use Code Telemetry To avoid misinterpretation, Code Telemetry should not be used to: * Compare teams against benchmarks * Rank individuals or teams * Draw direct cause and effect conclusions * Make decisions based on single data points Its value comes from **patterns**, not precision. * * * ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#code-telemetry-and-ai-impact) Code Telemetry and AI Impact Code Telemetry forms the foundation for the AI Impact feature. Once we understand how much AI written code is actually shipped, AI Impact analyzes how that usage aligns with downstream engineering metrics such as: * Cycle time * PR throughput * Review velocity * Commit frequency AI Impact does not assume AI is good or bad. It simply shows how AI usage in shipped code corresponds with changes in engineering outcomes. * * * ### [hashtag](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#in-summary) **In summary** * Code Telemetry is a **directional signal**, not a factual claim * It works on **shipped code**, not IDE activity * Confidence scores add transparency, not certainty * It is best used to understand trends over time * Its real value comes from pairing it with delivery metrics With the right expectations, Code Telemetry helps teams reason clearly about AI adoption without overclaiming accuracy or intent. [PreviousHivel AI Impact Screen: Overview & Insightschevron-left](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights) [NextBest Practiceschevron-right](https://docs.hivel.ai/best-practices) Last updated 1 month ago * [Why Code Telemetry exists](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#why-code-telemetry-exists) * [What Code Telemetry shows, and what it intentionally does not](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#what-code-telemetry-shows-and-what-it-intentionally-does-not) * [Confidence Score and what it really means](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#confidence-score-and-what-it-really-means) * [How Code Telemetry differs from Cursor or Copilot metrics](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#how-code-telemetry-differs-from-cursor-or-copilot-metrics) * [How to read Code Telemetry correctly](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#how-to-read-code-telemetry-correctly) * [How not to use Code Telemetry](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#how-not-to-use-code-telemetry) * [Code Telemetry and AI Impact](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#code-telemetry-and-ai-impact) * [In summary](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs#in-summary) sun-brightdesktopmoon sun-brightdesktopmoon --- # Hotfix & Jira Integration - Best Practices | Hivel To ensure high-quality insights into engineering health, we rely on clean and consistent metadata across Git and Jira. This document outlines best practices for accurately identifying hotfixes and enabling accurate metrics, such as Hotfix Resolution Rate and Hotfix Rate. Following these practices will ensure your team’s work is properly tracked and reflected in engineering reports. ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#id-1.-identify-hotfixes-via-pull-request-patterns) 1\. Identify Hotfixes via Pull Request Patterns We detect hotfix PRs by scanning Git metadata for specific keywords across several fields. This is the primary method for classifying a PR as a hotfix. #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#recommended-keywords-these-can-be-configured-based-on-your-naming-convention) Recommended Keywords (These can be configured based on your naming convention) : * hotfix * hot fix #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#fields-scanned) Fields Scanned: * Label * Title * Description * Branch Name * Tag #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#examples) 🔍 Examples: * _**hotfix/fix-auth-bug**_ (branch) * ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FveCFOqsRv4gvczCssUV7%252Fimage%2520%283%29.png%3Falt%3Dmedia%26token%3De04a35ee-f598-4269-b179-c8391e094a37&width=768&dpr=3&quality=100&sign=eef9bea6&sv=2) * _**Hotfix: Resolve checkout crash**_ (title) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fj4P70XGXGTgE4uXlnKli%252Fimage%2520%282%29.png%3Falt%3Dmedia%26token%3D1e8c343a-f0ba-4721-813c-dda285acac4f&width=768&dpr=3&quality=100&sign=d5954414&sv=2) * PR label: _**hotfix**_ * Tag: _**v2.1.4-hotfix**_ * Commit Message: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FPSo4y0EbV1wxGJOdwUJW%252Fimage%2520%281%29.png%3Falt%3Dmedia%26token%3D55ff9c94-4660-45ee-914d-3e29fa427b9f&width=768&dpr=3&quality=100&sign=f107ace4&sv=2) * The title, description can contain other task level details as well, it doesn’t have to be ONLY the ticket ID For example in the below screenshot “HAT-816” is the jira ticket ID ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fs9xLEDPvCMdFXEND5AST%252Fimage%2520%285%29.png%3Falt%3Dmedia%26token%3Dcc69f094-da4e-4e90-8df7-26518337b580&width=768&dpr=3&quality=100&sign=4b39e86b&sv=2) ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#id-2.-use-semantic-versioning-for-patch-releases) 2\. Use Semantic Versioning for Patch Releases Hotfixes can also be identified using version numbers that follow the semantic versioning format: x.y.z, where z (the patch number) is greater than 0. This method is optional and must be explicitly enabled. #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#example) Example: * PR title: _**Release v1.3.2**_ * Branch: _**release/v1.3.2**_ * Tag: _**v1.3.2**_ ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#id-3.-jira-issue-types-use-consistent-classification) 3\. Jira Issue Types – Use Consistent Classification To link hotfix PRs with Jira issues, we rely on standard Jira issue types. #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#required-setup) Required Setup: * Hotfix-related tickets must use the Bug issue type. * Ensure Jira issue types are configured consistently across teams. ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#id-4.-what-to-avoid) 4\. What to Avoid The following practices prevent us from generating reliable Jira-linked metrics: * Using shared or generic Jira accounts * Assigning issues via custom filters (e.g., using individual developers as an assignee type) * Inconsistent or missing PR metadata (no hotfix keyword, no version tags, etc.) * Not using or misusing Jira issue types (e.g. all issues marked as “Task”) ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#why-this-matters) Why This Matters When these best practices are followed, you unlock the ability to track and improve: * Hotfix Resolution Time * Hotfix Rate * PR-to-Jira traceability * Team and user-level accountability metrics [PreviousJira Best Practiceschevron-left](https://docs.hivel.ai/best-practices/jira-best-practices) [NextBest practices for adopting Story Pointschevron-right](https://docs.hivel.ai/best-practices/jira-best-practices/best-practices-for-adopting-story-points) Last updated 3 months ago * [1\. Identify Hotfixes via Pull Request Patterns](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#id-1.-identify-hotfixes-via-pull-request-patterns) * [2\. Use Semantic Versioning for Patch Releases](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#id-2.-use-semantic-versioning-for-patch-releases) * [3\. Jira Issue Types – Use Consistent Classification](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#id-3.-jira-issue-types-use-consistent-classification) * [4\. What to Avoid](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#id-4.-what-to-avoid) * [Why This Matters](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices#why-this-matters) sun-brightdesktopmoon sun-brightdesktopmoon --- # Enabling Hivel's AI-Powered Features | Hivel Hivel’s AI-powered features unlock deeper insights and surface meaningful patterns across your software development lifecycle, like Comment Categorization, Code Telemtry, Lucy (AI Insights Chatbot), etc. circle-check **AI Features Are Opt-In Only** By default, all AI-powered features in Hivel are **disabled**. These features are only activated: * Upon **explicit customer consent**, or * When a user **enables them manually** in the settings. ### [hashtag](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#how-to-enable-or-disable-ai-features) How to Enable or Disable AI Features ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FOQOuLdBDTes0RPruu9vL%252Fimage.png%3Falt%3Dmedia%26token%3Da05e2006-ef6e-43e1-a941-dd186038a45e&width=768&dpr=3&quality=100&sign=7aa95d3d&sv=2) #### [hashtag](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#steps) Steps: 1. Go to the **Configuration** screen. 2. Scroll to the section labeled **AI**. 3. You can choose to enable all or few of the features. > ⚠️ Turning the toggle ON allows Hivel to process select metadata via large language models (LLMs) to generate insights. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FCEwAGK4JoVOMCL0gBpIg%252Fimage.png%3Falt%3Dmedia%26token%3D3e1edabc-ebf1-4078-9dee-82e6bff804cc&width=768&dpr=3&quality=100&sign=4b307abe&sv=2) ### [hashtag](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#data-privacy-and-security-commitments) Data Privacy and Security Commitments #### [hashtag](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#ai-terms-and-conditions) [**AI Terms and Conditions**arrow-up-right](https://www.hivel.ai/privacy-policy#:~:text=AI%20Model%20Engagement%20and%20User%20Data%20Autonomy) Hivel prioritizes **data security, anonymity, and customer trust**. Here's how we protect your information: #### [hashtag](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#what-data-is-shared) **What Data Is Shared** Only the minimum required data is shared, and it's processed with care: * **Anonymized data only**: No company names, author identifiers, commit hashes, ticket numbers, or branch names are sent to the AI model. * **Aggregated content**: We batch similar types of data (e.g., commit messages or PR comments) and remove any contextual identifiers before sending. * **Zero business logic exposure**: We do not send your source code, configuration files, or deployment secrets. * **No access to customer environments**: AI models interact only with sanitized metadata already available within Hivel’s controlled systems. #### [hashtag](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#ephemeral-processing-and-no-retention) **Ephemeral Processing and No Retention** * Data is transmitted via secure APIs using **TLS encryption**. * AI model providers do **not store** any of your inputs or outputs. * Every interaction is **stateless** i.e. each input is processed in isolation and discarded immediately after generating the response. ### [hashtag](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#faqs) **FAQs** #### [hashtag](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#is-any-customer-code-shared-with-ai-models) **Is any customer code shared with AI models?** No. We do **not** share source code, internal logic, or proprietary configurations. AI features operate only on derived metadata (like commit messages or review comments), after rigorous redaction and obfuscation. #### [hashtag](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#which-ai-models-are-used) **Which AI models are used?** We use industry-grade LLMs provided by OpenAI and Anthropic, interfaced via private, stateless API calls. These providers are contractually and technically prohibited from retaining or training on your data. [PreviousMetric Behaviourchevron-left](https://docs.hivel.ai/configurations/metric-behaviour) [NextExclusionschevron-right](https://docs.hivel.ai/configurations/exclusions) Last updated 1 month ago * [How to Enable or Disable AI Features](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#how-to-enable-or-disable-ai-features) * [Data Privacy and Security Commitments](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#data-privacy-and-security-commitments) * [FAQs](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features#faqs) sun-brightdesktopmoon sun-brightdesktopmoon --- # Jira Best Practices | Hivel [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#jira-board-hygiene-and-sprint-best-practices) Jira Board Hygiene and Sprint Best Practices ------------------------------------------------------------------------------------------------------------------------------------------------------------------ Maintaining clean and well-structured Jira boards is essential for reliable sprint planning, predictable delivery, and trustworthy reporting. The practices below are designed to minimize manual effort while maximizing clarity for both developers and leaders. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#id-1.-before-the-sprint-starts) 1\. Before the Sprint Starts #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#create-tickets-ahead-of-sprint-start) Create Tickets Ahead of Sprint Start All work intended for a sprint should already exist in the backlog before sprint planning begins. * Create tickets in the backlog and move them into the sprint only after discussion. * Break down large pieces of work into small, actionable tickets that can be completed within a sprint. * Avoid creating tickets directly inside an active sprint unless they are truly unplanned. Why this matters Pre-created tickets allow planning to focus on sequencing and tradeoffs rather than discovery under time pressure. * * * #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#assign-story-points-during-planning) Assign Story Points During Planning Every ticket entering the sprint should have story points assigned. * Estimation should consider complexity, scope, and uncertainty, not individual developer speed. * Points should be agreed upon collaboratively during sprint planning. * Unestimated tickets should not be pulled into the sprint. Why this matters Consistent estimation improves velocity tracking and makes future sprint planning more predictable. * * * #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#link-all-tickets-to-epics) Link All Tickets to Epics Every ticket should be associated with an Epic. * Epics represent higher-level goals, initiatives, or customer outcomes. * Epic linkage enables roll-up reporting and clearer progress tracking. * Avoid orphan tickets without an Epic unless explicitly intentional. Why this matters Epics create structure and prevent Jira boards from becoming flat task lists with no strategic context. * * * #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#assign-ownership-clearly) Assign Ownership Clearly Each ticket should have a single, clear assignee. * Avoid assigning multiple people to one ticket. * Avoid generic or unassigned tickets entering the sprint. * If multiple people are involved, split the work into multiple tickets. Why this matters Clear ownership improves accountability and prevents work from silently stalling. * * * #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#confirm-team-commitment-before-starting-the-sprint) Confirm Team Commitment Before Starting the Sprint Before clicking **Start Sprint**, confirm that: * All tickets have story points. * All tickets are linked to Epics. * All tickets have assignees. * Developers agree the scope is realistic. Summary A sprint should only be started once the board reflects committed, estimated, and owned work. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#id-2.-once-the-sprint-is-in-progress) 2\. Once the Sprint Is in Progress #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#limit-a-d-hoc-work) Limit Ad Hoc Work Unplanned work should be the exception, not the norm. * Only add mid-sprint tickets for urgent issues, incidents, or blockers. * Ensure any new ticket added mid-sprint has story points and an Epic. * Discuss the tradeoff openly in standups. Why this matters Frequent ad hoc additions erode sprint predictability and distort velocity. * * * #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#actively-manage-scope) Actively Manage Scope If new work must be added: * Remove or de-scope equivalent work where possible. * Avoid silently increasing total sprint scope. * Make scope changes visible to the team. Why this matters Stable scope preserves trust in sprint commitments and delivery metrics. * * * #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#adjust-story-points-when-reality-changes) Adjust Story Points When Reality Changes If a ticket proves significantly larger or smaller than expected: * Update story points to reflect actual effort. * Use this as learning for future estimation. * Avoid retroactively changing points only to “make numbers look good”. Why this matters Accurate data matters more than perfect optics. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#id-3.-before-closing-the-sprint) 3\. Before Closing the Sprint #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#ensure-completed-tickets-are-in-done) Ensure Completed Tickets Are in Done Before closing the sprint: * Confirm all finished work is transitioned to the Done status. * Ensure Done reflects your team’s actual definition of done, including testing and review if applicable. Why this matters Sprint reports and velocity calculations depend entirely on correct status transitions. * * * #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#do-not-carry-done-tickets-forward) Do Not Carry Done Tickets Forward Once a ticket is marked Done: * Do not move it to the next sprint. * If follow-up work is needed, create a new ticket instead. Why this matters Moving Done tickets forward corrupts historical sprint data and reporting. * * * #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#handle-incomplete-work-cleanly) Handle Incomplete Work Cleanly For tickets that are not finished: * Move them to the next sprint only if work remains. * Re-estimate if scope has changed. * Avoid leaving stale tickets partially done across multiple sprints. Summary Only unfinished work should roll forward. Completed work should stay completed. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#id-4.-low-effort-jira-automations-and-smart-defaults) 4\. Low-Effort Jira Automations and Smart Defaults This section focuses on improvements that require **minimal ongoing maintenance** but significantly improve hygiene. #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#automatically-enforce-required-fields) Automatically Enforce Required Fields Use Jira Automation to prevent bad data from entering sprints. Examples: * Block sprint start if tickets are missing story points. * Auto-comment or flag tickets without Epics. * Warn when tickets are unassigned. Why this matters Automation removes the need for manual policing during planning. * * * #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#auto-update-fields-on-status-changes) Auto-Update Fields on Status Changes Common lightweight automations include: * Set resolution when a ticket moves to Done. * Auto-assign the reporter or component owner when a ticket is created. * Clear assignee when a ticket is moved back to To Do. Why this matters This keeps data consistent without adding process overhead. * * * #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#tag-and-track-unplanned-work-automatically) Tag and Track Unplanned Work Automatically Create an automation rule that: * Labels tickets added after sprint start as unplanned. * Adds them to a dedicated Epic or category. * Optionally posts a comment explaining they were added mid-sprint. Why this matters This preserves sprint integrity while still allowing urgent work. * * * #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#use-board-and-workflow-guards-instead-of-manual-checks) Use Board and Workflow Guards Instead of Manual Checks Prefer system-enforced rules over reminders. Examples: * Workflow conditions that prevent Done without required fields. * Board filters that hide invalid tickets from sprint views. * Quick filters for unestimated or unassigned tickets. Why this matters Good defaults reduce reliance on individual discipline. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#benefits-of-following-these-practices) Benefits of Following These Practices * Clear visibility into sprint progress and risks. * More predictable sprint planning and delivery. * Stronger ownership and accountability. * Cleaner historical data for velocity and trend analysis. * Less time spent fixing Jira instead of shipping software. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices#final-summary) Final Summary Clean Jira boards are not about process overhead. They are about creating a shared, reliable system that reflects reality. When tickets are well-defined before the sprint, scope is managed transparently during execution, and automation handles the repetitive checks, teams gain confidence in their delivery and leaders gain confidence in the data. [PreviousBest Practices for Software Development Efficiencychevron-left](https://docs.hivel.ai/best-practices/best-practices-for-software-development-efficiency) [NextHotfix & Jira Integration - Best Practiceschevron-right](https://docs.hivel.ai/best-practices/jira-best-practices/hotfix-and-jira-integration-best-practices) Last updated 3 months ago * [Jira Board Hygiene and Sprint Best Practices](https://docs.hivel.ai/best-practices/jira-best-practices#jira-board-hygiene-and-sprint-best-practices) * [1\. Before the Sprint Starts](https://docs.hivel.ai/best-practices/jira-best-practices#id-1.-before-the-sprint-starts) * [2\. Once the Sprint Is in Progress](https://docs.hivel.ai/best-practices/jira-best-practices#id-2.-once-the-sprint-is-in-progress) * [3\. Before Closing the Sprint](https://docs.hivel.ai/best-practices/jira-best-practices#id-3.-before-closing-the-sprint) * [4\. Low-Effort Jira Automations and Smart Defaults](https://docs.hivel.ai/best-practices/jira-best-practices#id-4.-low-effort-jira-automations-and-smart-defaults) * [Benefits of Following These Practices](https://docs.hivel.ai/best-practices/jira-best-practices#benefits-of-following-these-practices) * [Final Summary](https://docs.hivel.ai/best-practices/jira-best-practices#final-summary) sun-brightdesktopmoon sun-brightdesktopmoon --- # Setting Up Slack to Receive Hivel Alerts | Hivel circle-info We suggest creating a dedicated Slack channel just for alerts, so updates stay visible and easy to track. ### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel/setting-up-slack-to-receive-hivel-alerts#steps-to-set-up) **Steps to Set Up:** 1. **Integrate Slack with Hivel:** * Go to **Settings →** [**Integrations**arrow-up-right](https://app.hivel.ai/settings/integrations) **→ Slack**. * Complete the integration process as outlined in [this guidearrow-up-right](https://docs.hivel.ai/integrations/slack-integration-with-hivel) . 2. **Add your Slack Channel ID:** * Create or open your Slack channel and copy the **Channel ID** from the "About" section. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F7wMyDnngGfclpryqh27K%252Fimage.png%3Falt%3Dmedia%26token%3Daaf682e7-5ead-4c55-90cb-aa711bbdc459&width=768&dpr=3&quality=100&sign=dabce6b9&sv=2) * Click the **Settings ⚙️** icon in the Alerts screen, and paste the Channel ID in the **Alerts Configuration** section. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FsEJiHfRBpCtMOHyqeJAM%252Fimage.png%3Falt%3Dmedia%26token%3De997f573-fba1-429d-9c9a-44a4ed571ff5&width=768&dpr=3&quality=100&sign=8a5a904b&sv=2) 1. **Invite "Hivel Alerts" Bot to Slack:** * Type `**@Hivel Alerts**` in the Slack channel and invite the bot. Once done, Hivel will start sending alerts to your Slack channel. ### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel/setting-up-slack-to-receive-hivel-alerts#sending-alerts-to-personal-dms-instead-of-channels) Sending Alerts to Personal DMs instead of channels 1. Copy the member ID of the individual who should receive the alerts - by selecting the profile icon -> view full profile -> three dots on the right then "Copy member ID" 1. Note - you can only configure one such channel personally. So in case you have configured your own member ID, you won't be able to add someone else's. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FC1rUIHkcrUpwIGZuNUeA%252Fimage.png%3Falt%3Dmedia%26token%3D2a2af41d-d88a-4a58-b0f8-dc28e80bab87&width=768&dpr=3&quality=100&sign=5a9e7914&sv=2) 👉 **Need help?** Contact us at [\[email protected\]](https://docs.hivel.ai/cdn-cgi/l/email-protection) . [PreviousAlerts in Hivelchevron-left](https://docs.hivel.ai/using-hivel/alerts-in-hivel) [NextLucychevron-right](https://docs.hivel.ai/using-hivel/lucy) Last updated 1 month ago * [Steps to Set Up:](https://docs.hivel.ai/using-hivel/alerts-in-hivel/setting-up-slack-to-receive-hivel-alerts#steps-to-set-up) * [Sending Alerts to Personal DMs instead of channels](https://docs.hivel.ai/using-hivel/alerts-in-hivel/setting-up-slack-to-receive-hivel-alerts#sending-alerts-to-personal-dms-instead-of-channels) sun-brightdesktopmoon sun-brightdesktopmoon --- # Hivel Score | Hivel [](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation) #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score#org-level-score-calculation) Org level score calculation [](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation) #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score#team-level-score-calculation) Team level score calculation Hivel Score provides engineering leaders with a fast, reliable snapshot of overall performance - without the need to navigate multiple dashboards. It brings together key signals like **speed, quality, and throughput** into a single, easy-to-understand score. #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score#what-is-hivel-score) What is Hivel Score? Hivel Score is an **aggregate, organization-level indicator** that reflects how your teams are performing across core engineering metrics. Each score is presented out of 100, making it simple to quickly assess performance at a glance. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FPrgVE58rQnAK47jxBfli%252Fimage.png%3Falt%3Dmedia%26token%3D3aac2f54-c15b-4fea-b0e8-4446972e7388&width=768&dpr=3&quality=100&sign=befeda1a&sv=2) #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score#how-to-interpret-the-score) How to interpret the score * **Scores are contextual**: They are most meaningful when compared to a previous timeframe. * **Trend-focused**: The score highlights whether metrics have improved, declined, or remained stable. * **Drilldowns available**: Supporting metrics and percentage changes provide deeper insights into what’s driving the score. #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score#why-it-matters) Why it matters Hivel Score is designed to help you: 1. **Quickly assess performance health** across teams or the entire organization 2. **Identify areas of improvement** by understanding metric-level changes 3. **Track score progress over time** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FkW4r7mew5Jt38b5Gue9T%252Fimage.png%3Falt%3Dmedia%26token%3Db94559e2-5bb6-4c58-bfa6-e20f7594bb52&width=768&dpr=3&quality=100&sign=95f82685&sv=2) #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score#about-scoring-and-stack-ranking) About scoring and stack ranking The scoring system, along with the stack rank view, is intended to provide **directional clarity** \- helping you understand how teams are progressing over time and where attention may be needed. Rather than serving as a direct comparison tool, it offers a **relative view of performance trends**, making it easier to: * Spot teams that are improving or facing challenges * Highlight which metrics may need focus * Understand how performance evolves across the organization ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F06GLGYmtGuPkCiVHTdyE%252Fimage.png%3Falt%3Dmedia%26token%3D2a83907b-0914-460f-821c-2fc027f8eccb&width=768&dpr=3&quality=100&sign=68a42dce&sv=2) [PreviousLucychevron-left](https://docs.hivel.ai/using-hivel/lucy) [NextOrg level Hivel Score Calculationchevron-right](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation) Last updated 3 hours ago sun-brightdesktopmoon sun-brightdesktopmoon --- # AI usage - PR checklist + Prompt Cookbook + Cursor Rules | Hivel ### [hashtag](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules#pr-checklist-policy-using-ai-tools-responsibly) PR Checklist / Policy: Using AI Tools Responsibly Consider making this a page in your Engineering Handbook. Engineers should run through this checklist when using Copilot or Cursor for features, refactors, or bug fixes. * * * #### [hashtag](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules#pull-request-code-change-policy) Pull Request / Code Change Policy Step What to do Why it matters **Capture Context Before AI Use** In your PR or before prompting AI, clearly define: • The goal (feature/fix/refactor) • The constraints (performance, memory, dependencies, DB schema, API contracts) • Existing patterns/style (coding conventions, error handling, package structure) • What must / must not change (e.g. avoid breaking public APIs) This ensures the AI’s suggestions are aligned with architecture/style and reduces dangerous drift. **Use Good Prompts / Rules** Use structured prompts: • State the goal • Supply relevant context (file snippet, types/interfaces) • Ask for test coverage/error handling/security as needed (see Prompt Cookbook below) • Limit the scope (one file, or one small change) Better prompt → higher quality suggestions. Helps make suggestions easier to review. **Review AI Suggestions Like Code Reviews** When you see AI generated or assisted code: • Read it line-by-line • Check correctness, edge cases, security, resource use, database effects • Ensure readability, maintainability, naming & consistency with team style • If using Copilot: experiment with alternative suggestions; pick the best one. Prevents introducing bugs or messy code. Ensures AI is augmenting, not replacing human oversight. **Tests, Error & Boundary Cases** Always ensure: • Unit tests / integration tests cover new or changed logic, especially for edge cases • Error handling, failure modes are considered (invalid input, timeouts, nulls etc.) • Database transactions are safe, schema compatibility maintained. Many AI outputs fail at boundary conditions. Testing ensures code works as expected. **Security / Sensitive Data Review** • Don’t paste secrets or credentials into prompts or code. • Use static analysis / code scanning for security vulnerabilities. • Review for injection risks, permission leaks, untrusted inputs. • Keep modules that access sensitive data under tighter human review. AI may suggest insecure patterns. Avoid accidental data exposure. **Fit With Existing Architecture & Dependencies** • Make sure suggested code plays nicely with existing services, modules, patterns. • Avoid duplicating functionality, violating modular boundaries. • Upkeep dependency versions and compatibility. Keeps maintainability high and avoids technical debt. **Document Changes & Rationale** If you accept an AI suggestion that changes logic/design: • Write in PR description what was changed, why. • Indicate what trade-offs were made. • If AI used rules / patterns, reference them. Helps reviewers understand why AI was used; aids future maintenance. **Code Review Signoff & Ownership** • Even if AI wrote a lot, a human must own the change. • Reviewers should verify code quality, tests, performance. • Do not use “AI did it” as justification for skipping review. Accountability + high quality. **Monitor Post-Merge Behavior** After merging: • Track fallout: bugs, regressions, customer issues. • If this change increases errors / rejects during QA, revisit the usage. • Retrospect what worked / what didn’t. Data ensures learning and iteration; metrics reflect reality. **Continuous Improvement** • Periodically share best prompt examples internally. • For Cursor - Update rules or style guide based on what suggestions are bad / common failures. • Run occasional audits of AI-assisted PRs to see where suggestions consistently fail. • Collect peer feedback. Helps reduce noise, improve quality over time. * * * ### [hashtag](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules#prompt-templates-examples) Prompt Templates / Examples Here are good prompt patterns you or your team can adopt. Use or adapt in the AI assistants. Task Prompt Template Notes / Things to Include **Feature Implementation** _“Implement a_ `__` _in_ `__` _that does_ `__`_. Use_ `__` _if relevant. Write unit tests as well. Ensure error handling for invalid inputs, timeouts, and DB failures. Match existing coding style.”_ Include the goal, the component or module name, test requirements, error / edge conditions, match style. **Refactor / Clean Up** _“Refactor method_ `__` _in_ `__` _to simplify logic. Preserve existing behavior and API contract. Add tests if coverage is low. Ensure naming and error handling follow team conventions.”_ Helps preserve correct functionality. Trigger deeper thinking. **Bug Fix** _“Fix bug where_ `__` _in_ `__` _(e.g. “when user submits empty field, backend 500s”). Include tests reproducing bug and fix. Also review for similar occurrences elsewhere.”_ Including description and reproducibility helps. Asking to scan for similar patterns improves code hygiene. **Performance / Optimization** _“Optimize the query in_ `__` _retrieving_ `__` _from Postgres. Consider indexes, limit/pagination, avoid N+1, use appropriate joins. Retain readability and maintainability. Show before/after rationale.”_ Encourages thinking about performance tradeoffs. **Security / Sanitization** _“Add input validation, sanitization, and secure practices for_ `__` _that takes user input. Ensure prevention of SQL injection, XSS, unauthorized access. Write tests for invalid inputs.”_ Promotes safer code. **Code Review Helper** _“Review this diff / file:_ `__`_; point out issues for readability, maintainability, test coverage, security, style mismatches. Suggest small fixes or improvements.”_ Useful to catch oversights before PR. **Writing Tests** _“Write unit tests(s) for_ `__` _that cover success cases, invalid inputs, error paths. Use_ `__`_.”_ Ensures test coverage. **Database Schema Changes / Migrations** _“Suggest a migration to introduce_ `__` _while preserving existing data. Write migration script. Update service layer and repository accordingly. Ensure backward compatibility.”_ Important for DB-safe evolution. * * * ### [hashtag](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules#cursor-rules) Cursor Rules Below is a sample set of rules you can keep in a repository (or global) so Cursor (or any similar AI tool) has project-level constraints and guidance. circle-exclamation `.cursorrules` will be deprecated in the future, hence consider updating rules directly in **Cusor Settings -> Rules** * * * ### [hashtag](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules#summary-usage-guidelines) Summary / Usage Guidelines * For each PR, assume parts of it are AI-assisted. Always treat suggestion as draft. * Use the checklist above as gating criteria. If fail any step (e.g. no tests, no error handling), request changes. * Prompt templates + Rules help make suggestions consistent and aligned. [PreviousBest practices for AI usagechevron-left](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage) [NextConfigurationschevron-right](https://docs.hivel.ai/configurations) Last updated 6 months ago * [PR Checklist / Policy: Using AI Tools Responsibly](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules#pr-checklist-policy-using-ai-tools-responsibly) * [Prompt Templates / Examples](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules#prompt-templates-examples) * [Cursor Rules](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules#cursor-rules) * [Summary / Usage Guidelines](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules#summary-usage-guidelines) sun-brightdesktopmoon Copy # .cursorrules — project / team style & constraints # General - Use strict typing everywhere. Do not use `any` or equivalent without explicit justification. - Always follow the project’s naming conventions for files, classes, methods, interfaces. (e.g. React: components PascalCase, hooks useCamelCase, utils camelCase; Java: classes PascalCase etc.) - Document public / exported functions and classes with JSDoc / JavaDoc style comments. - Error handling must log or handle expected and unexpected error paths. - Avoid copying/pasting code. Use shared modules / utilities. # React / TypeScript - Prefer functional components + hooks; avoid class components per new code. - Use ESLint + Prettier rules; enforce linting pre-commit / CI. - For UI components: follow existing component library styles, props naming, theming tokens etc. - Write unit tests (Jest / React Testing Library) for any component with logic (not purely presentational). # Java / Spring Boot - Use dependency injection; avoid `new` for dependencies in services/controllers except when encapsulated. - Use REST controllers / service / repository separation. - Methods should have clear single responsibility; i.e. small methods. - Use logging (both info + error levels); exceptions should carry context. - For database interactions (JPA or JDBC): ensure transactions handled; check for SQL injection risks; avoid raw SQL unless necessary. # Database / Postgres - Use parameterized queries or ORM to avoid injection. - Follow performance best practices: indexes, limits, avoiding N+1 queries. - Use migrations; track schema evolution; avoid destructive changes without migration plan. - Partition / sharding only when needed; ensure explain plans used for heavy queries. # Security / Quality - No secrets or credentials in code or prompts. - Use static analysis / linters / security scanning on generated code. - Tests required for any change with business logic, error handling, external API or DB calls. - Peer review required for changes > ~50 LOC or touching more than 1 module / package / domain boundary. sun-brightdesktopmoon --- # Org level Hivel Score Calculation | Hivel * * * ### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#setting-up-your-configuration) Setting Up Your Configuration Before any scores are calculated, you'll need to complete a one-time configuration. This involves setting the **weight** you want to assign to each of the three performance buckets: * **Speed** - How quickly your teams move * **Quality** - The standard of work being delivered * **Throughput** -The volume of work being completed You can distribute the weights according to what matters most to your organization. The only rule is that the three weights must add up to **100%**. If they don't, you'll see a validation error and won't be able to save until this is corrected. > **Note:** Scores will only start being calculated after your configuration is saved. You can revisit and update this configuration at any time from Settings. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fc0baiX4nvTMPv1J00UO3%252Fimage.png%3Falt%3Dmedia%26token%3D5cade112-2e16-4de1-828f-cd539754e5d5&width=768&dpr=3&quality=100&sign=bccffdf7&sv=2) * * * ### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#how-the-org-level-hivel-score-is-calculated) How the Org-Level Hivel Score is Calculated The score is built from the ground up - starting at individual metrics, rolling up to buckets, and finally combining into one org-level number. #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#step-1-metric-scores) Step 1: Metric Scores Each bucket (Speed, Quality, Throughput) is made up of a fixed set of metrics - things like Commits, PRs Merged, or Review Time. Every metric is scored on a **0–100 scale** by comparing a team's value against all teams' performance over the past 6 months. This ensures scores always reflect relative performance across your org, not arbitrary thresholds. Teams with no activity on a metric receive a score of 0. #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#step-2-bucket-scores-per-team) Step 2: Bucket Scores Per Team Within each bucket, metrics carry predefined weights that reflect their relative importance. A team's bucket score is the weighted average of its individual metric scores. #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#step-3-org-level-aggregation) Step 3: Org-Level Aggregation For each bucket, the org score is calculated as a **developer-weighted average** across all top-level teams. This means larger teams have a proportionally greater influence on the org score, ensuring the number reflects your actual organizational makeup. Once weighted averages are computed for all three buckets, your configured weights are applied to arrive at the **final Org Hivel Score**. **Example** Team Developers Speed Quality Throughput A 10 70 80 75 B 5 60 65 70 C 15 85 90 88 With configured weights of Speed 30%, Quality 40%, Throughput 30%, the final Org Hivel Score works out to **79.37**. * * * ### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#when-can-you-view-the-score) When Can You View the Score? Scores are available for **completed months only**. You won't see a score for the current, in-progress month - this ensures the data is complete and the score is accurate before it's displayed. Use the **Duration Selector** to navigate between past months (full month selection only). * * * ### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#what-youll-see-on-the-dashboard) What You'll See on the Dashboard Once configured, the org-level dashboard gives you: * **Hivel Score** for the selected month, along with a trend vs. the last 6 months * **Score Trend Graph** - a line chart showing how your org score has moved over the past 6 months * **Category Breakdown** - a bar view of your Speed, Quality, and Throughput scores. Click on any bar to see the individual metrics within that bucket, their scores, and how they compare to the 6-month average * **Team Ranking Table** - a flat list of all teams ranked by their Hivel Score, showing: * Team Name * Score * % Change vs. 6-month average * Team score vs. Org score (% difference) You can also use the **"See Users with Lowest Score"** toggle to identify individuals who may need additional support, and use **"View All Teams"** for a fuller view with optional cascading sub-team visibility. * * * ### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#a-few-things-to-keep-in-mind) A Few Things to Keep in Mind * Only **top-level teams** contribute to the Org Hivel Score * If no data is available for a team or metric, a score of **0** is shown * **Team vs. Org** comparisons are made at the overall score level only, not at the individual bucket level * * * _For questions or help with your configuration, please reach out to our support team._ [PreviousHivel Scorechevron-left](https://docs.hivel.ai/using-hivel/hivel-score) [NextTeam level Hivel Score Calculationchevron-right](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation) Last updated 1 day ago * [Setting Up Your Configuration](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#setting-up-your-configuration) * [How the Org-Level Hivel Score is Calculated](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#how-the-org-level-hivel-score-is-calculated) * [When Can You View the Score?](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#when-can-you-view-the-score) * [What You'll See on the Dashboard](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#what-youll-see-on-the-dashboard) * [A Few Things to Keep in Mind](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation#a-few-things-to-keep-in-mind) sun-brightdesktopmoon sun-brightdesktopmoon --- # Metric Behaviour | Hivel In this section you can adjust rework days, enable benchmarking, workspaces, release cycles, and set file type exclusions. #### [hashtag](https://docs.hivel.ai/configurations/metric-behaviour#flashy-review) Flashy Review The Flashy Review section allows you to define what constitutes a flashy review for your organization, with customizable thresholds for Lines of Change and time taken to review. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fa1wplw8i35Fojm9bT5zW%252Fimage.png%3Falt%3Dmedia%26token%3D0d1bead9-120f-4d0a-b694-b66853081e36&width=768&dpr=3&quality=100&sign=3319ae7c&sv=2) #### [hashtag](https://docs.hivel.ai/configurations/metric-behaviour#rework-days) Rework Days You can adjust the threshold that should be considered for Rework. * For changes made to code originally written within this threshold will be considered as Rework. * For changes older than this threshold will be considered as Maintenance. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F83DQtNnlae7nQxwhHYmI%252Fimage.png%3Falt%3Dmedia%26token%3Da24f3792-7190-45ab-8bc3-c51d9de6c03b&width=768&dpr=3&quality=100&sign=5d99c4d2&sv=2) #### [hashtag](https://docs.hivel.ai/configurations/metric-behaviour#exclude-file-types) Exclude File Types You can exclude certain file types from any calculation so that unwanted data does skew up the metrics. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fnd174ZNymC17zxQJ6Y3h%252Fimage.png%3Falt%3Dmedia%26token%3D19cad834-7599-4498-9dea-fc02d47948b6&width=768&dpr=3&quality=100&sign=6bcad26a&sv=2) * For our processing and calculations, we automatically exclude files and directories that start or end with the following: `.settings`, `dist`, `tmp`, `out-tsc`, `node_modules`, `bower_components`, `.idea`, `typings`, `.vscode`, `vendor/`, `coverage`. * Additionally, if any files contain the following in their paths, they are also excluded: `src`, `assets`, `images`. * All of these options can be adjusted on the settings page, where you can also specify additional files to be excluded. [PreviousTrack hotfixes via patch version patternchevron-left](https://docs.hivel.ai/configurations/hotfix-configurations/track-hotfixes-via-patch-version-pattern) [NextEnabling Hivel's AI-Powered Featureschevron-right](https://docs.hivel.ai/configurations/enabling-hivels-ai-powered-features) Last updated 5 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Cursor: Expanded Metrics Guide | Hivel Cursor provides detailed insights into AI usage patterns via the **Admin Panel export CSV** and **Admin API**. These metrics allow admins to track code origin, suggestion interactions, and chat-based adoption for each developer on a daily basis. * * * #### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption/cursor-expanded-metrics-guide#metric-categories) 🔍 **Metric Categories** **Area** **Metrics Covered** **AI Contribution** AI vs Manual LoC, Accepted Lines Added, Composer Suggestions **Interaction Metrics** Tabs shown, Tabs accepted, Chat completions, Suggestions applied **Coverage & Activity** Active status per user per day, Usage trends over time **Engagement Intensity** Files edited, Commit activity, Frequency of usage * * * #### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption/cursor-expanded-metrics-guide#key-metric-definitions) 🧮 **Key Metric Definitions** **✅ AI Lines vs Manual Lines** * **Total LOC**: This is directly retrieved from the Cursor API, using the sum of two specific fields in the API response (as shown in the screenshot below). It represents the total number of lines added or deleted within a given period. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FzuZNnSQczjmp6nCbfgYj%252Fimage.png%3Falt%3Dmedia%26token%3D9c5414be-0a1a-4bea-a465-9f8491457725&width=768&dpr=3&quality=100&sign=69b60525&sv=2) * **Total AI Lines Added**: The total AI lines are also calculated by summing the two specific fields in the API response, as shown in the screenshot. This represents the number of accepted lines added + accepted lines removed by AI by the developer. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FRwOhc9VDG7742A7g0FyV%252Fimage.png%3Falt%3Dmedia%26token%3D1de33289-2605-4e0b-8571-3b702db2f2c6&width=768&dpr=3&quality=100&sign=b0c6de76&sv=2) * **Manual LOC**: Manual LOC is calculated by subtracting the AI LOC from the Total LOC. In other words, `**Manual LOC = Total LOC - AI LOC**``.` **✅ Suggestions Shown / Accepted** * **totalTabsShown**: The total number of suggestions displayed to the developer (autocomplete or inline suggestions). * **totalTabsAccepted**: The total number of suggestions accepted by the developer into the code. * **totalAccepts**: Includes all types of accepted completions, such as **Composer** or **Chat** suggestions. * **totalApplies**: Represents the final, user-confirmed inserts into the code editor. **✅ Acceptance Rate** * **Formula**: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FipnMk2U42jUdbrEklwMx%252Fimage.png%3Falt%3Dmedia%26token%3D885cca2b-b8e6-43ec-8f9f-e940a4dbdb2c&width=768&dpr=3&quality=100&sign=ec577734&sv=2) * **Updated Explanation**: The **Acceptance Rate** is a percentage of displayed suggestions that were accepted. * * * #### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption/cursor-expanded-metrics-guide#id-3-ways-of-using-cursor-and-how-ai-loc-is-calculated) 🌟 3 Ways of Using Cursor and How AI LOC is Calculated Cursor provides developers with multiple ways to interact with AI suggestions. The method of interaction affects how AI LOC is calculated. Here are three common usage scenarios: **1\. Using Cursor on the the right side of Cursor IDE (Standard Use)** * **How it works**: The developer receives AI suggestions in the code editor, either as suggestions or inline code completions. These suggestions are explicitly accepted by the developer and added directly to the code. * **AI LOC Calculation**: In this case, the **Total AI LOC** is calculated based on the lines added or deleted by the AI suggestions that the developer accepted. Both **Accepted Lines Added** and **Accepted Lines Deleted** are counted in the total AI lines. * **Example**: If the AI suggests adding a new function and the developer click on **Apply** and accepts it, those lines are counted as **AI LOC**. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FfjNSdSP57CfQXw5YgpdX%252Fimage.png%3Falt%3Dmedia%26token%3D07fdb6b2-61cc-4760-b559-050cc98e5ecb&width=300&dpr=3&quality=100&sign=9aa039ea&sv=2) **2\. Inline Cursor Usage** * **How it works**: The developer views AI suggestions by selecting a portion of code and click on Quick edit and chat with Agent or GPT odel * **AI LOC Calculation**: In this scenario, **AI LOC is counted**. * **Example**: The developer took quick help for formatting a block of code. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FL5gFvPl6ao64Yvz0oa31%252Fimage.png%3Falt%3Dmedia%26token%3Dd3cb817e-f824-44f5-be4d-7d2977c12e22&width=300&dpr=3&quality=100&sign=1788aa6b&sv=2) **3\. Using Tab Mode (AI LOC not counted)** * **How it works**: The developer uses the AI suggestion directly by click on tab which helps in autocompletion of the code * **AI LOC Calculation**: **AI LOC is not counted** in this case because the developer has not accepted the suggestion as-is. In this case, you get tabs accepted. * **Example**: The developer needs help with autocompletion of code. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FX93WJnubJf4QkkVk2OqH%252Fimage.png%3Falt%3Dmedia%26token%3D880b8cc9-5dc3-4958-9b6c-124c08829a59&width=300&dpr=3&quality=100&sign=9ca3a0d4&sv=2) #### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption/cursor-expanded-metrics-guide#user-classification) 👤 **User Classification** **✅ Active Users** A user is marked as **active** if they: * Received a suggestion. * Edited a file with Cursor open. * Opened Cursor Composer (chat). * Accepted a suggestion. **❌ Inactive Users** A user is marked as **inactive** if no AI interaction occurred on a given day, even if the IDE was open. * **Coverage**: Coverage charts reflect the percentage of active users daily or weekly. **Hivel Calculations for Active/Inactive Users**: * **Active Users** = Number of unique users with **isActive = true** at least once in the selected period. * **Inactive Users** = Total unique users (with any usage record) - Active Users. * * * #### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption/cursor-expanded-metrics-guide#technical-foundations) 🧱 **Technical Foundations** * **Tracking**: Metrics are tracked on a per-user, per-day basis. * **Reset**: Metrics are reset daily, with historical data available for up to 90 days prior to your integration. **⚠️ Known Limitations** * **Cursor Suggested Lines Not Accepted**: If the lines suggested by Cursor are shown but not accepted (for instance, when the suggestion is staged but not applied to the code), **the LOC will show as 0**. * **Copy-Pasting**: If a developer copy-pastes content from a suggestion without accepting it via the IDE, it will **not** be counted as AI lines, and the LOC will show as 0. * **Modified Usage**: Any changes made to the code that were inspired by AI suggestions but not directly accepted (such as rewriting or modifying code based on AI suggestions) will not be tracked or counted. * **Offline Use**: If Cursor is used offline, no data is captured. Any actions performed during offline sessions are not counted in the metrics. **Summary**: **Cursor's metrics primarily track explicit interactions** with AI suggestions and not actions like copy-pasting or modified usage. This can lead to an **underestimation of AI influence**. * * * #### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption/cursor-expanded-metrics-guide#sample-cursor-daily-record) 📦 **Sample Cursor Daily Record** **Field** **Value** **email** [\[email protected\]](https://docs.hivel.ai/cdn-cgi/l/email-protection) **date** 2025-07-29 **isActive** true **totalTabsShown** 98 **totalTabsAccepted** 22 **acceptedLinesAdded** 105 **acceptedLinesDeleted** 16 **composerRequests** 6 **composerSuggestionsAccepted** 2 total**linesAdded** 310 total**linesDeleted** 48 This sample shows interactions for one day, with detailed metrics on **suggestions shown**, **accepted**, and the number of **AI lines** added by the developer. * * * #### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption/cursor-expanded-metrics-guide#faqs) **FAQs** **Q) Are Metrics Tied to Commits?** All four metrics (totalLinesAdded, totalLinesDeleted, acceptedLinesAdded, acceptedLinesDeleted) are based on editor activity. Cursor tracks changes as they happen in the editor, not when the code is committed or pushed. The "raw count of all code changes" refers to the actual edits made in the editor, regardless of whether those changes are later committed. **Q) If a user accepts an AI suggestion but later deletes the code or never commits/pushes it — does it still count in acceptedLinesAdded/Deleted for that day?** Yes, if a user accepts an AI suggestion, it will be counted in **acceptedLinesAdded**/**acceptedLinesDeleted** for that day, even if the code is later deleted or never committed. These metrics track the **initial acceptance** of AI suggestions within the editor. * * * [PreviousCursor Adoptionchevron-left](https://docs.hivel.ai/ai-adoption/cursor-adoption) [NextHivel AI Impact Screen: Overview & Insightschevron-right](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights) Last updated 7 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Lucy | Hivel Lucy is the Hivel assistant that allows you to retrieve engineering metrics and trends through simple prompts. Instead of navigating through multiple dashboards or Cockpit views, Lucy helps you quickly surface data such as team trends, contributor rankings, or potential hotspots across repositories. Lucy is currently in **Beta**, so the scope of questions it can answer is gradually increasing. The goal at this stage is to help teams quickly explore trends and summaries without replacing the existing dashboards. For deeper analysis or detailed drilldowns, the Cockpit dashboards remain the most reliable and comprehensive way to explore data. circle-info Lucy's scope is restricted to GIT-related metrics for the Beta phase. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F4Qn8TiYmmXiefMbH6ep7%252FScreen%2520Cast%25202026-03-11%2520at%25204.26.38%2520PM.gif%3Falt%3Dmedia%26token%3Db1b58034-3e04-4217-b18c-0b6cbc7bbb26&width=768&dpr=3&quality=100&sign=21472a9c&sv=2) * * * [hashtag](https://docs.hivel.ai/using-hivel/lucy#what-lucy-helps-with) What Lucy Helps With ------------------------------------------------------------------------------------------------ Lucy currently focuses on a few specific use cases where quick visibility is helpful. ### [hashtag](https://docs.hivel.ai/using-hivel/lucy#generate-trends-across-multiple-metrics) Generate Trends Across Multiple Metrics Lucy can generate trend views for multiple metrics across a time period for the org or teams or authors. This allows users to quickly understand how several engineering metrics move together without switching between different screens. Example questions: * Show the trend of cycle time, review time, and merge time for Team @Ninjas over the last 3 months * Compare coding time and PR size trends for the @Payments team in the last quarter * Show review time trend for @Harry in the last 60 days **Why this is useful** On the Cockpit dashboards you can drill into individual metrics. Lucy helps combine multiple metrics together in one quick view so that trends can be spotted faster. * * * ### [hashtag](https://docs.hivel.ai/using-hivel/lucy#identify-bottlenecks-or-hotspots) Identify Bottlenecks or Hotspots Lucy can highlight potential bottlenecks across repositories for certain metrics. **Example questions:** * Which repositories have the highest unreviewed PRs * Show repos with the highest hotfix rate in the last 90 days * Identify teams with the most unreviewed PRs These queries help quickly surface areas that may need attention before exploring them in detail in Cockpit. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FMxTvhQCnChNyUb0WKtRQ%252Fimage.png%3Falt%3Dmedia%26token%3De6e34876-78bc-4690-8b44-790f5af19ac4&width=768&dpr=3&quality=100&sign=76fe42a0&sv=2) * * * ### [hashtag](https://docs.hivel.ai/using-hivel/lucy#identify-top-contributors) Identify Top Contributors Lucy can identify authors or teams that contribute the most toward specific metrics. **Example questions:** * Who are the top contributors in the @Payments repository this month * Show authors with the highest number of merged PRs in the last 30 days * Which teams contributed the most commits last quarter This can help teams quickly identify activity levels across contributors or teams. * * * [hashtag](https://docs.hivel.ai/using-hivel/lucy#current-state-of-lucy) Current State of Lucy -------------------------------------------------------------------------------------------------- Lucy is currently in **Beta**, which means we are actively improving both the intelligence and the range of questions it can answer. **At this stage:** * The scope of supported questions is small * Responses may be basic compared to Cockpit dashboards * Trend representations may not always capture the full context of the data * Some prompts may not return results if they fall outside the supported query patterns Lucy is designed to **assist quick exploration**, not replace Cockpit dashboards or detailed analysis workflows. * * * [hashtag](https://docs.hivel.ai/using-hivel/lucy#when-to-use-lucy-vs-cockpit) When to Use Lucy vs Cockpit -------------------------------------------------------------------------------------------------------------- **Use Lucy when you want to:** * Quickly check trends across multiple metrics * Identify hotspots across repositories or teams * Find top contributors or activity patterns **Use Cockpit dashboards when you need:** * Deep drilldowns * Detailed PR level analysis * Custom filters or precise metric investigation * * * [hashtag](https://docs.hivel.ai/using-hivel/lucy#example-prompts-to-try) Example Prompts to Try ---------------------------------------------------------------------------------------------------- **Here are a few prompts that typically work well:** • Show cycle time trend for the Y team in the last 3 months • Compare review time and coding time for Team X this quarter • Which repositories have the highest unreviewed PRs • Show the top contributors by merged PRs in the last 30 days • Identify repos with the highest hotfix rate this quarter * * * ### [hashtag](https://docs.hivel.ai/using-hivel/lucy#how-to-enable-lucy) How to enable Lucy Lucy can be enabled from [Configurationsarrow-up-right](https://app.hivel.ai/settings/configuration) -> AI -> Lucy ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FUOvFIAPtfCXjagUqOCPR%252Fimage.png%3Falt%3Dmedia%26token%3D7c637cfb-99c0-4ab9-8aca-4af964091f67&width=768&dpr=3&quality=100&sign=9ad69573&sv=2) [PreviousSetting Up Slack to Receive Hivel Alertschevron-left](https://docs.hivel.ai/using-hivel/alerts-in-hivel/setting-up-slack-to-receive-hivel-alerts) [NextHivel Scorechevron-right](https://docs.hivel.ai/using-hivel/hivel-score) Last updated 1 day ago * [What Lucy Helps With](https://docs.hivel.ai/using-hivel/lucy#what-lucy-helps-with) * [Generate Trends Across Multiple Metrics](https://docs.hivel.ai/using-hivel/lucy#generate-trends-across-multiple-metrics) * [Identify Bottlenecks or Hotspots](https://docs.hivel.ai/using-hivel/lucy#identify-bottlenecks-or-hotspots) * [Identify Top Contributors](https://docs.hivel.ai/using-hivel/lucy#identify-top-contributors) * [Current State of Lucy](https://docs.hivel.ai/using-hivel/lucy#current-state-of-lucy) * [When to Use Lucy vs Cockpit](https://docs.hivel.ai/using-hivel/lucy#when-to-use-lucy-vs-cockpit) * [Example Prompts to Try](https://docs.hivel.ai/using-hivel/lucy#example-prompts-to-try) * [How to enable Lucy](https://docs.hivel.ai/using-hivel/lucy#how-to-enable-lucy) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to update the name of an user? | Hivel 1. Go to **Settings** → **Users**. 2. Search for the user in the search bar 3. Select the edit icon next to their name 4. Edit name 5. Click **Update** [PreviousHow to merge users?chevron-left](https://docs.hivel.ai/set-up/users/how-to-merge-users) [NextCan I see the data of a user or repo that I don’t have access to on my SCM tool?chevron-right](https://docs.hivel.ai/set-up/users/can-i-see-the-data-of-a-user-or-repo-that-i-dont-have-access-to-on-my-scm-tool) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to Encourage Jira Hygiene Without Creating Friction | Hivel chevron-right**One Pager Sprint Hygiene Checklist**[hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#one-pager-sprint-hygiene-checklist) ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#before-starting-every-sprint) Before Starting Every Sprint ☐ All tickets in the sprint have story points ☐ All tickets are linked to an Epic ☐ All tickets have a single assignee ☐ Sprint scope has team agreement before clicking Start Sprint * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#during-the-sprint) During the Sprint ☐ Avoid adding new tickets unless work is urgent or blocking ☐ Any ticket added mid-sprint is clearly marked as unplanned ☐ If new work is added, discuss scope tradeoffs in standups ☐ Update story points only if scope or complexity truly changes * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#before-moving-tickets-to-done) Before Moving Tickets to Done ☐ Work fully meets the team’s Definition of Done ☐ No open subtasks remain ☐ Required fields such as resolution are set ☐ Done reflects real completion, not just code finished * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#before-closing-the-sprint) Before Closing the Sprint ☐ All completed tickets are in Done ☐ Incomplete tickets are moved to the next sprint and re-estimated if needed ☐ Done tickets are not carried forward ☐ Sprint is closed on time without extending dates * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#recommended-low-effort-automations) Recommended Low-Effort Automations ☐ Flag tickets added after sprint start as unplanned ☐ Block Done if required fields or subtasks are incomplete ☐ Auto-set resolution when issues move to Done ☐ Warn when issues enter a sprint without story points or Epic * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#board-visibility-checks) Board Visibility Checks ☐ Quick filter for tickets missing story points ☐ Quick filter for tickets without Epics ☐ Separate visibility for unplanned work ☐ Dashboards shared with the team, not just managers * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#key-principle-to-remember) Key Principle to Remember Jira hygiene should be **automatic, visible, and enforced at key moments**. If it relies on reminders or manual policing, it will not scale. Effective Jira hygiene is not about enforcing discipline through reminders. It is about configuring Jira so that clean data is the default outcome. The steps below are ordered by **impact vs effort**. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-1.-enforce-hygiene-at-sprint-boundaries) 1\. Enforce Hygiene at Sprint Boundaries Sprint boundaries are the single most important control point. #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#what-to-enforce) What to enforce Before starting a sprint, ensure that: * All work items in the sprint have story points * All work items are linked to an Epic * All work items have an assignee #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#how-to-implement) How to implement Option A. Sprint checklist approach * During sprint planning, filter the backlog by “Missing story points” and “No Epic” * Resolve these in bulk before clicking Start Sprint **Option B. Automation approach (recommended)** * Create a Jira Automation rule that triggers when a sprint starts * Condition: work items in sprint missing required fields * Action: comment on those work items or notify the sprint owner **Reference** Atlassian sprint planning best practices [https://www.atlassian.com/agile/scrum/sprint-planningarrow-up-right](https://www.atlassian.com/agile/scrum/sprint-planning) **Why this works** It prevents dirty data from entering the sprint without interrupting daily execution. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-2.-require-fields-only-when-they-become-relevant) 2\. Require Fields Only When They Become Relevant One of the biggest sources of friction is making fields mandatory too early. #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#recommended-pattern) Recommended pattern * Story points required only when an issue moves into an active sprint * Assignee required only when work starts * Epic required for stories and tasks, not necessarily for bugs #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#how-to-implement-1) How to implement * Use workflow validators on status transitions * Apply field requirements on “To Do → In Progress” or “Backlog → Sprint” **Reference** Jira workflow conditions and validators [https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/arrow-up-right](https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/) **Why this works** Contextual enforcement feels helpful instead of bureaucratic. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-3.-automate-what-humans-should-not-have-to-remember) 3\. Automate What Humans Should Not Have to Remember Automation should handle repetitive hygiene checks silently. #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#high-impact-automations-to-set-up) High-impact automations to set up 1. Flag unplanned work automatically * Trigger: issue added to an active sprint * Action: add label “unplanned” or comment explaining it was added mid-sprint 1. Auto-set resolution on Done * Trigger: issue transitions to Done * Action: set resolution field 1. Warn on missing estimates or ownership * Trigger: issue moved to In Progress * Condition: missing story points or assignee * Action: comment or notify **Reference** Jira Automation rule library [https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/arrow-up-right](https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/) **Why this works** Automation enforces consistency without social friction. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-4.-encode-definition-of-done-in-the-workflow) 4\. Encode Definition of Done in the Workflow Documentation alone does not enforce behavior. #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#what-to-enforce-in-jira) What to enforce in Jira * Prevent work items from moving to Done if: * Required fields are missing * Open subtasks still exist * QA or review steps are incomplete #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#how-to-implement-2) How to implement * Add workflow validators on the Done transition * Optionally auto-transition subtasks when the parent issue is completed **Reference** Defining and enforcing Done in Jira [https://www.atlassian.com/blog/jira/8-steps-to-a-definition-of-done-in-jiraarrow-up-right](https://www.atlassian.com/blog/jira/8-steps-to-a-definition-of-done-in-jira) **Why this works** It ensures Done reflects real completion and keeps reports trustworthy. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-5.-use-visibility-instead-of-hard-blocks-where-possible) 5\. Use Visibility Instead of Hard Blocks Where Possible Not every hygiene issue needs to be blocked. #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#recommended-visibility-patterns) Recommended visibility patterns * Board quick filters for “Missing story points” * Dashboard gadget for “Work items without Epics” * Separate swimlane or filter for unplanned work #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#how-to-implement-3) How to implement * Leverage Hivel's dashboards for the above. **Why this works** Teams naturally correct what they can see without being forced. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-6.-treat-sprint-start-and-end-dates-as-sacred) 6\. Treat Sprint Start and End Dates as Sacred Sprint dates directly affect velocity and reporting. #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#best-practices) Best practices * Do not start sprints retroactively * Do not extend sprints to “finish” work * Close sprints on time even if work remains **Reference** How Jira calculates velocity and sprint reports [https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/arrow-up-right](https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/) **Why this works** Accurate dates preserve long-term trend reliability. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-7.-clarify-story-points-vs-subtasks) 7\. Clarify Story Points vs Subtasks This prevents a very common reporting issue. #### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#guidance) Guidance * Story points should live on the parent issue * Subtasks are for execution breakdown only * Avoid estimating subtasks unless you fully understand the reporting impact **Why this works** Velocity and sprint reports rely on parent work items, not subtasks. * * * ### [hashtag](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#key-takeaway) Key Takeaway Jira hygiene works when: * Rules are enforced only at key moments * Automation replaces reminders * Visibility replaces micromanagement * Workflow gates protect data integrity If hygiene depends on people remembering rules, it will fail. If hygiene is encoded into Jira’s structure, it sustains itself. * * * [PreviousBest practices for adopting Story Pointschevron-left](https://docs.hivel.ai/best-practices/jira-best-practices/best-practices-for-adopting-story-points) [NextBest practices for AI usagechevron-right](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage) Last updated 3 months ago * [1\. Enforce Hygiene at Sprint Boundaries](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-1.-enforce-hygiene-at-sprint-boundaries) * [2\. Require Fields Only When They Become Relevant](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-2.-require-fields-only-when-they-become-relevant) * [3\. Automate What Humans Should Not Have to Remember](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-3.-automate-what-humans-should-not-have-to-remember) * [4\. Encode Definition of Done in the Workflow](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-4.-encode-definition-of-done-in-the-workflow) * [5\. Use Visibility Instead of Hard Blocks Where Possible](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-5.-use-visibility-instead-of-hard-blocks-where-possible) * [6\. Treat Sprint Start and End Dates as Sacred](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-6.-treat-sprint-start-and-end-dates-as-sacred) * [7\. Clarify Story Points vs Subtasks](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#id-7.-clarify-story-points-vs-subtasks) * [Key Takeaway](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction#key-takeaway) sun-brightdesktopmoon sun-brightdesktopmoon --- # Alerts in Hivel | Hivel Alerts let you know when important engineering metrics cross the thresholds you care about, so you don’t have to constantly check dashboards. [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#why-alerts-matter) Why Alerts Matter ----------------------------------------------------------------------------------------------------- ### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#for-executives-cto-vp-of-engineering) For Executives (CTO, VP of Engineering) * Get signals when org-wide delivery metrics move out of healthy ranges (like Cycle Time, MTTR, Release Merge Frequency, Change Failure Rate, etc.) * Stay ahead of reliability issues without digging across dashboards * Keep a steady pulse on team performance across the org ### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#for-engineering-managers-team-leads) For Engineering Managers/Team Leads * Catch slowdowns early (for example: Cycle Time > 5 days) * Monitor team-wide patterns before sprint planning or reviews * Maintain alignment with expectations and avoid last-minute surprises ### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#for-developers) For Developers * Get nudges when your PRs wait too long for review * Monitor personal patterns like coding time, review time, or PR activity * Stay aware of your own trends without manually checking dashboards [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#alert-types-scopes) Alert Types (Scopes) --------------------------------------------------------------------------------------------------------- Hivel supports three alert scopes. Each scope controls what the alert monitors: ### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#id-1.-organization-level-alerts) 1\. Organization-Level Alerts * Watch metrics across the entire org * Great for executives or central engineering operations * Only admins / execs with “complete data visibility” can configure them ### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#id-2.-team-level-alerts) 2\. Team-Level Alerts * Monitor metrics for a single team * Ideal for managers responsible for specific groups ### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#id-3.-personal-alerts) 3\. Personal Alerts * Users can set alerts for themselves or any other individual, on teams they choose * Great for PR reminders or personal productivity patterns [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#before-you-start-permissions) Before You Start - Permissions ----------------------------------------------------------------------------------------------------------------------------- Make sure your role is assigned the correct permissions in the [Access Managementarrow-up-right](https://app.hivel.ai/settings/rbac) screen: * **Modify Alerts** – Create/edit/delete alerts (Org & Team level) * **View Alerts Menu** – Access the alert dashboard * **Modify Alerts Config** – Configure Slack channels & digests (Org & Team level only) * **Personal Alerts** – Create/edit personal alerts regardless of access to above permissions ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FhyWfMtJLyVe9FiUA7tIq%252Fimage.png%3Falt%3Dmedia%26token%3D4b3cf31a-b1c2-4dc7-912b-de1a7ddfd044&width=768&dpr=3&quality=100&sign=325cb27b&sv=2) [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#how-to-set-up-an-alert-step-by-step) How to Set Up an Alert (Step-by-Step) ------------------------------------------------------------------------------------------------------------------------------------------- Navigate to **Alerts** under **Overview**, choose the scope you want, and click on "New Alert". ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FnYbAE8NTZTCH8wHjiKHQ%252Fimage.png%3Falt%3Dmedia%26token%3Dd21fc426-908b-4a6b-86ae-588501ff9500&width=768&dpr=3&quality=100&sign=c99318c9&sv=2) Here is a short walkthrough of the Alerts setup process: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F5nwRFlROh4hA0CAVexnH%252FScreen%2520Recording%25202025-12-10%2520at%252011.27.03%25E2%2580%25AFAM.gif%3Falt%3Dmedia%26token%3D30df114d-81f0-4795-a869-d1c6a7114e81&width=768&dpr=3&quality=100&sign=8c3e16e6&sv=2) #### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#id-1.-choose-your-metric-and-set-the-threshold) 1\. Choose your metric & set the threshold Note: * A metric can only have one alert per scope _(Example: only one Cycle Time alert allowed at the org level)_ * Metrics already used at that level won’t appear in the dropdown #### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#id-2.-choose-when-the-alert-should-fire) 2\. Choose when the alert should fire Hivel uses time-window averages, not real-time checks, to avoid spam. You can either: * Use an existing Digest schedule * Or set a Custom schedule for just this alert (daily, weekly, or monthly) > Note: If you choose a date above 28 for a monthly alert, the system will warn you that alerts won’t fire for the months that don’t have those dates. #### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#id-3.-select-recipients) 3\. Select recipients You can send alerts to: * Slack * Email * Or both > **Note:** For Slack, make sure you've integrated it with Hivel and set up the Slack channels ([details in this guidearrow-up-right](https://docs.hivel.ai/using-hivel/alerts-in-hivel/setting-up-slack-to-receive-hivel-alerts) > ). #### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#id-4.-review-and-save) 4\. Review & save Review the Alert settings and click Save. Your alert will now appear in the Alerts table. ### [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#creating-a-digest-optional) Creating a Digest (Optional) Digests help you group multiple alerts into a single scheduled summary to avoid notification overload. To create one: 1. Go to Alerts → Settings ⚙️ icon → Digests 2. Create a digest with a name, timing, recipients, and Slack channel or emails. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FGR2F3tWi0r0ZNqPwPU2d%252Fimage.png%3Falt%3Dmedia%26token%3D023a9877-f3f3-465f-ac56-23319283ec04&width=768&dpr=3&quality=100&sign=920e9c41&sv=2) 3. Assign alerts to this digest during alert creation. circle-info **Note:** If a digest does not have any email recipients configured, you will not be able to add email addresses during alert creation. In this case, update the email recipients in the digest configuration first, and then proceed to create the alert. [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#how-hivel-manages-alerts-behind-the-scenes) How Hivel Manages Alerts Behind the Scenes ------------------------------------------------------------------------------------------------------------------------------------------------------- * Only one alert per metric per scope is allowed. * Each scope (Org, Team, Personal) can have its own Slack channel. * If a digest is deleted, all linked alerts automatically switch to custom schedules using the digest’s original timing. * If a Slack channel is deleted, alerts using only Slack are disabled until a new channel is added. * If a team in an alert is deleted, the alert becomes inactive until updated. [hashtag](https://docs.hivel.ai/using-hivel/alerts-in-hivel#need-help) Need Help? -------------------------------------------------------------------------------------- If you’re unable to see Alert options or need assistance setting things up, reach us at [\[email protected\]](https://docs.hivel.ai/cdn-cgi/l/email-protection) . [PreviousPerformance Appraisalchevron-left](https://docs.hivel.ai/using-hivel/performance-appraisal) [NextSetting Up Slack to Receive Hivel Alertschevron-right](https://docs.hivel.ai/using-hivel/alerts-in-hivel/setting-up-slack-to-receive-hivel-alerts) Last updated 1 month ago * [Why Alerts Matter](https://docs.hivel.ai/using-hivel/alerts-in-hivel#why-alerts-matter) * [For Executives (CTO, VP of Engineering)](https://docs.hivel.ai/using-hivel/alerts-in-hivel#for-executives-cto-vp-of-engineering) * [For Engineering Managers/Team Leads](https://docs.hivel.ai/using-hivel/alerts-in-hivel#for-engineering-managers-team-leads) * [For Developers](https://docs.hivel.ai/using-hivel/alerts-in-hivel#for-developers) * [Alert Types (Scopes)](https://docs.hivel.ai/using-hivel/alerts-in-hivel#alert-types-scopes) * [1\. Organization-Level Alerts](https://docs.hivel.ai/using-hivel/alerts-in-hivel#id-1.-organization-level-alerts) * [2\. Team-Level Alerts](https://docs.hivel.ai/using-hivel/alerts-in-hivel#id-2.-team-level-alerts) * [3\. Personal Alerts](https://docs.hivel.ai/using-hivel/alerts-in-hivel#id-3.-personal-alerts) * [Before You Start - Permissions](https://docs.hivel.ai/using-hivel/alerts-in-hivel#before-you-start-permissions) * [How to Set Up an Alert (Step-by-Step)](https://docs.hivel.ai/using-hivel/alerts-in-hivel#how-to-set-up-an-alert-step-by-step) * [Creating a Digest (Optional)](https://docs.hivel.ai/using-hivel/alerts-in-hivel#creating-a-digest-optional) * [How Hivel Manages Alerts Behind the Scenes](https://docs.hivel.ai/using-hivel/alerts-in-hivel#how-hivel-manages-alerts-behind-the-scenes) * [Need Help?](https://docs.hivel.ai/using-hivel/alerts-in-hivel#need-help) sun-brightdesktopmoon sun-brightdesktopmoon --- # Users | Hivel [How to invite more users to use Hivel?chevron-right](https://docs.hivel.ai/set-up/users/how-to-invite-more-users-to-use-hivel) [How to add or update an user's email id?chevron-right](https://docs.hivel.ai/set-up/users/how-to-add-or-update-an-users-email-id) [How to merge users?chevron-right](https://docs.hivel.ai/set-up/users/how-to-merge-users) [How to update the name of an user?chevron-right](https://docs.hivel.ai/set-up/users/how-to-update-the-name-of-an-user) [Can I see the data of a user or repo that I don’t have access to on my SCM tool?chevron-right](https://docs.hivel.ai/set-up/users/can-i-see-the-data-of-a-user-or-repo-that-i-dont-have-access-to-on-my-scm-tool) [How to archive users?chevron-right](https://docs.hivel.ai/set-up/users/how-to-archive-users) [PreviousHow to sign up to Hivel?chevron-left](https://docs.hivel.ai/set-up/sign-up/how-to-sign-up-to-hivel) [NextHow to invite more users to use Hivel?chevron-right](https://docs.hivel.ai/set-up/users/how-to-invite-more-users-to-use-hivel) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to archive users? | Hivel Archiving users is essential when individuals leave the organization or when their data is no longer relevant. Regularly doing this activity helps ensure that metrics remain accurate and free of unnecessary data. To archive users, you can simply: 1. Go the Setting screen -> Teams 2. Select the particular users 3. Click on Archive button in the top right ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FUt20UNkXUhjCXlielgFs%252FGIF%2520Recording%2520Aug%252022%2520from%2520Jumpshare.gif%3Falt%3Dmedia%26token%3D4560f275-55ad-463f-a85e-55fd6983022a&width=768&dpr=3&quality=100&sign=5974f2cc&sv=2) To unarchive any user, please reach out to [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#cdbeb8bdbda2bfb98da5a4bba8a1e3aca4) . [PreviousCan I see the data of a user or repo that I don’t have access to on my SCM tool?chevron-left](https://docs.hivel.ai/set-up/users/can-i-see-the-data-of-a-user-or-repo-that-i-dont-have-access-to-on-my-scm-tool) [NextTeamschevron-right](https://docs.hivel.ai/set-up/teams) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Team Versioning | Hivel ### [hashtag](https://docs.hivel.ai/set-up/team-versioning#what-is-team-versioning) What is Team Versioning? **Team Versioning** provides the flexibility to view metrics based on **how teams were structured during the selected time period**, preserving historical accuracy. By default, Hivel metrics reflect the current team structure - meaning that past metric values are calculated based on **today’s team structure**, not how the team was structured historically. **With Team Versioning enabled:** * Historical data remains intact. * Team member additions, removals, and transfer dates are respected. * Metrics reflect who was actually part of the team during the selected date range. This prevents productivity metrics from being retroactively distorted when team composition changes. * * * #### [hashtag](https://docs.hivel.ai/set-up/team-versioning#default-behavior-without-team-versioning) **🔍 Default Behavior (Without Team Versioning)** * Metrics are always calculated using the **current team structure**. * If an author moves teams, their past contributions are still shown under their **new team**, not where they were when the work was done. * Only current state data is visible. * Removing a team member from all the teams removes them from all views. * Historical contributions are not time-aware. **Example:** * Author A was in Team B from Jan to Feb. * In March, Author A is moved to Team C. * You view Team B metrics from **Jan 15 – Feb 15**: 👉 Without Team Versioning, **Author A's contributions will not show** under Team B (since they are now in Team C). * * * #### [hashtag](https://docs.hivel.ai/set-up/team-versioning#behavior-with-team-versioning-enabled) **📦 Behavior With Team Versioning Enabled** With Team Versioning enabled, Hivel utilizes **historical team structures** to calculate metrics. This ensures each metric reflects which authors were part of a team **at the time the work occurred**. * Historical data is preserved. * Visibility is filtered by the selected date range. * Contributions remain visible for the period when the member was active. * No new data for a team is shown after the member’s exit date from the team. **Example 1:** * Author A is in Team B (Jan–Feb), then moved to Team C in March. * You view metrics for: * **Jan 15 – Feb 15**: ✅ Author A's contributions appear in **Team B** metrics. * **Mar 15 – Apr 15**: ❌ Author A's contributions do **not** appear in Team B metrics, but are part of Team C instead. **Example 2:** Team members: X, Y, Z * X and Y are existing employees. * Z joined the team on March 20, 2026. Selected date range: February 2026 * Visible members: X, Y Selected date range: Feb 22 – March 19, 2026 * Visible members: X, Y Selected date range: Feb 22 – March 20, 2026 * Visible members: X, Y, Z If Y exits the team on March 20, 2026: * Y’s historical contributions remain visible for periods prior to March 20, 2026. * No new activity from Y is shown from March 21, 2026. **Example 3:** Assume Teams A and B both had 10 members in January 2026. * 3 members were removed from Team A effective January 31, 2026. * 3 members were removed from Team B effective February 28, 2026. If **February 2026** was selected and teams are viewed separately: * Team A shows **7** total members (the 3 members already left). * Team B shows **10** total members (removal of 3 members occur at the end of February). ### [hashtag](https://docs.hivel.ai/set-up/team-versioning#metric-calculation-note-duration-sensitivity) Metric calculation note (duration sensitivity) * Weekly metrics are normalized to a 7-day week. * If a member was active for only part of a week (for example, 2 days) and then left the team or organization, the metric is still divided by 7. As a result, that member’s weekly metric may appear lower than expected when viewed at weekly granularity. * * * circle-info **Please Note:** The feature is based solely on user movement across teams, rather than the actual teams themselves. If a team is removed from Hivel, all the associated versioning data will not be retained. ### [hashtag](https://docs.hivel.ai/set-up/team-versioning#summary-and-troubleshooting-checklist) Summary and troubleshooting checklist Team Versioning provides: * Historically accurate reporting * Date-aware visibility based on join and exit dates * More reliable metrics and insights during team changes If a dashboard or metric looks inconsistent, verify: * The selected date range * Members join and exit dates #### [hashtag](https://docs.hivel.ai/set-up/team-versioning#why-use-team-versioning) **📌 Why Use Team Versioning?** We recommend using Team Versioning to: * Analyze metrics accurately for historical team performance. * Avoid misleading trends caused by team structure changes. * Support performance reviews and retrospectives based on actual team dynamics at the time. If you’re unsure whether Team Versioning is enabled or want to enable it, reach out to [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#5724222727382523173f3e21323b79363e) . [PreviousLabelschevron-left](https://docs.hivel.ai/set-up/labels) [NextIntegrationschevron-right](https://docs.hivel.ai/integrations) Last updated 25 days ago * [What is Team Versioning?](https://docs.hivel.ai/set-up/team-versioning#what-is-team-versioning) * [Metric calculation note (duration sensitivity)](https://docs.hivel.ai/set-up/team-versioning#metric-calculation-note-duration-sensitivity) * [Summary and troubleshooting checklist](https://docs.hivel.ai/set-up/team-versioning#summary-and-troubleshooting-checklist) sun-brightdesktopmoon sun-brightdesktopmoon --- # Team level Hivel Score Calculation | Hivel ### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#what-is-the-team-level-hivel-score) What is the Team-Level Hivel Score? The Team-Level Hivel Score gives you a focused view of how a specific team - and its sub-teams - are performing across Speed, Quality, and Throughput. It uses the same scoring framework as the org level, but scoped to the team you select, letting you drill deeper into performance patterns within your org. * * * ### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#setting-up-your-configuration) Setting Up Your Configuration The same configuration used at the org level applies here. If you've already set your bucket weights (Speed, Quality, Throughput totalling 100%), you're all set. Scores are calculated only after configuration is saved and are visible for completed months only. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fl1wX60l3Ft2Nwp7tJJVA%252Fimage.png%3Falt%3Dmedia%26token%3Ddfbf26a0-e66e-42d5-8582-433c7ead8090&width=768&dpr=3&quality=100&sign=24ebb1da&sv=2) * * * ### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#how-the-team-level-hivel-score-is-calculated) How the Team-Level Hivel Score is Calculated The score is built bottom-up - from individual metric scores, to bucket scores, to a final team score. #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#step-1-metric-scores-0-100-scale) Step 1: Metric Scores (0–100 scale) Each metric (e.g., Commits, Review Time) is scored by comparing a sub-team's value against all sub-teams' performance over a **rolling 6-month window**, including the current month. This keeps scores contextual and reflective of recent trends. To ensure scores aren't skewed by extreme outliers or inactive periods, the following data cleaning is applied before scoring: * Values of **0 are excluded** (treated as no activity) * The **top and bottom 2%** of values are removed The remaining values set the scoring range (min to max). Each sub-team's current month value is then plotted within this range to produce a 0–100 score. Sub-teams with no activity (zero value) score 0, while those at the very top of the range score 100. **Example - Metric: Commits, Month: January** Here's how 6 months of Commits data across sub-teams translates into January scores: Sub-Team Jan Commits Score A 0 0 (no activity) B 120 36.6 C 89 21.46 D 300 100 (top outlier) E 72 13.17 F 0 0 (no activity) After removing zeros and 2% outliers from all 6 months of data, the scoring range is set at **Min = 45, Max = 250**. Each sub-team's January value is scored within this range. Sub-team D's value of 300 falls above the top 2% threshold, so it automatically scores 100. #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#step-2-bucket-scores) Step 2: Bucket Scores Within each bucket, metrics carry predefined weights. A sub-team's bucket score is the weighted average of its individual metric scores. _Example - Throughput bucket with Commits (60%) and PRs Merged (40%):_ A sub-team scoring 80 on Commits and 70 on PRs Merged would receive a Throughput score of **76**. #### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#step-3-final-team-hivel-score) Step 3: Final Team Hivel Score The three bucket scores are combined using your configured weights to produce the final Hivel Score for each sub-team. _Example - with Speed 30%, Quality 40%, Throughput 30%:_ A sub-team with Speed = 60, Quality = 75, Throughput = 76 would receive a Hivel Score of **70.8**. * * * ### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#what-youll-see-on-the-dashboard) What You'll See on the Dashboard The team-level dashboard mirrors the org view, scoped to your selected team: * **Hivel Score** for the selected month, with a 6-month trend * **Score Trend Graph** - how the team's score has moved over the past 6 months * **Category Breakdown** - Speed, Quality, and Throughput scores with expandable metric detail, including each metric's score, weight, and change vs. the 6-month average * **Sub-Team Ranking Table** - all sub-teams ranked by score, showing % change vs. 6-month average > If the selected team has no sub-teams, the dashboard will display a "No sub-teams available" message. * * * ### [hashtag](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#a-few-things-to-keep-in-mind) A Few Things to Keep in Mind * Scores use a **rolling 6-month window**, so they naturally adapt as your team's performance evolves * Sub-teams with **no activity** on a metric receive a score of 0 for that metric * Scores are only visible for **completed months** - no mid-month previews * If no data is available, the score will show as **0** * * * _For questions or help with your configuration, please reach out to our support team._ [PreviousOrg level Hivel Score Calculationchevron-left](https://docs.hivel.ai/using-hivel/hivel-score/org-level-hivel-score-calculation) [NextMetrics & Definitionschevron-right](https://docs.hivel.ai/metrics-and-definitions) Last updated 1 day ago * [What is the Team-Level Hivel Score?](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#what-is-the-team-level-hivel-score) * [Setting Up Your Configuration](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#setting-up-your-configuration) * [How the Team-Level Hivel Score is Calculated](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#how-the-team-level-hivel-score-is-calculated) * [What You'll See on the Dashboard](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#what-youll-see-on-the-dashboard) * [A Few Things to Keep in Mind](https://docs.hivel.ai/using-hivel/hivel-score/team-level-hivel-score-calculation#a-few-things-to-keep-in-mind) sun-brightdesktopmoon sun-brightdesktopmoon --- # Teams | Hivel [How to create teams?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-create-teams) [How to delete a team?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-delete-a-team) [How to modify a team?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-modify-a-team) [How to create sub-teams?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-create-sub-teams) [How to add users to a team and sub-team?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-add-users-to-a-team-and-sub-team) [How to remove users from a team or sub-team?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-remove-users-from-a-team-or-sub-team) [PreviousHow to archive users?chevron-left](https://docs.hivel.ai/set-up/users/how-to-archive-users) [NextHow to create teams?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-create-teams) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to add or update an user's email id? | Hivel To do this, go to **Settings** → **Users**. 1. Search for the user in the search bar. 2. Click on the entry. 3. In the right panel that pops up, click on the pencil icon. 4. Add the mail ID in the field and hit "Save". ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FMAO1vM5V9idnA29moz2y%252Fimage.png%3Falt%3Dmedia%26token%3D18215426-daaa-438a-a1fb-1a73816f1a86&width=768&dpr=3&quality=100&sign=9806c20c&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FSbV78TafYtqpjV114vyE%252Fimage.png%3Falt%3Dmedia%26token%3Df986be37-08e0-417c-90d4-bb4bc5065e65&width=768&dpr=3&quality=100&sign=1d163d07&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F9iypopdwo2F0AQ7XcMKd%252Fimage.png%3Falt%3Dmedia%26token%3D13818e11-8a1a-4ee7-b9b7-144962ce1703&width=768&dpr=3&quality=100&sign=8201be67&sv=2) circle-exclamation **Please note:** You can add a user's email id if it isn't there already, **but you cannot edit an existing email id.** Please contact [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#9eedebeeeef1eceadef6f7e8fbf2b0fff7) to change the email id. [PreviousHow to invite more users to use Hivel?chevron-left](https://docs.hivel.ai/set-up/users/how-to-invite-more-users-to-use-hivel) [NextHow to merge users?chevron-right](https://docs.hivel.ai/set-up/users/how-to-merge-users) Last updated 6 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Cursor Adoption | Hivel circle-info To integrate Cursor and start seeing the following metrics, see [_**here**_arrow-up-right](https://docs.hivel.ai/integrations/cursor-adoption) . Hivel's **Cursor Adoption** feature offers detailed insights into how well the Cursor AI is being utilized within a team or whole organization and how useful it is proving to be. * * * ### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption#overview) Overview **User Coverage Graph** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FeWeSueBOmhwIKBCwjm4T%252Fimage.png%3Falt%3Dmedia%26token%3D82584890-45e4-4d30-86d3-b44f82bb7df2&width=768&dpr=3&quality=100&sign=c22c375&sv=2) * This graph shows the trend of **active** and **inactive** users over different time periods (weekly, monthly, quarterly). * It provides a high-level overview of Cursor adoption across teams and helps identify periods of higher or lower engagement. #### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption#suggestions-acceptance-rate) **Suggestions Acceptance Rate** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FUemcxknXj8JNC9y4wBRb%252Fimage.png%3Falt%3Dmedia%26token%3D6e5de83d-6c7f-43c4-98ba-6488625cdfed&width=768&dpr=3&quality=100&sign=ec54c7fc&sv=2) * This metric shows how useful users find Cursor’s suggestions. A higher acceptance rate indicates that users are finding the suggestions useful enough to directly accept them. #### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption#ai-vs-manual-code) **AI vs Manual Code** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FnU98webcdwUt5aJfxrAS%252Fimage.png%3Falt%3Dmedia%26token%3D68e21bba-a7c1-4da2-9b1f-b58e1e93e1be&width=768&dpr=3&quality=100&sign=7e69b4d0&sv=2) * This graph helps you understand the volume of **AI-generated code** versus manually written code in your codebase. * Even if the suggestions acceptance rate is high, this graph reveals whether users are integrating Cursor deeply into their workflow or just using it occasionally. * A lower percentage of AI-generated code indicates that users might be using Cursor as an afterthought rather than as a central part of their workflow. #### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption#ai-models-and-extensions) **AI Models and Extensions** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F4bLARxCyG7vlhvCmdJEp%252Fimage.png%3Falt%3Dmedia%26token%3D03ccefc7-2874-402e-9b20-32662c16caab&width=768&dpr=3&quality=100&sign=482ce44f&sv=2) * These charts show: * **AI Models**: Usage across different AI models in Cursor. * **Extensions**: Visualizes AI-generated code by programming languages * **Note**: Both charts exclude tab completions, focusing only on the core usage. #### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption#a-few-high-level-usage-metrics) A few high-level usage metrics ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Flrb1RM1rvjdYga060mfM%252Fimage.png%3Falt%3Dmedia%26token%3D067e12d1-4f5c-4d51-9226-a42de7acb5ab&width=768&dpr=3&quality=100&sign=7cd8d52&sv=2) **Total Paid Seats**: * This represents the number of licensed users in the current subscription cycle. * It is not tied to specific dates or teams, just the total number of users for the subscription. **Active Users**: * Active users are those who have engaged with Cursor during the selected time frame. Activities include logging in, accepting suggestions, writing code, or making requests. **Inactive Users**: * Inactive users are those who have not performed any actions within the selected time frame. circle-info The Active + Inactive count may differ from the Total Paid Seats because it is based on the selected timeframe and teams, which may not always match the total license count. **Total Bubot Calls**: * This counts the number of times **Bugbot** (Cursor's code review tool) has been used during the selected time frame. * * * ### [hashtag](https://docs.hivel.ai/ai-adoption/cursor-adoption#ai-usage-analysis) **AI Usage Analysis** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FhYPRl97QvwIxEu3C2mTO%252Fimage.png%3Falt%3Dmedia%26token%3D2e4a9a4c-d956-439a-94d4-69041008ec11&width=768&dpr=3&quality=100&sign=c0c13a73&sv=2) The **AI Usage Analysis** tab breaks down individual user activity, showing: * The total lines of code each user has written. * The percentage of code that was AI-generated versus manually written. **Cohorts for AI Usage** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FVslwguXZPxOP1wA6Erkr%252Fimage.png%3Falt%3Dmedia%26token%3D19c92e52-f424-4d0e-a825-a00a8ccde619&width=768&dpr=3&quality=100&sign=2314e8d6&sv=2) * **High Usage (>=70%)**: These are the top users who rely heavily on AI to assist in coding. * **Medium Usage (30-69%)**: These users make moderate use of AI in their coding. * **Low Usage (<30%)**: These users are minimally relying on AI. This segmentation is helpful for identifying your AI "trailblazers" (those with high usage) who can share best practices and tips with others who have low usage. By fostering collaboration between cohorts, your organization can maximize the value gained from Cursor. * * * By tracking these metrics and visualizations, you can gain valuable insights into how teams are using Cursor, who is benefiting most from its features, and where there may be opportunities to encourage greater adoption or improve workflow integration. [PreviousGitHub Copilot: Expanded Metrics Guidechevron-left](https://docs.hivel.ai/ai-adoption/copilot-adoption/github-copilot-expanded-metrics-guide) [NextCursor: Expanded Metrics Guidechevron-right](https://docs.hivel.ai/ai-adoption/cursor-adoption/cursor-expanded-metrics-guide) Last updated 8 months ago * [Overview](https://docs.hivel.ai/ai-adoption/cursor-adoption#overview) * [AI Usage Analysis](https://docs.hivel.ai/ai-adoption/cursor-adoption#ai-usage-analysis) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to merge users? | Hivel Sometimes, while importing users from Git, there may be a duplication of users because developers commit using their personal email ids or use the same personal access token on a different machine. In such cases you can merge multiple users into one primary user. circle-info Please note: **This action cannot be undone.** If you have mistakenly merged users together please contact [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#72010702021d0006321a1b04171e5c131b) for assistance. #### [hashtag](https://docs.hivel.ai/set-up/users/how-to-merge-users#here-is-how-to-merge-users-in-hivel) Here is how to merge users in Hivel: 1\. Go to **Settings** **→** **Users** 2\. Select the users you want to merge ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Foik2F8twIp8BFINx56o0%252Fimage.png%3Falt%3Dmedia%26token%3Dd0de3a0a-95d5-46d9-8198-310e04cac635&width=768&dpr=3&quality=100&sign=1c076c56&sv=2) 3\. Click on the **Merge** icon. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FyfqYZ4JmY9Clhx1nID0E%252Fimage.png%3Falt%3Dmedia%26token%3D83fab3ab-e6e2-41ab-9de1-0dfc5ceb3ef9&width=768&dpr=3&quality=100&sign=a3dfdfd4&sv=2) 4\. Select a primary user ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FN95u6NJvRWxLflTbB1iq%252Fimage.png%3Falt%3Dmedia%26token%3D7a364a6a-3552-42ee-9c52-07c89e783e2e&width=768&dpr=3&quality=100&sign=668a2cba&sv=2) 5\. Click **Merge** [PreviousHow to add or update an user's email id?chevron-left](https://docs.hivel.ai/set-up/users/how-to-add-or-update-an-users-email-id) [NextHow to update the name of an user?chevron-right](https://docs.hivel.ai/set-up/users/how-to-update-the-name-of-an-user) Last updated 6 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Can I see the data of a user or repo that I don’t have access to on my SCM tool? | Hivel No, you can not access any users or repositories on Hivel if you don’t have access to them on the SCM tool. [PreviousHow to update the name of an user?chevron-left](https://docs.hivel.ai/set-up/users/how-to-update-the-name-of-an-user) [NextHow to archive users?chevron-right](https://docs.hivel.ai/set-up/users/how-to-archive-users) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to create teams? | Hivel * Go to **Settings** → **Teams** → **Create Team** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FeXp0igiuOWQRxm9eUzuQ%252Fimage.png%3Falt%3Dmedia%26token%3D0a536ccb-944a-4bd3-b800-c9055fe18265&width=768&dpr=3&quality=100&sign=785ecc71&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F7D2VdjKUA04HJ2HLIPyq%252Fimage.png%3Falt%3Dmedia%26token%3D726db11b-103d-441c-87ef-d1a7b8319338&width=768&dpr=3&quality=100&sign=e89b5e04&sv=2) * Enter a team name and select a team owner. Don't worry, you can always change these later if needed. * Click **Create and add**. You can add additional members in the next step if required. * A single team member can be added to multiple teams. This way, you can classify an engineer into their squads, engineers by seniority, location, etc. [PreviousTeamschevron-left](https://docs.hivel.ai/set-up/teams) [NextHow to delete a team?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-delete-a-team) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to modify a team? | Hivel 1. Go to Settings → Teams 2. Select the team which you want to modify. 3. You can change the team name, team owner, and add or delete team members. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F4milgGFGtUbBebQuVgRr%252Fimage.png%3Falt%3Dmedia%26token%3Dc38ba4f5-13d8-43f1-9d61-40ca349180b4&width=768&dpr=3&quality=100&sign=f8e6177d&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FyQnyionu9jOPR9tifjf5%252Fimage.png%3Falt%3Dmedia%26token%3Dd02abd63-f617-4eea-b8ce-df2e83d76dcb&width=768&dpr=3&quality=100&sign=118ba556&sv=2) circle-exclamation Remember to click on **Update** when you’re done editing [How to add users to a team and sub-team?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-add-users-to-a-team-and-sub-team) [How to remove users from a team or sub-team?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-remove-users-from-a-team-or-sub-team) [PreviousHow to delete a team?chevron-left](https://docs.hivel.ai/set-up/teams/how-to-delete-a-team) [NextHow to create sub-teams?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-create-sub-teams) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Access Management | Hivel The Access Management system provides a more structured, secure, and flexible approach to access. This ensures that the right individuals have appropriate control based on their responsibilities. * * * ### [hashtag](https://docs.hivel.ai/set-up/access-management#access-management-role-hierarchy) **Access Management Role Hierarchy** To establish clear permissions and responsibilities, we have introduced **five distinct roles**: 1. **Admin** _(Full access to the entire platform, responsible for managing permissions and settings)_ 2. **Executive** _(CXOs level i.e. CTO, CEO and Founders)_ 3. **Leader** _(VPs, Director and Department heads)_ 4. **Managers** _(Team Leads, Engineering Managers and Project Managers)_ 5. **User** _(Individual contributors like developers)_ ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fm0pHxOMKZs9j3SrDxemn%252F1st%2520Img.png%3Falt%3Dmedia%26token%3D1a3fa1dd-0f76-4221-baba-62cdcf046486&width=768&dpr=3&quality=100&sign=9735c0cc&sv=2) Each role is assigned specific permissions, ensuring a well-defined access structure and preventing unauthorized modifications. * * * ### [hashtag](https://docs.hivel.ai/set-up/access-management#am-screen-structure-and-functionality) **AM Screen: Structure & Functionality** The **RBAC screen** is divided into three dedicated tabs: #### [hashtag](https://docs.hivel.ai/set-up/access-management#id-1.-role-access-only-admins-can-access) **1\. Role Access (only Admins can access)** This tab provides **Admins** with full control over roles and permissions. Key functionalities include: * **Viewing assigned permissions** for each role. * **Modifying role permissions** as needed. * **Saving changes** for real-time updates. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FFrtxA03AIBSafrt9tlkq%252F2n%2520Img.png%3Falt%3Dmedia%26token%3D9193caa3-a49d-4dca-a944-9c03701b5826&width=768&dpr=3&quality=100&sign=a986b7d4&sv=2) This centralized approach ensures permissions are **accurately assigned** while maintaining security and flexibility. * * * #### [hashtag](https://docs.hivel.ai/set-up/access-management#id-2.-user-management) **2\. User Management** This section allows for efficient user administration by displaying a **list of users** in the system. **Note:** If multiple users are merged in the **Teams** screen, only the **Primary User** will be displayed in this tab. **Key functionalities:** * **Inviting new users:** * If a person is not yet a user, they can be invited via the **"Invite"** button in the last column. * Clicking this button allows Admins to: * **Select the user role** * **Assign them to teams, projects, and workspaces** (if enabled) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FywwBiJfyWqYBmeDrtWjc%252F3rd%2520Img%2520-%2520New.png%3Falt%3Dmedia%26token%3D82a61641-29d1-4280-b42e-07e000c881b2&width=768&dpr=3&quality=100&sign=a9a6a237&sv=2) * **Editing existing users:** * Modify a user’s **role, team, projects, and workspaces** (if enabled). * Users **cannot** modify their own details or the role of anyone **above them** in the hierarchy. * Users **can only edit roles at their level or below**, ensuring secure delegation. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F7mhfSpvHyMUxSuGflWIa%252F4th%2520Img.png%3Falt%3Dmedia%26token%3D174e4154-e69c-4b0f-9751-57d588d0ac44&width=768&dpr=3&quality=100&sign=f88293d2&sv=2) _Adjust roles_ ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FkkTXjTvOPdM8UXIla3Zs%252F5th%2520img%2520%281%29.png%3Falt%3Dmedia%26token%3Dea29ba55-3c9c-4025-9bbf-eefa76b77bac&width=768&dpr=3&quality=100&sign=8f3f95c2&sv=2) _Select teams which can be accessed_ ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FawoMl6A9e1pXQaaCdA6g%252F6th%2520Img%2520-%2520new.png%3Falt%3Dmedia%26token%3D71906631-c53a-41c3-bea8-f16c7a35a6d5&width=768&dpr=3&quality=100&sign=6988e16&sv=2) _Select projects which can be accesed_ * * * #### [hashtag](https://docs.hivel.ai/set-up/access-management#id-3.-pending-access-requests-admin-only) **3\. Pending Access Requests (Admin-Only)** For organizations that require **Admin approval** for new user sign-ups, this tab acts as a **centralized approval hub**. **How it works:** * When a new user requests access, the **Admin receives an email notification**. * All **pending access requests** appear in this section. * The Admin can then **approve or deny** requests, ensuring controlled onboarding. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FqB4103Hm0ekdiVhj8ZNH%252F7th%2520Img.png%3Falt%3Dmedia%26token%3D376a3055-43db-414f-a202-eca5d7759e8d&width=768&dpr=3&quality=100&sign=710eeccd&sv=2) [PreviousHow to remove users from a team or sub-team?chevron-left](https://docs.hivel.ai/set-up/teams/how-to-remove-users-from-a-team-or-sub-team) [NextLabelschevron-right](https://docs.hivel.ai/set-up/labels) Last updated 3 months ago * [Access Management Role Hierarchy](https://docs.hivel.ai/set-up/access-management#access-management-role-hierarchy) * [AM Screen: Structure & Functionality](https://docs.hivel.ai/set-up/access-management#am-screen-structure-and-functionality) sun-brightdesktopmoon sun-brightdesktopmoon --- # Leader's Guide to Engineering Metrics | Hivel [PreviousDeveloper's Guide to Hivelchevron-left](https://docs.hivel.ai/use-cases/developers-guide-to-hivel) [NextFAQschevron-right](https://docs.hivel.ai/faqs) Last updated 6 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Labels | Hivel **Labels** in Hivel allow you to tag users with additional metadata that you can later use to filter across various metrics and reporting screens. They’re highly flexible and customizable, helping you organize users beyond just teams or roles. circle-info Please note: Labels will be set at an org level and be visible to everyone as filters. * * * ### [hashtag](https://docs.hivel.ai/set-up/labels#what-you-can-do-with-labels) What You Can Do with Labels * Add meaningful tags to users (e.g. `Location: APAC`, `Seniority: Senior`, `Department: Frontend`) * Assign multiple labels to one or more users * Group labels into **categories** for better organization * Filter metrics and insights using these labels ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fix5oVVEfTgkKP9bRVKTG%252Fimage.png%3Falt%3Dmedia%26token%3Dbd095860-c442-422b-9b9d-186b27bed4ce&width=768&dpr=3&quality=100&sign=4dc1c114&sv=2) * * * ### [hashtag](https://docs.hivel.ai/set-up/labels#how-to-set-up-labels) 🛠️ How to Set Up Labels 1. **Go to the Labels Screen** * Navigate to **Settings → Labels**. 2. **Create a Category (if needed)** * All labels must belong to a **category**. * Click **"Add Category"** if you don’t already have one. 3. **Add a New Label** * Under an existing category, click **“Add Label”**. * Enter the label name (e.g. `Contractor`, `Europe`, `Level 2`). > **Note:** Labels **must belong to a category** - they cannot exist independently. * ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Flu8PAUk74DYN4oQIDlXs%252Fimage.png%3Falt%3Dmedia%26token%3D972ed58a-4447-4ccd-8142-932f4cb3864a&width=768&dpr=3&quality=100&sign=d75be54c&sv=2) 4. **Edit or Remove Labels and Categories** * Click the ✏️ (pencil) icon to **edit**. * Click the ❌ (cross) icon to **delete**. * **Deleting a label** will remove it from **all users** it's currently assigned to. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FeCVKdTPNZRO0NZuXrMkS%252Fimage.png%3Falt%3Dmedia%26token%3Da95d2564-b866-4cc1-a382-f13e86631212&width=768&dpr=3&quality=100&sign=cd51eb75&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FCS6x98vhoarfBMMCT48O%252Fimage.png%3Falt%3Dmedia%26token%3Dfbe3c3ff-5d5c-4df6-b662-5a0c986bbb71&width=768&dpr=3&quality=100&sign=44593820&sv=2) * * * ### [hashtag](https://docs.hivel.ai/set-up/labels#assign-labels-to-users) 👥 Assign Labels to Users ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F8003OMaH35Dvr5yDvzRW%252FScreenshot%25202025-09-15%2520at%25202.20.00%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Dab1f6228-b489-47fb-8734-824670a33941&width=768&dpr=3&quality=100&sign=eb4cafcc&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fz3DpbZkWOzcCrdLKSShT%252FScreenshot%25202025-09-15%2520at%25202.20.27%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Df9d13dbb-afcd-40ab-aed1-c2bf0d172624&width=768&dpr=3&quality=100&sign=be23014b&sv=2) 1. Go to the **Users** screen. 2. Select one or multiple users. 3. Click the **Labels icon**. 4. Choose the labels to assign and click **Save**. * * * ### [hashtag](https://docs.hivel.ai/set-up/labels#filtering-by-labels) 🔎 Filtering by Labels ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FoUzIchWORu3C4OhBcemA%252FScreen%2520Cast%25202025-09-15%2520at%25201.59.49%2520PM.gif%3Falt%3Dmedia%26token%3Db9c75130-4af9-4cbf-aac6-71799cff7ecd&width=768&dpr=3&quality=100&sign=4722778d&sv=2) Once labels are assigned: * You’ll see **label filters** across Hivel’s metrics and reporting screens. * These filters act as an **extra layer of user segmentation**, making it easier to analyze specific cohorts. * * * ### [hashtag](https://docs.hivel.ai/set-up/labels#example-use-cases) 🧩 Example Use Cases Category Labels Location APAC, EMEA, NA Department Frontend, Backend, QA Seniority Junior, Mid, Senior Employment Full-time, Contractor Onboarding Completed, In Progress [PreviousAccess Managementchevron-left](https://docs.hivel.ai/set-up/access-management) [NextTeam Versioningchevron-right](https://docs.hivel.ai/set-up/team-versioning) Last updated 6 months ago * [What You Can Do with Labels](https://docs.hivel.ai/set-up/labels#what-you-can-do-with-labels) * [🛠️ How to Set Up Labels](https://docs.hivel.ai/set-up/labels#how-to-set-up-labels) * [👥 Assign Labels to Users](https://docs.hivel.ai/set-up/labels#assign-labels-to-users) * [🔎 Filtering by Labels](https://docs.hivel.ai/set-up/labels#filtering-by-labels) * [🧩 Example Use Cases](https://docs.hivel.ai/set-up/labels#example-use-cases) sun-brightdesktopmoon sun-brightdesktopmoon --- # Use Cases | Hivel [Developer's Guide to Hivelchevron-right](https://docs.hivel.ai/use-cases/developers-guide-to-hivel) [Leader's Guide to Engineering Metricschevron-right](https://docs.hivel.ai/use-cases/leaders-guide-to-engineering-metrics) [PreviousRelease Notes - October 2024chevron-left](https://docs.hivel.ai/release-notes/release-notes-october-2024) [NextDeveloper's Guide to Hivelchevron-right](https://docs.hivel.ai/use-cases/developers-guide-to-hivel) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to invite more users to use Hivel? | Hivel If the user does not have a Git account, they can sign up using [app.hivel.ai/signuparrow-up-right](http://app.hivel.ai/signup) ### [hashtag](https://docs.hivel.ai/set-up/users/how-to-invite-more-users-to-use-hivel#if-the-user-has-a-git-account-then-follow-the-below-steps) **If the user has a Git account then follow the below steps -** 1. Go to **Settings.** 2. Select [Access Management](https://docs.hivel.ai/set-up/access-management) 3. Click on User Management. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F70pHuv2tBd2DYCDIRjLQ%252FScreenshot%25202025-02-20%2520at%25205.16.25%2520PM.png%3Falt%3Dmedia%26token%3D0c426088-3ee4-410f-9bd8-3a77491d0fbc&width=768&dpr=3&quality=100&sign=f339efe6&sv=2) 4\. Search for the user in the user list or use the search tab. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FvEUTMTWHVWx3uSJEZam0%252FScreenshot%25202025-02-20%2520at%25206.00.35%2520PM.png%3Falt%3Dmedia%26token%3Dc2881577-7d4b-44ee-9bd1-89a3a65915c2&width=768&dpr=3&quality=100&sign=f429c434&sv=2) 5\. Click on the Invite option for new users. 6\. If the user has no email ID associated with their name, manually enter the email address. 7\. Select the role based on the hierarchy. * **Admin** _(Full access to the entire platform, responsible for managing permissions and settings)_ * **Executive** _(CTO, CEO and Founders)_ * **Leader** _(VPs, Director and Department heads)_ * **Managers** _(Team Leads, Engineering Managers and Project Managers)_ * **User** _(Developers and Engineers)_ ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FwBJERbPHXSE0WFdIUOG4%252FScreenshot%25202025-02-20%2520at%25205.13.57%2520PM.png%3Falt%3Dmedia%26token%3D1fed3a30-15fd-4457-92d3-ec044bd294c4&width=768&dpr=3&quality=100&sign=d4e513d7&sv=2) circle-info **Click on Continue at every step to save the progress.** 1. Assign the user to relevant teams and projects. 2. An email invite will automatically be sent to the user. If you encounter any issues, contact [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#c5b6b0b5b5aab7b185adacb3a0a9eba4ac) for assistance. [PreviousUserschevron-left](https://docs.hivel.ai/set-up/users) [NextHow to add or update an user's email id?chevron-right](https://docs.hivel.ai/set-up/users/how-to-add-or-update-an-users-email-id) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to delete a team? | Hivel You can only delete teams that _you_ have created. To delete a team - 1. Go to **Settings** → **Team** 2. Select a team -> then 3 dots on the right. 3. Click the delete icon. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F9LuZaHokJ5l5r2b01v9T%252Fimage.png%3Falt%3Dmedia%26token%3D3c8a3c2f-637d-437d-8245-ed7093bb369c&width=768&dpr=3&quality=100&sign=f6628c06&sv=2) [PreviousHow to create teams?chevron-left](https://docs.hivel.ai/set-up/teams/how-to-create-teams) [NextHow to modify a team?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-modify-a-team) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to create sub-teams? | Hivel The best way to view data in Hivel is by team. If you have a sub-team structure at your company, Hivel's got you covered too. #### [hashtag](https://docs.hivel.ai/set-up/teams/how-to-create-sub-teams#here-is-how-to-create-sub-teams-in-hivel) Here is how to create sub-teams in Hivel: 1\. Go to **Settings →Teams** 2\. If you don't have any teams created yet, [create a team](https://docs.hivel.ai/set-up/teams/how-to-create-teams) 3\. Select the team within which you want to create a sub-team 4\. Navigate to Subteam menu using the toggle. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fu4pj5fXghPTRKEps0Ro2%252FScreenshot%25202025-11-11%2520at%252012.13.27%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Df962c67d-7a01-4e8b-8c71-6f8ffcf61739&width=768&dpr=3&quality=100&sign=34ad1936&sv=2) 5\. Select 'Create Subteam' and in the dialog box enter team name select a **team owner**, followed by adding other users. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FeJGXyQBTEZ20CJSNNFr2%252Fimage.png%3Falt%3Dmedia%26token%3Df47267d0-aaa0-414d-8ef3-47a440babecf&width=768&dpr=3&quality=100&sign=9f19befe&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F3D1QEKSn5FQtyCRBJIig%252Fimage.png%3Falt%3Dmedia%26token%3Da2d6d211-2a96-473e-b91f-fcf65dea60b5&width=768&dpr=3&quality=100&sign=5913c68&sv=2) 6\. Click **Create Subteam.** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FxqNDLPNOt6vC6UZ6Egk3%252Fimage.png%3Falt%3Dmedia%26token%3D862c5dfa-fc5f-478b-8d2d-395b381e917f&width=768&dpr=3&quality=100&sign=95fc4235&sv=2) 7\. You can view your sub-teams within the main team succesfully. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FA36rOvffU3NZ6UD7t8Up%252Fimage.png%3Falt%3Dmedia%26token%3D2cb55d31-087e-41a0-a675-29552a08e56c&width=768&dpr=3&quality=100&sign=321017bb&sv=2) > If the changes are not reflected immediately, refresh the the screen to reflect the changes. [PreviousHow to modify a team?chevron-left](https://docs.hivel.ai/set-up/teams/how-to-modify-a-team) [NextHow to add users to a team and sub-team?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-add-users-to-a-team-and-sub-team) Last updated 2 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Marco - Code Review Tool | Hivel ### [hashtag](https://docs.hivel.ai/integrations/marco-code-review-tool#getting-started-with-hivel-code-review) Getting Started with Hivel Code Review Welcome to your new AI-powered code review companion. This guide will help you configure your environment and understand how to get the most out of hivel-marco, our intelligent review agent. ### [hashtag](https://docs.hivel.ai/integrations/marco-code-review-tool#configuration-and-setup) ⚙️ Configuration & Setup Control how the AI interacts with your code through the Hivel dashboard. #### [hashtag](https://docs.hivel.ai/integrations/marco-code-review-tool#id-1.-organizational-settings) 1\. Organizational Settings Admins can manage review behavior by navigating to: 👉 [app.hivel.ai/settings/code-reviewarrow-up-right](https://app.hivel.ai/settings/code-review) In this section, you can define: * Specific Instructions: Custom guidelines the AI should follow (e.g., "Ensure all functions have JSDoc"). * Global Filters: Files or directories to include or exclude across all projects. * Default Branches: Set the standard target branches for reviews across your organization. Note: These settings serve as your "baseline" but can be overridden at the individual repository level for maximum flexibility. #### [hashtag](https://docs.hivel.ai/integrations/marco-code-review-tool#id-2.-repository-level-configs) 2\. Repository Level Configs For the highest quality reviews, we recommend indexing your repository when enabling them for the first time. While Marco will still review PRs without this step, indexing allows the AI to understand your entire codebase contextually. * Analyze/Reanalyze: Trigger a manual scan of your repo to update the AI’s mental model of your project. Note: We recommend reanalyzing your repo at the end of each sprint or when a sizable revamp/ feature is added to it. A repository owner can make the final decision of what they consider to be a sizable change. * Override Configs: Any of the org-level configs such as instructions, file filters and branches can also be configured here, at the repo level. Any modifications at the repo stage, override the Org Level configs. ### [hashtag](https://docs.hivel.ai/integrations/marco-code-review-tool#working-in-github) 🚀 Working in GitHub Once enabled, the review process is entirely automated. Look for the hivel-marco bot in your Pull Requests. #### [hashtag](https://docs.hivel.ai/integrations/marco-code-review-tool#automated-triggers) Automated Triggers * New PRs: When a PR is raised against a configured target branch, a review is automatically triggered. * Incremental Updates: If you push new code to an existing open PR, Marco performs an incremental review. It only analyzes the new changes to avoid repeating previous suggestions. #### [hashtag](https://docs.hivel.ai/integrations/marco-code-review-tool#the-review-report) The Review Report Every review includes three core components: Feature Description Security Check First Priority: We scan for Secrets or PII. These are sanitized before reaching the AI to keep your data safe. If detected, remove them before merging! PR Summary A concise overview of what the PR intends to accomplish. File Breakdown A contextual map of changes, categorized by file. Complexity Score An intelligent estimate of the review effort required (see below). **Understanding Complexity Scores** We look beyond "Lines of Code" to calculate how difficult a PR is to digest: Score Description 1.0 – 2.0 Minor tweaks, typos, or simple config updates. 2.1 – 4.0 Straightforward logic changes or small features. 4.1 – 6.0 Standard feature work or moderate refactoring. 6.1 – 8.0 Significant logic changes; requires deep focus. 8.1 – 10.0 High-risk architectural changes or massive diffs. ### [hashtag](https://docs.hivel.ai/integrations/marco-code-review-tool#actionable-suggestions) 🛠️ Actionable Suggestions Marco doesn't just critique; it provides solutions. Suggestions are posted directly on the relevant lines of code within the GitHub UI. * Criticality Levels: Suggestions are tagged as Low, Medium, High, or Critical to help you prioritize fixes. * Explanations: Each suggestion includes why the change is needed and how to implement the fix. * One-Click Fixes: You can accept suggestions directly within GitHub. * Pro Tip: Use the "Batch Suggestions" feature in GitHub’s "Files Changed" tab to review and commit multiple AI suggestions in a single go. Disclaimer: While our AI agent is highly advanced, it may occasionally make mistakes. Always re-test your code after committing AI-suggested changes. [PreviousIntegrationschevron-left](https://docs.hivel.ai/integrations) [NextSCMchevron-right](https://docs.hivel.ai/integrations/scm) Last updated 1 month ago * [Getting Started with Hivel Code Review](https://docs.hivel.ai/integrations/marco-code-review-tool#getting-started-with-hivel-code-review) * [⚙️ Configuration & Setup](https://docs.hivel.ai/integrations/marco-code-review-tool#configuration-and-setup) * [🚀 Working in GitHub](https://docs.hivel.ai/integrations/marco-code-review-tool#working-in-github) * [🛠️ Actionable Suggestions](https://docs.hivel.ai/integrations/marco-code-review-tool#actionable-suggestions) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to remove users from a team or sub-team? | Hivel To **remove users from a team or sub-team** in Hivel, follow these steps: #### [hashtag](https://docs.hivel.ai/set-up/teams/how-to-remove-users-from-a-team-or-sub-team#steps-to-remove-users) Steps to Remove Users: 1. **Navigate to the Teams page**: Go to the Teams page and select the particular team from which you want to remove users. 2. **Select the Users to Remove**: Find and select all the users that you wish to remove from the team. 3. **Click on the "Delete" Icon**: On the right corner of the user selection list, click on the **"Delete"** icon to remove the users from the team. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FoIqwnbxdyNXex2ZTqjJS%252Fimage.png%3Falt%3Dmedia%26token%3D87ffc968-804f-4749-b961-90077b7e94a3&width=768&dpr=3&quality=100&sign=172601ff&sv=2) circle-info **Important**: If you **remove a user from the parent team**, they will also be removed from **all sub-teams** under that parent team. If a user is **only removed from a sub-team**, they will **remain part of the parent team**. This is by design, as a user can be part of the larger parent team even if not part of its sub-teams. circle-info **Another Note**: Removing users from a team does not delete their data. If the user becomes part of another team later, their data will still be available and visible when that new team is selected. To permanently remove an user from the platform, use the [archive functionality](https://docs.hivel.ai/set-up/users/how-to-archive-users) . [PreviousHow to add users to a team and sub-team?chevron-left](https://docs.hivel.ai/set-up/teams/how-to-add-users-to-a-team-and-sub-team) [NextAccess Managementchevron-right](https://docs.hivel.ai/set-up/access-management) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to add users to a team and sub-team? | Hivel To add authors to a team on the Teams page in Hivel, you can follow these methods: #### [hashtag](https://docs.hivel.ai/set-up/teams/how-to-add-users-to-a-team-and-sub-team#id-1.-if-the-team-is-already-created) 1\. **If the Team is Already Created:** * Navigate to the **Teams** page and select the specific team you want to add authors to. * Once inside the team, click on the **"Add Users"** button. * In the search bar, type the name of the users you want to add, and select the applicable users from the list. * The selected users will be added as an author to the team. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FBbFhYsssL8LNHCJN1ESd%252FScreen%2520Cast%25202026-01-30%2520at%25201.03.29%2520PM.gif%3Falt%3Dmedia%26token%3Dbed85b0b-8673-4d35-b374-1b1d2d50fcc5&width=768&dpr=3&quality=100&sign=2b3ffe1b&sv=2) #### [hashtag](https://docs.hivel.ai/set-up/teams/how-to-add-users-to-a-team-and-sub-team#id-2.-if-the-team-is-not-created) 2\. **If the Team is Not Created:** * Select all the users who should be part of the team. * Click on the **"Create Team"** button. * Fill in the required details about the team, such as the team name, description, and any other relevant information. * After filling in the details, save the team. The selected users will be added as authors automatically. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F4hCFqk8ZN6HMMXr1QGeT%252FScreen%2520Cast%25202026-01-30%2520at%25201.06.45%2520PM.gif%3Falt%3Dmedia%26token%3Dc03e59e3-3498-4901-aea6-b471892c49c0&width=768&dpr=3&quality=100&sign=af0dbe83&sv=2) #### [hashtag](https://docs.hivel.ai/set-up/teams/how-to-add-users-to-a-team-and-sub-team#id-3.-to-add-users-to-a-sub-team) 3\. **To add users to a sub-team** * You can navigate directly to the subteam by expanding the parent team. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F92y06K5ucvD2ALikdHL9%252Fimage.png%3Falt%3Dmedia%26token%3D37f083b3-a667-4742-b463-dc36f1db2409&width=768&dpr=3&quality=100&sign=811acdc0&sv=2) * Or you can, navigate to the parent team -> then switch to Subteams section -> Select the subteam. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F2LZimVlxDo1wZZJHx5zu%252Fimage.png%3Falt%3Dmedia%26token%3D9eac139b-02b8-4ece-9b41-ae797602d7a3&width=768&dpr=3&quality=100&sign=382a679&sv=2) * Once inside the subteam, click on "Add Users" and select all the users who should be part of the subteam. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F1JB7KZX0Sa2VKCC2vAyn%252FScreenshot%25202026-01-30%2520at%25201.18.26%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D838cbd19-1a36-4bcc-abce-93963c66b188&width=768&dpr=3&quality=100&sign=bfb9b6d3&sv=2) * After filling in the details, save the team. The selected users will be added as authors automatically. By following these steps, you'll be able to effectively add authors to a team or sub-teams, whether it's already created or not. [PreviousHow to create sub-teams?chevron-left](https://docs.hivel.ai/set-up/teams/how-to-create-sub-teams) [NextHow to remove users from a team or sub-team?chevron-right](https://docs.hivel.ai/set-up/teams/how-to-remove-users-from-a-team-or-sub-team) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # SCM | Hivel [GitHubchevron-right](https://docs.hivel.ai/integrations/scm/github) [Gitlabchevron-right](https://docs.hivel.ai/integrations/scm/gitlab) [BitBucketchevron-right](https://docs.hivel.ai/integrations/scm/bitbucket) [Azurechevron-right](https://docs.hivel.ai/integrations/scm/azure) [PreviousMarco - Code Review Toolchevron-left](https://docs.hivel.ai/integrations/marco-code-review-tool) [NextGitHubchevron-right](https://docs.hivel.ai/integrations/scm/github) sun-brightdesktopmoon sun-brightdesktopmoon --- # Improve Performance | Hivel [How to improve Speed?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed) [How to improve Qualitychevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality) [How to improve planning and throughputchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-planning-and-throughput) [How to track, manage, and reduce technical debt?chevron-right](https://docs.hivel.ai/improve-performance/how-to-track-manage-and-reduce-technical-debt) [What are the impacts of context switching on developer productivity and how to reduce it?chevron-right](https://docs.hivel.ai/improve-performance/what-are-the-impacts-of-context-switching-on-developer-productivity-and-how-to-reduce-it) [How to build a data-driven culture of Engineering?chevron-right](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering) [How to balance speed and quality?chevron-right](https://docs.hivel.ai/improve-performance/how-to-balance-speed-and-quality) [PreviousCoding Metrics Setupchevron-left](https://docs.hivel.ai/integrations/on-prem-setup/coding-metrics-setup) [NextHow to improve Speed?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Best practices for AI usage | Hivel [](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules) ![Cover](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F3E5993RMC8GthzAFymuG%252FScreenshot%25202025-09-11%2520at%25201.41.20%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D8de18778-e9fe-4b8b-b45a-010f964b3f96&width=490&dpr=3&quality=100&sign=c78b9efe&sv=2) _**PR checklist + Prompt Cookbook + Cursor Rules**_ 1 [General AI coding assistant practicesarrow-up-right](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#general-ai-coding-assistant-practices) 2 [GitHub Copilot - usage best practices with examplesarrow-up-right](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#github-copilot-usage-best-practices-with-examples) 3 [Cursor - usage best practices with examplesarrow-up-right](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#cursor-usage-best-practices-with-examples) 4 [Claude Code - best practicesarrow-up-right](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#claude-code-best-practices-for-developers) 5 [Safeguards for Responsible AI Usearrow-up-right](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#safeguards-for-responsible-ai-use) [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#general-ai-coding-assistant-practices) General AI coding assistant practices ------------------------------------------------------------------------------------------------------------------------------------------------------------ ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#start-with-a-clear-intent-then-constrain-the-task) Start with a clear intent, then constrain the task **How to do it** * State goal, constraints, definition of done, and the exact files or interfaces involved. * Prefer short iterative prompts that build on the current diff. **Example** “Add optimistic updates to `IssueList.tsx` using React Query. Keep existing typing. Update `useIssues.ts` to invalidate the `issues` key only on success. Provide a minimal diff and a 3-item test plan.” **Why** Specific context reduces ambiguity and improves suggestion quality. GitHub’s prompt engineering guidance stresses being explicit about functions, files, and context. [GitHub Docsarrow-up-right](https://docs.github.com/en/copilot/concepts/prompt-engineering?utm_source=chatgpt.com) ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#always-review-test-and-secure) Always review, test, and secure **How to do it** * Ask the assistant to write unit tests first for risky changes, then code to make them pass. * Run linters, code scanning, secret scanning, and CI before merge. **Copilot prompt example** “Generate Jest unit tests for `calculateDiscount.ts` that cover 0, boundary, and invalid inputs. Do not stub business rules. Next, propose code changes to make all tests pass.” **Why** GitHub recommends combining Copilot with tests and automated scanning, and shows step-by-step test generation flows. This ties usage to shipped quality instead of raw acceptance. **Security checklist to apply during review** * Validate inputs on the server, never trust user input. * Do not log secrets or tokens. * Guard auth, authorization, and output encoding paths. Reference [OWASP quick checksarrow-up-right](https://owasp.org/www-project-secure-coding-practices-quick-reference-guide/stable-en/02-checklist/05-checklist?utm_source=chatgpt.com) for input validation. ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#make-metrics-reflect-shipped-quality) Make metrics reflect shipped quality **How to do it** * Pair activity metrics with outcomes like merged PRs, test pass trends, rework, and defects. * Read acceptance together with language or area, not in isolation. Your Copilot and Cursor pages encourage acceptance and language breakdowns. Use them with outcome signals to avoid vanity measures. ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#keep-developers-accountable) Keep developers accountable **How to do it** * Require a human LGTM for AI-assisted diffs. * Keep architecture and security decisions in team's hands. * GitHub’s secure use guidance and enterprise docs reinforce human review and policy controls. ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#document-decisions-inside-the-pr) Document decisions inside the PR **How to do it** * Ask the tool to draft the PR description and test plan, then add your rationale, edge cases, and rollout plan. **Example PR note template** “Intent: add optimistic updates for issues. Constraints: preserve cache keys and typing. Tests: 5 unit, 1 E2E. Risk: stale cache on error. Rollback: feature flag `optimisticIssues`.” Copilot’s cheat sheet includes commands for explaining code and creating tests that help populate this PR template. [GitHub Chat Cheat Sheetarrow-up-right](https://docs.github.com/en/copilot/reference/cheat-sheet) ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#protect-data-and-ip) Protect data and IP **How to do it** * Do not paste secrets or proprietary payloads unless your enterprise configuration explicitly allows it. * Use approved enterprise settings for logging and data boundaries. ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#build-a-learning-loop) Build a learning loop **How to do it** * When output is off, reply with why and ask for a corrected version that follows your examples. * Maintain a small internal “prompt cookbook” of patterns that work for your stack. GitHub’s official tips emphasize setting context, making asks specific, and iterating. [The GitHub Blogarrow-up-right](https://github.blog/developer-skills/github/how-to-write-better-prompts-for-github-copilot/?utm_source=chatgpt.com) - a fun and useful read with more examples and tips. * * * [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#github-copilot-usage-best-practices-with-examples) GitHub Copilot - usage best practices with examples -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#pick-the-right-copilot-surface) Pick the right Copilot surface **When to use inline** * Completing a function, adding parameters, small refactors. **When to use Copilot Chat** * Explaining unfamiliar code, writing tests, multi-file changes, or generating a migration plan. The docs show test generation and E2E examples directly from Chat. **Chat prompts you can copy** * “Explain how `useRetryingFetch` works and list failure modes.” * “Generate table-driven Jest tests for `parseDateRange` including invalid ranges.” * “Propose a minimal diff to replace legacy crypto with `subtle.crypto` and update tests.” ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#review-acceptance-with-intent) Review acceptance with intent **Practice** * Review the first two or three alternative suggestions. Accept the smallest correct diff. Reject verbose or speculative code. **Inline example** * “Show two simpler alternatives with fewer allocations and explain tradeoffs.” Why: GitHub encourages scanning alternatives and giving acceptance feedback to shape future suggestions. ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#test-first-for-risky-changes) Test first for risky changes **Scenario** You are adding rate limiting to an API. **Chat sequence** * “Write Jest tests for `rateLimiter.ts` that cover normal, burst, and blocked user scenarios.” * “Generate implementation changes that pass the tests. Keep public API unchanged.” * “Add an E2E Playwright test for the 429 response path.” ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#use-copilot-in-code-review-without-skipping-human-judgment) Use Copilot in code review without skipping human judgment * Ask: “Summarize this diff. Flag potential N+1 queries and missing input validation.” * Keep your checklist items for secrets, validation, and authorization. GitHub’s secure practice pages advocate combining Copilot with automated scanning and human review. ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#keep-copilot-scoped) Keep Copilot scoped * Provide only the files needed and the exact function signatures. * Never include secrets. Use masked env values in examples. ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#interpret-copilot-metrics-with-care) Interpret Copilot metrics with care * Track suggestions accepted by language and area of code, then correlate with merged PRs, test pass rate, rework, and defects. * If acceptance is high but rework rises, slow down and tighten review. This mirrors your “expanded metrics” emphasis on segmentation and context. * * * [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#cursor-usage-best-practices-with-examples) Cursor - usage best practices with examples ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#seed-cursor-with-rules) Seed Cursor with rules * [Cursor Rulesarrow-up-right](https://docs.cursor.com/en/context/rules) * Keep it focused and composable, under 500 lines. * Include language patterns, error handling rules, test frameworks, and things to avoid. Cursor’s docs spell out how to write effective rules. * Keep in mind, you can go ahead with setting up `.cursorrules`, but it will be deprecated soon. ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#work-in-small-reviewable-steps) Work in small, reviewable steps **Scenario** You need to add a debounce to a search box. **Composer prompt** “Update `SearchBox.tsx` to debounce input by 300 ms using `useCallback` and `setTimeout`. Show a minimal diff. Add a test for rapid keystrokes.” **Follow-up** “Explain the diff and provide one simpler alternative.” Why: Cursor guidance and community tips encourage iterative edits and minimal diffs. ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#make-cursor-refactor-your-own-diffs) Make Cursor refactor your own diffs **Scenario** You wrote a pagination helper. **Chat prompt** “Review `paginate.ts`. Reduce allocations and avoid off-by-one errors. Propose a smaller version with identical behavior and add tests for edge pages.” ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#use-context-intentionally) Use context intentionally **Practice** * Reference only files that are required for the change. * For multi-module edits, ask Cursor to first list affected files and functions before it edits. This reduces irrelevant changes. ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#interpret-cursor-metrics-with-care) Interpret Cursor metrics with care **Practice** * Read AI vs manual lines and acceptance rates next to merged PRs and rework. * Sample AI-assisted PRs weekly for maintainability and security. Your Cursor docs mention capture limits, so qualitative review stays important. ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#close-the-loop-in-the-pr) Close the loop in the PR **Prompt** “Draft a PR description summarizing intent, constraints, test plan, and risk. Keep it under 120 words.” Then you add links to tickets and any rollout notes. * * * [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#claude-code-best-practices-for-developers) Claude Code Best Practices for Developers -------------------------------------------------------------------------------------------------------------------------------------------------------------------- (Focused on improving output quality) Claude Code can produce highly reliable, idiomatic code when given the right structure, context, and feedback. This guide focuses on how developers can systematically improve Claude’s outputs and make them more consistent, testable, and production-ready.​ ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-1-set-strong-context) Set strong context Claude works best when it understands your project, conventions, and constraints clearly.​ * Maintain a CLAUDE.md (or similar) at the repo root that includes: * Project overview, architecture sketch, and main data models. * Coding standards (style guides, naming, error handling, logging). * How to run tests, linters, formatters, and local environment.​ * Always reference concrete files and paths: * Paste or attach the specific files Claude should consider (e.g., `src/api/user.ts`, `tests/user.test.ts`). * Tell Claude explicitly which files it is allowed to edit and which are read-only.​ * Provide realistic examples: * Show a “good” existing function or module and say: “Match this style and patterns.” * Include an example request/response or input/output for APIs and CLIs.​ ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-2-write-precise-structured-prompts) Write precise, structured prompts The single biggest lever on output quality is the prompt structure.​ * Use a consistent prompt template, for example: * Context: What the project/module does and any relevant standards. * Goal: One clear task, e.g., “Implement X”, “Refactor Y”, “Add logging.” * Constraints: Performance, security, libraries, patterns to use/avoid. * Tests: Existing tests, desired new tests, or explicit acceptance criteria. * Output format: “Return only updated code for file A and B” or “Reply with a unified diff.”​ * Avoid fuzzy asks: * Replace “Improve this code” with “Refactor to reduce duplication, keep behavior identical, and ensure all tests in `tests/user.test.ts` still pass.” * Avoid mixing multiple unrelated tasks in a single prompt; split them.​ * Make hidden expectations explicit: * Mention error handling strategy, logging format, null-handling, and type-checking rules. * Clarify which external APIs or internal services are authoritative.​ ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-3-use-tests-and-examples-as-the-truth) Use tests and examples as the “truth” Claude becomes much more reliable when tests and examples define correctness.​ * Lead with tests whenever possible: * Provide failing test cases first and ask Claude to “make these tests pass without breaking existing tests.” * If no tests exist, ask Claude to generate tests before or alongside the implementation.​ * Give table-driven or example-based specs: * For business rules, supply a table or list of input → expected output scenarios. * Ask Claude to restate these in its own words before coding to surface misunderstandings.​ * Keep tests close to the code: * Always show the relevant test file next to the implementation file in your prompt. * After code generation, ask Claude to adjust tests if behavior intentionally changes, and to explain the change.​ ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-4-iterate-in-small-focused-steps) Iterate in small, focused steps Short, focused loops produce more accurate and maintainable code than one-shot “big bang” prompts.​ * Limit scope per iteration: * Aim for a single function, class, or endpoint change per prompt. * For large refactors, ask for a step-by-step plan first, then implement step 1, then step 2, etc.​ * Use a “plan → code → review” pattern: * Ask: “Propose a detailed plan to implement X in this codebase without writing code yet.” * Once the plan looks right, ask Claude to implement only the next step.​ * Always follow up with critique: * After generation, respond with specific feedback: “You missed case A; the logger format is wrong; and this must not block the main thread.” * Ask Claude to revise just those points, not to rewrite everything.​ ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-5-enforce-your-standards-in-the-prompt) Enforce your standards in the prompt Claude will usually conform to whatever rules you clearly and consistently enforce.​ * Embed standards in every relevant prompt: * Language version, style guide (e.g., PEP 8, Airbnb), type system usage, and project-specific idioms. * Error handling policies (e.g., domain-specific error classes, never return raw exceptions). * Require lint- and type-clean output: * Say: “Write code that passes `npm run lint` and `npm run test` with zero warnings.” * If your toolchain is known, mention it explicitly (e.g., ESLint, mypy, pylint, detekt).​ * Standardize logging, metrics, and tracing: * Provide an example of a well-instrumented function and ask Claude to follow that pattern. * Explicitly forbid printing directly to stdout/stderr if your logging infra expects structured logs.​ ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-6-make-claude-explain-and-self-check) Make Claude explain and self-check Getting Claude to reason about its own output catches many issues early.​ * Ask for reasoning after the code: * “After writing the code, briefly explain how it works and why it satisfies the requirements.” * “List potential edge cases this implementation might still miss.”​ * Use an explicit self-review step: * “Now review your code against the acceptance criteria and tests and describe any mismatches. Fix them if found.” * “Compare your changes against the project’s error-handling rules in CLAUDE.md and adjust.”​ * Encourage alternative designs: * “Propose one alternative implementation with different trade-offs (performance vs. readability), but mark clearly which one you recommend.”​ ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-7-control-file-edits-and-diffs) Control file edits and diffs Tightly controlling how Claude edits files reduces merge pain and accidental regressions.​ * Be explicit about allowed changes: * “Only modify the `createOrder` function in `order_service.py`. Do not change any other functions.” * “Add new code at the bottom of the file under the ‘// Feature flags’ section only.” * Prefer diff-style outputs for larger changes: * Ask for unified diffs (`diff -u`) so you can review and apply changes safely. * Instruct: “Do not regenerate the whole file; produce minimal edits needed.”​ * Avoid hidden behavior changes: * Tell Claude to keep public signatures and observable behavior unchanged unless explicitly told otherwise. * If behavior must change, ask for a short changelog bullet list.​ ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-8-use-claude-for-refactoring-and-understanding) Use Claude for refactoring and understanding Claude is strong at explaining and reshaping existing code when guided properly.​ * Clarify your refactoring goals: * “Reduce duplication between A and B by extracting a shared helper.” * “Improve readability and add comments, but do not change runtime behavior.”​ * Ask for high-level summaries: * “Summarize what this module does, its key responsibilities, and any code smells you see.” * Use the summary to confirm shared understanding before deeper changes.​ * Have Claude propose better structures: * “Suggest a more modular design for this code, then implement only the new interfaces and stubs first.” * “Identify functions that should be moved to a different module and explain why.”​ ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-9-guide-performance-security-and-edge-cases) Guide performance, security, and edge cases You can push Claude to consider non-happy-path concerns explicitly.​ * Performance: * Clearly state constraints (“Input can be up to 1M items”, “This runs in a hot path”). * Ask for complexity analysis and possible bottlenecks after code is generated.​ * Security: * Call out relevant risks: injection, XSS, CSRF, authentication, authorization, secrets handling. * Ask: “Review your code for security issues in this context and fix any problems you see.”​ * Robustness: * Request explicit handling of nulls, timeouts, retries, and external failure modes. * Provide a list of edge cases and ask Claude to point to where each is handled.​ ### [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-10-example-prompt-template) Example prompt template You can adapt this template as a standard for your team.​ * Context * “You are helping with a codebase described in CLAUDE.md below. This project is a \[brief description\]. We use \[language, framework, style guide\].” * Files * “Here is the current content of `path/to/file` and relevant tests: \[paste code\].” * Goal * “Task: \[single, clear task\]. Maintain existing behavior unless explicitly told otherwise.” * Constraints * “Constraints: * Follow \[style guide/tools\]. * Code must pass \[tests/commands\]. * Do not modify \[list of files/functions\].” * Tests/spec * “Here are the test cases / acceptance criteria / examples that must hold: \[paste or describe\].” * Output format * “Output: Provide only the updated code for \[file(s)\], as a unified diff. Then explain in 3–5 sentences how it satisfies the requirements and which edge cases it handles.” Using a structure like this consistently can dramatically improve Claude’s code quality, reduce rework, and make outputs more predictable. * * * [hashtag](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#safeguards-for-responsible-ai-use) Safeguards for Responsible AI Use ---------------------------------------------------------------------------------------------------------------------------------------------------- * **Require tests for AI-assisted changes above a size threshold** Example GitHub Action: block merge if diff touches more than N lines across M files and the PR has zero new or updated tests. Copilot docs recommend automated checks and testing around AI output. * **Block merges on security failures** Example: run secret scan, SAST rules, and dependency checks on every PR. Reject if any high severity issue appears. Use OWASP input validation reminders in review. [owasp.orgarrow-up-right](https://owasp.org/www-project-secure-coding-practices-quick-reference-guide/stable-en/02-checklist/05-checklist?utm_source=chatgpt.com) * **Count only code that lands and passes CI when discussing “AI impact”** Tie assistant usage to merged PRs and green pipelines rather than raw suggestion counts. This aligns with your metrics pages that caution against surface-only numbers. * **Weekly sampling of AI-assisted PRs** Have tech leads sample two AI-assisted PRs per team each week for security, clarity, and maintainability. Record findings and feed them back into rules or the prompt cookbook. Cursor rules are designed to evolve with feedback. [PreviousHow to Encourage Jira Hygiene Without Creating Frictionchevron-left](https://docs.hivel.ai/best-practices/jira-best-practices/how-to-encourage-jira-hygiene-without-creating-friction) [NextAI usage - PR checklist + Prompt Cookbook + Cursor Ruleschevron-right](https://docs.hivel.ai/best-practices/ai-usage-pr-checklist-+-prompt-cookbook-+-cursor-rules) Last updated 3 months ago * [General AI coding assistant practices](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#general-ai-coding-assistant-practices) * [Start with a clear intent, then constrain the task](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#start-with-a-clear-intent-then-constrain-the-task) * [Always review, test, and secure](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#always-review-test-and-secure) * [Make metrics reflect shipped quality](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#make-metrics-reflect-shipped-quality) * [Keep developers accountable](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#keep-developers-accountable) * [Document decisions inside the PR](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#document-decisions-inside-the-pr) * [Protect data and IP](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#protect-data-and-ip) * [Build a learning loop](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#build-a-learning-loop) * [GitHub Copilot - usage best practices with examples](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#github-copilot-usage-best-practices-with-examples) * [Pick the right Copilot surface](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#pick-the-right-copilot-surface) * [Review acceptance with intent](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#review-acceptance-with-intent) * [Test first for risky changes](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#test-first-for-risky-changes) * [Use Copilot in code review without skipping human judgment](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#use-copilot-in-code-review-without-skipping-human-judgment) * [Keep Copilot scoped](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#keep-copilot-scoped) * [Interpret Copilot metrics with care](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#interpret-copilot-metrics-with-care) * [Cursor - usage best practices with examples](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#cursor-usage-best-practices-with-examples) * [Seed Cursor with rules](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#seed-cursor-with-rules) * [Work in small, reviewable steps](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#work-in-small-reviewable-steps) * [Make Cursor refactor your own diffs](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#make-cursor-refactor-your-own-diffs) * [Use context intentionally](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#use-context-intentionally) * [Interpret Cursor metrics with care](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#interpret-cursor-metrics-with-care) * [Close the loop in the PR](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#close-the-loop-in-the-pr) * [Claude Code Best Practices for Developers](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#claude-code-best-practices-for-developers) * [Set strong context](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-1-set-strong-context) * [Write precise, structured prompts](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-2-write-precise-structured-prompts) * [Use tests and examples as the “truth”](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-3-use-tests-and-examples-as-the-truth) * [Iterate in small, focused steps](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-4-iterate-in-small-focused-steps) * [Enforce your standards in the prompt](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-5-enforce-your-standards-in-the-prompt) * [Make Claude explain and self-check](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-6-make-claude-explain-and-self-check) * [Control file edits and diffs](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-7-control-file-edits-and-diffs) * [Use Claude for refactoring and understanding](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-8-use-claude-for-refactoring-and-understanding) * [Guide performance, security, and edge cases](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-9-guide-performance-security-and-edge-cases) * [Example prompt template](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#id-10-example-prompt-template) * [Safeguards for Responsible AI Use](https://docs.hivel.ai/best-practices/best-practices-for-ai-usage#safeguards-for-responsible-ai-use) sun-brightdesktopmoon sun-brightdesktopmoon --- # Developer's Guide to Hivel | Hivel Get started with Hivel by using this guide to know exactly what metrics to check—and when to check them. Organized around key events and check-in times, this resource will guide you in monitoring the metrics that matter most, from daily cycle time reviews to quarterly performance benchmarks, making it easy to stay on track and continuously improve. 📅 Key Events 🕒 Key Times Key Event What to Check What to do **Missed Deadlines** 1\. PR Bottlenecks Use the [Pull Request Screenarrow-up-right](https://hivel.gitbook.io/knowlegebase/using-hivel/pull-request) to check for PRs awaiting your review or merge, or PRs with 5+ days cycle time. Prioritize reviews or break down large PRs into smaller ones. You can also escalate by adding more reviewers to the process. 2\. Cycle Time Check the Process Screen to analyze whether long coding or review phases are contributing to missed deadlines. 3\. Rework & Maintenance On the Coding Screen, see how much of your effort went towards code churn. 4\. Unplanned Completed Work On the Delivery Accuracy screen, see how much unplanned ad-hoc work was completed in the last sprint, and how that affected your planned roadmap items. **New Feature Deployment** 1\. Deployment Frequency Check Cockpit to ensure you’re deploying frequently (daily or weekly). 2\. Change Failure Rate Track failures in the Process Screen to see how often deployments require rollbacks or fixes. If failure rates are high or deployments are few, work on improving testing and CI/CD processes. **Critical Production Issue** 1\. Change Failure Rate On the PR screen, see how many PRs were hotfix related, and see the trends on Cockpit. 2\. MTTR (Mean Time to Restore) Use the PR Screen to check how quickly production issues are resolved. Work on improving your response time during production issues and ensure that reviews, even under pressure, are thorough to prevent future failures. 3\. Flashy Reviews Review the PR Screen for any rushed, surface-level reviews. **Key Event** **What to Check** **What to do** **Daily Check-In** 1\. Open PRs See which PRs are open for you to review and to merge on the [Pull Request screenarrow-up-right](https://chatgpt.com/using-hivel/pull-request) . **Weekly Check-In** 1\. [Cycle Timearrow-up-right](https://chatgpt.com/metrics-and-definitions/speed/cycle-time) Check the [Process Screenarrow-up-right](https://chatgpt.com/using-hivel/process) to analyze whether long coding or review phases are contributing to missed deadlines. 2\. Coding Focus Time On the [Activity Screenarrow-up-right](https://chatgpt.com/using-hivel/activity) , ensure your coding focus time is maximized. 3\. [Deployment Frequencyarrow-up-right](https://chatgpt.com/metrics-and-definitions/speed/deployment-frequency) Check [Cockpitarrow-up-right](https://chatgpt.com/c/broken-reference) to ensure you’re deploying frequently (daily or weekly).If your cycle time is increasing or your deployment frequency is low, work on breaking tasks into smaller pieces and improving team collaboration. **Biweekly Review** 1\. [Change Failure Ratearrow-up-right](https://chatgpt.com/metrics-and-definitions/quality/change-failure-rate) Track failures in the [PR Screenarrow-up-right](https://chatgpt.com/using-hivel/pull-request) to see how often deployments require rollbacks or fixes.If failure rates are high or deployments are few, work on improving testing and CI/CD processes. 2\. [PR Review Timearrow-up-right](https://chatgpt.com/metrics-and-definitions/speed/review-time) On the [Pull Request Screenarrow-up-right](https://chatgpt.com/using-hivel/pull-request) , track how long your PRs are sitting in the review stage.Improve testing and ensure clear communication during the review process if failure rates or review times are high. **Monthly Review** 1\. Code Churn Check the [Coding Screenarrow-up-right](https://chatgpt.com/using-hivel/coding) to see how much time you're spending on [new workarrow-up-right](https://chatgpt.com/metrics-and-definitions/throughput/new-work) versus [reworkarrow-up-right](https://chatgpt.com/metrics-and-definitions/quality/rework) and [maintenancearrow-up-right](https://chatgpt.com/metrics-and-definitions/quality/maintenance) .Aim to write well-tested code that minimizes rework, and advocate for regular refactoring if maintenance is high. 2\. [Meetingsarrow-up-right](https://chatgpt.com/using-hivel/cockpit-pro/meetings-breakdown) On [Custom Dashboardsarrow-up-right](https://chatgpt.com/c/broken-reference) , see how long you spent in meetings vs. doing deep work. 3\. [Throughputarrow-up-right](https://chatgpt.com/metrics-and-definitions/throughput) On the [Cockpitarrow-up-right](https://chatgpt.com/c/broken-reference) , analyze your trends for Commits, PRs Opened, and PRs merged. 4\. Overall Activity On [Dev360arrow-up-right](https://chatgpt.com/using-hivel/dev360) , see what type of work you spent the most time on, and whether you had consistent activity trends. **Quarterly Review** 1\. Team Performance Alignment Use the [Dev360arrow-up-right](https://chatgpt.com/using-hivel/dev360) and [Cockpitarrow-up-right](https://chatgpt.com/c/broken-reference) to compare your performance metrics ([cycle timearrow-up-right](https://chatgpt.com/metrics-and-definitions/speed/cycle-time) , [review timearrow-up-right](https://chatgpt.com/metrics-and-definitions/speed/review-time) , [rework %arrow-up-right](https://chatgpt.com/metrics-and-definitions/quality/rework) ) to team averages.Propose improvements and celebrate progress as necessary. 2\. Long-term trends Review your personal trends across multiple sprints using the [Custom Dashboardsarrow-up-right](https://chatgpt.com/c/broken-reference) and [Goals Screenarrow-up-right](https://chatgpt.com/goals) . [PreviousUse Caseschevron-left](https://docs.hivel.ai/use-cases) [NextLeader's Guide to Engineering Metricschevron-right](https://docs.hivel.ai/use-cases/leaders-guide-to-engineering-metrics) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # What are the impacts of context switching on developer productivity and how to reduce it? | Hivel ### [hashtag](https://docs.hivel.ai/improve-performance/what-are-the-impacts-of-context-switching-on-developer-productivity-and-how-to-reduce-it#impact-of-context-switching-on-developer-productivity) Impact of Context Switching on Developer Productivity **Context switching** refers to the process of a developer shifting focus between different tasks, projects, or environments. While it may seem efficient to multitask, context switching can have significant negative impacts on developer productivity due to the mental overhead involved in transitioning between different tasks. Here are the key impacts of context switching on developer productivity: 1. **Reduced focus and mental clarity** * Switching between tasks requires cognitive effort to "reload" the context of each task. This mental reloading wastes valuable time and energy, reducing overall focus on the current task. * **Impact**: Developers may lose track of key details, leading to more mistakes, slower progress, and reduced quality of work. 2. **Increased time to regain flow** * For complex tasks, developers need to enter a state of deep focus (also known as "flow"). Frequent context switches disrupt this flow, and it can take anywhere from 10 to 30 minutes to fully regain it after being interrupted. * **Impact**: Development tasks, particularly complex ones like debugging or architectural changes, take significantly longer due to the constant need to reset mental focus. 3. **Higher error rates** * Multitasking often leads to incomplete or hurried work, as attention is divided. This can result in more bugs, code quality issues, or even misinterpretation of requirements. * **Impact**: Increased defect rates or rework time, which in turn affects overall project timelines and quality. 4. **Lower overall productivity** * Studies have shown that constant task-switching leads to reduced output because time is lost during the transitions between tasks. * **Impact**: Developers may spend more time transitioning between tasks than actually completing them, leading to a significant drop in their productive time. 5. **Increased cognitive fatigue** * Constantly juggling different tasks leads to mental fatigue, which impacts both the quality of work and overall job satisfaction. * **Impact**: Over time, developers can experience burnout or frustration, further reducing productivity and motivation. 6. **Decreased creativity and problem-solving ability** * Creative problem-solving requires uninterrupted focus. Frequent context switching hinders the ability to come up with innovative solutions, especially for challenging tasks. * **Impact**: The team’s ability to produce high-quality solutions is reduced, as developers spend more time managing interruptions rather than engaging in deep problem-solving. ### [hashtag](https://docs.hivel.ai/improve-performance/what-are-the-impacts-of-context-switching-on-developer-productivity-and-how-to-reduce-it#how-to-reduce-context-switching) How to Reduce Context Switching Once you’ve tracked and identified the impact of context switching, the following strategies can help minimize its negative effects: 1. **Enforce work-in-progress (WIP) limits** * Encourage developers to work on fewer tasks simultaneously by setting clear WIP limits in project management tools. This ensures they focus on completing one task before moving to the next. 2. **Batch meetings and interruptions** * Schedule meetings and other team interactions in blocks to minimize the number of interruptions throughout the day, giving developers longer stretches of uninterrupted time to focus. 3. **Introduce "focus time" policies** * Set "focus hours" where no meetings or non-critical interruptions are allowed, ensuring developers have dedicated time to work on their tasks without distractions. 4. **Improve task prioritization** * Ensure that work is clearly prioritized to avoid developers jumping between tasks unnecessarily. Align teams on what tasks should take precedence to avoid unnecessary shifting between priorities. 5. **Automate and streamline handovers** * Improve documentation and use tools like project management boards to ensure smooth handoffs, reducing the amount of time developers need to spend re-acquiring context when switching tasks. By tracking and reducing context switching, developers can regain focus, maintain flow, and boost productivity, while also reducing cognitive fatigue and improving overall job satisfaction. [PreviousHow to track, manage, and reduce technical debt?chevron-left](https://docs.hivel.ai/improve-performance/how-to-track-manage-and-reduce-technical-debt) [NextHow to build a data-driven culture of Engineering?chevron-right](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering) Last updated 1 year ago * [Impact of Context Switching on Developer Productivity](https://docs.hivel.ai/improve-performance/what-are-the-impacts-of-context-switching-on-developer-productivity-and-how-to-reduce-it#impact-of-context-switching-on-developer-productivity) * [How to Reduce Context Switching](https://docs.hivel.ai/improve-performance/what-are-the-impacts-of-context-switching-on-developer-productivity-and-how-to-reduce-it#how-to-reduce-context-switching) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to balance speed and quality? | Hivel To balance speed and quality, considering focusing on specific metrics - cycle time, deployment frequency (speed metrics), and change failure rate, mean time to repair (MTTR), PRs reviewed, and flashy reviews (quality metrics). #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-balance-speed-and-quality#id-1.-optimize-cycle-time-without-sacrificing-code-review) 1\. **Optimize cycle time without sacrificing code review** * Focus on reducing idle time in the development cycle, such as waiting for deployments or code reviews, without skipping these essential steps. Implementing a pull request queue and setting expected times for reviews can help. * **Example**: Automate basic code quality checks with linters and commit hooks to ensure that only code that meets certain standards reaches review, thus speeding up the cycle time without compromising quality. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-balance-speed-and-quality#id-2.-increase-deployment-frequency-with-feature-toggling) 2\. **Increase deployment frequency with feature toggling** * Use feature flags to manage deployments more flexibly. This allows more frequent updates to your application with less risk, as features can be enabled or disabled without redeploying. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-balance-speed-and-quality#id-3.-manage-change-failure-rate-with-canary-releases) 3\. **Manage change failure rate with canary releases** * Use canary releases and blue-green deployments to minimize the impact of changes. By gradually increasing the user base seeing the new version, you can detect failures early and reduce their impact. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-balance-speed-and-quality#id-4.-reduce-mttr-through-post-incident-analysis-and-automated-rollbacks) 4\. Reduce MTTR through post-incident analysis and automated rollbacks * Conduct thorough reviews after resolving any incident to identify the root cause and to document lessons learned. Having a playbook allows team members to react swiftly and effectively, reducing the time spent figuring out how to address common problems. * Automated rollbacks can immediately mitigate the impact of a faulty deployment, drastically reducing downtime and the associated repair time. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-balance-speed-and-quality#id-5.-ensure-thorough-pr-reviews-with-automated-and-manual-checks) 5\. **Ensure thorough PR reviews with automated and manual checks** * Combine automated testing and manual peer reviews to ensure high code quality. Encourage detailed, constructive feedback during reviews and maintain a culture where quality is everyone's responsibility. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-balance-speed-and-quality#id-6.-address-flashy-reviews-with-mandatory-review-standards) 6\. **Address flashy reviews with mandatory review standards** * Set minimum review time standards or checklists for PRs, especially large ones, to ensure no changes are approved without adequate scrutiny, thus reducing flashy reviews. By integrating these practices, teams can effectively manage the delicate balance between moving fast and maintaining the high quality necessary for long-term success. Each practice not only addresses specific metrics but also fosters a culture where quality and speed are equally valued and managed. [PreviousHow to build a data-driven culture of Engineering?chevron-left](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering) [NextRelease Noteschevron-right](https://docs.hivel.ai/release-notes) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Why does the filters change when I move to dashboards but in other screen it remains same? | Hivel The **date and teams filters** remain persistent across all screens except the **Dashboards** screen. * If you have a **saved filter** in Dashboards, it will automatically apply when you navigate to Dashboards, and this filter will remain active when you move back to other screens. * If there’s **no saved filter** in Dashboards, the filters from your previous screen will carry over and apply. This ensures a seamless filtering experience across Hivel! [PreviousWhy am I not able to select more than 6 months at a time?chevron-left](https://docs.hivel.ai/faqs/system-behavior-and-limitations-faqs/why-am-i-not-able-to-select-more-than-6-months-at-a-time) [NextReporting & Goal Tracking FAQschevron-right](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # System Behavior & Limitations FAQs | Hivel [Why am I not able to select more than 6 months at a time?chevron-right](https://docs.hivel.ai/faqs/system-behavior-and-limitations-faqs/why-am-i-not-able-to-select-more-than-6-months-at-a-time) [Why does the filters change when I move to dashboards but in other screen it remains same?chevron-right](https://docs.hivel.ai/faqs/system-behavior-and-limitations-faqs/why-does-the-filters-change-when-i-move-to-dashboards-but-in-other-screen-it-remains-same) [PreviousHow can I add a template in dashboards for my org to follow?chevron-left](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/how-can-i-add-a-template-in-dashboards-for-my-org-to-follow) [NextWhy am I not able to select more than 6 months at a time?chevron-right](https://docs.hivel.ai/faqs/system-behavior-and-limitations-faqs/why-am-i-not-able-to-select-more-than-6-months-at-a-time) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to improve planning and throughput | Hivel [Leveraging data for more effective sprint planningchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-planning-and-throughput/leveraging-data-for-more-effective-sprint-planning) [What metrics can I use to prevent developer burnout?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-planning-and-throughput/what-metrics-can-i-use-to-prevent-developer-burnout) [PreviousBuilding a feedback loop for continuous code improvementchevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-quality/building-a-feedback-loop-for-continuous-code-improvement) [NextLeveraging data for more effective sprint planningchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-planning-and-throughput/leveraging-data-for-more-effective-sprint-planning) sun-brightdesktopmoon sun-brightdesktopmoon --- # Azure AD SSO | Hivel > This documentation applies **only to Hivel Cloud customers**. If you are looking for an **on-premise solution**, please contact us at [\[email protected\]arrow-up-right](mainto:support@hivel.ai) > . This setup allows you to enable Single Sign-On (SSO) for Hivel users through Microsoft Entra ID (formerly Azure AD). ### [hashtag](https://docs.hivel.ai/integrations/azure-ad-sso#configuration-steps) Configuration Steps When creating the SAML application in Microsoft Entra: **Mandatory fields to configure on your side:** * App Name: Hivel * Identifier (Entity ID): [https://app.hivel.ai/arrow-up-right](https://app.hivel.ai/) * Reply URL (Assertion Consumer Service URL): [https://app.hivel.ai/hivelapi/auth/azure-ad/callbackarrow-up-right](https://app.hivel.ai/hivelapi/auth/azure-ad/callback) Other fields are optional and can be skipped. **Once configured, please share the following with the Hivel team:** 1. Login URL: * Login URL Example : [https://login.microsoftonline.com/55d96f5e-2b75-4762-ae08-11de584d8e83/saml2arrow-up-right](https://login.microsoftonline.com/55d96f5e-2b75-4762-ae08-11de584d8e83/saml2) 2. Microsoft Entra Identifier (issuer): * Microsoft Entra Identifier (issuer) Example: [https://sts.windows.net/55d96f5e-2b75-4762-ae08-11de584d8e83/arrow-up-right](https://sts.windows.net/55d96f5e-2b75-4762-ae08-11de584d8e83/) 3. Logout URL: * Logout URL Example: [https://login.microsoftonline.com/55d96f5e-2b75-4762-ae08-11de584d8e83/saml2arrow-up-right](https://login.microsoftonline.com/55d96f5e-2b75-4762-ae08-11de584d8e83/saml2) 4. Share the **Microsoft Tenant ID** with the Hivel team. > Once the app is created and all of the above are configured, share the **Microsoft Tenant ID** with the Hivel team. [PreviousOkta SSOchevron-left](https://docs.hivel.ai/integrations/okta-sso) [NextSlack Integration with Hivelchevron-right](https://docs.hivel.ai/integrations/slack-integration-with-hivel) Last updated 26 days ago sun-brightdesktopmoon sun-brightdesktopmoon --- # FAQs | Hivel [Team & User Management FAQschevron-right](https://docs.hivel.ai/faqs/team-and-user-management-faqs) [PR, Issues & Workflow FAQschevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs) [System Behavior & Limitations FAQschevron-right](https://docs.hivel.ai/faqs/system-behavior-and-limitations-faqs) [Reporting & Goal Tracking FAQschevron-right](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs) [Metrics & Data FAQschevron-right](https://docs.hivel.ai/faqs/metrics-and-data-faqs) [Marco - Code Review Agentchevron-right](https://docs.hivel.ai/faqs/marco-code-review-agent) [PreviousLeader's Guide to Engineering Metricschevron-left](https://docs.hivel.ai/use-cases/leaders-guide-to-engineering-metrics) [NextTeam & User Management FAQschevron-right](https://docs.hivel.ai/faqs/team-and-user-management-faqs) sun-brightdesktopmoon sun-brightdesktopmoon --- # Why am I not able to select more than 6 months at a time? | Hivel By default, Hivel provides a selection flexibility of **180 days** for all organizations. #### [hashtag](https://docs.hivel.ai/faqs/system-behavior-and-limitations-faqs/why-am-i-not-able-to-select-more-than-6-months-at-a-time#why-180-days) Why 180 Days? * This timeframe aligns with the typical needs of leaders and managers, who often review **two quarters of performance** to analyze trends, identify differences, and take action effectively. #### [hashtag](https://docs.hivel.ai/faqs/system-behavior-and-limitations-faqs/why-am-i-not-able-to-select-more-than-6-months-at-a-time#need-more-flexibility) Need more flexibility? * If you’d like to extend the filter beyond 180 days, simply let us know, and we can adjust it to suit your organization’s requirements. circle-info Here’s a quick hack😉: If you want to select a full year in your filters, go to [Release Configuration](https://docs.hivel.ai/faqs/metrics-and-data-faqs/how-to-see-all-the-metrics-by-sprints-or-releases) , define the one-year date range, and give it a name (e.g., "Yearly View"). Once saved, it will appear in your regular filters for easy access! [PreviousSystem Behavior & Limitations FAQschevron-left](https://docs.hivel.ai/faqs/system-behavior-and-limitations-faqs) [NextWhy does the filters change when I move to dashboards but in other screen it remains same?chevron-right](https://docs.hivel.ai/faqs/system-behavior-and-limitations-faqs/why-does-the-filters-change-when-i-move-to-dashboards-but-in-other-screen-it-remains-same) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Project Management | Hivel [Jirachevron-right](https://docs.hivel.ai/integrations/project-management/jira) [Azure Boardschevron-right](https://docs.hivel.ai/integrations/project-management/azure-boards) [ClickUpchevron-right](https://docs.hivel.ai/integrations/project-management/clickup) [PreviousAzure GIT Serverchevron-left](https://docs.hivel.ai/integrations/scm/azure/azure-git-server) [NextJirachevron-right](https://docs.hivel.ai/integrations/project-management/jira) sun-brightdesktopmoon sun-brightdesktopmoon --- # Team & User Management FAQs | Hivel [Why can't I remove a user from a team?chevron-right](https://docs.hivel.ai/faqs/team-and-user-management-faqs/why-cant-i-remove-a-user-from-a-team) [How to change a team owner?chevron-right](https://docs.hivel.ai/faqs/team-and-user-management-faqs/how-to-change-a-team-owner) [How to mark leaves & absences?chevron-right](https://docs.hivel.ai/faqs/team-and-user-management-faqs/how-to-mark-leaves-and-absences) [Why do I see "No existing user found" message while loginchevron-right](https://docs.hivel.ai/faqs/team-and-user-management-faqs/why-do-i-see-no-existing-user-found-message-while-login) [PreviousFAQschevron-left](https://docs.hivel.ai/faqs) [NextWhy can't I remove a user from a team?chevron-right](https://docs.hivel.ai/faqs/team-and-user-management-faqs/why-cant-i-remove-a-user-from-a-team) sun-brightdesktopmoon sun-brightdesktopmoon --- # Google Calendar | Hivel [How to integrate Google Calendar in Hivelchevron-right](https://docs.hivel.ai/integrations/calendar/google-calendar/how-to-integrate-google-calendar-in-hivel) [PreviousCalendarchevron-left](https://docs.hivel.ai/integrations/calendar) [NextHow to integrate Google Calendar in Hivelchevron-right](https://docs.hivel.ai/integrations/calendar/google-calendar/how-to-integrate-google-calendar-in-hivel) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to improve Speed? | Hivel Speed is one of the pillars in software delivery performance, directly impacting how quickly features and fixes reach your customers. But improving speed is not just about accelerating the process; it's about optimizing every phase to ensure quicker delivery without compromising quality. In this section, we focus on key speed metrics: * **Cycle Time** * **Coding Time** * **Review Time** * **Merge Time** * **Pick Up Time** Each of these metrics reflects a distinct phase of the software delivery process. By understanding and improving each, teams can shorten their time to delivery and respond more quickly to changing business needs. In the following pages, we’ll dive into each metric, explore strategies for improvement, and look at the tools and practices that can help optimize your team's delivery speed. Whether you're looking to streamline your development process, accelerate code reviews, or reduce merge delays, this guide will provide actionable insights. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed#key-metrics-to-track-speed) Key Metrics to Track Speed Understanding and improving speed starts with tracking the right metrics. These are the key metrics that represent different stages of the software delivery cycle: * **Cycle Time** The total time it takes from the _First Commit_ till _PR Merge_; shorter cycle time means faster feedback and quicker delivery. * **Coding Time** The time from the _First Commit_ till _PR Open_. Efficient coding processes and practices reduce bottlenecks and help speed up delivery. * **Review Time** The time spent in review i.e from the time _PR is Open to Review_ till _PR is Approved_. Minimizing review time is critical for faster iterations. * **Merge Time** The time taken to integrate changes into the main codebase after approval. Reducing merge time ensures faster deployment. * **Pick Up Time** The time before a developer picks up new work after finishing previous tasks. A streamlined process helps maintain consistent flow. While bottlenecks can certainly slow down progress, improving speed is not solely about identifying issues. It's about understanding the processes behind each metric and applying strategies that boost efficiency across the entire delivery pipeline. In the following sections, we’ll break down each of these metrics in detail and provide actionable strategies to optimize them. Whether you want to: * Streamline the **development process** * Speed up **code reviews** * Reduce delays in **merging code** * Minimize **pick up times** We’ll guide you through practical steps and best practices that can make a significant impact on your team's speed. * * * [PreviousImprove Performancechevron-left](https://docs.hivel.ai/improve-performance) [NextWhat to do if my Cycle Time is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high) Last updated 6 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How can I see the progress against my goals? | Hivel Once you have [set your goalsarrow-up-right](https://hivel.gitbook.io/knowlegebase/using-hivel/goals) you can easily track the progress against them by [downloading a Goals reportarrow-up-right](https://hivel.gitbook.io/knowlegebase/using-hivel/cockpit/how-to-download-reports#other-reports) . You can set the frequency either weekly, monthly, or quarterly to see how the teams have been faring against their targets at regular intervals. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FsO8bCEsz2CAHmGszUITU%252Fimage.png%3Falt%3Dmedia%26token%3De149d781-1550-40e6-a8ac-4327da052e75&width=768&dpr=3&quality=100&sign=39c6e532&sv=2) [PreviousReporting & Goal Tracking FAQschevron-left](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs) [NextHow to measure impact of Copilots using Hivel?chevron-right](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/how-to-measure-impact-of-copilots-using-hivel) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Calendar | Hivel [Google Calendarchevron-right](https://docs.hivel.ai/integrations/calendar/google-calendar) [Microsoft Outlookchevron-right](https://docs.hivel.ai/integrations/calendar/microsoft-outlook) [PreviousSetting up your own key for AI featureschevron-left](https://docs.hivel.ai/integrations/ai-tools/setting-up-your-own-key-for-ai-features) [NextGoogle Calendarchevron-right](https://docs.hivel.ai/integrations/calendar/google-calendar) sun-brightdesktopmoon sun-brightdesktopmoon --- # What to do if my Coding Time is high? | Hivel ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-coding-time-is-high#identify-which-team-or-repo) Identify which team or repo As a first step we should understand which team or repo is facing high coding times so that we can evaluate if that is expected or not given the business context and focus on them. You can do this in the Cockpit, by switching to tabular view and sorting on coding time column. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F99TAv4v2sUBVZ4jjblbL%252FGIF%2520Recording%2520Aug%252012%2520from%2520Jumpshare%2520%281%29.gif%3Falt%3Dmedia%26token%3D410ae94d-9bbe-455c-a922-a71adfb3fa9c&width=768&dpr=3&quality=100&sign=e873c4f6&sv=2) ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-coding-time-is-high#causes-of-high-coding-time) Causes of high coding time * **Poorly Defined Requirements:** If requirements are unclear or incomplete, developers may spend significant time trying to understand the scope or may need to rework code later. * **Technical Debt:** High levels of technical debt make it harder and slower to implement new features or fix bugs due to a tangled or outdated codebase. * **Lack of Proper Tooling:** Without efficient tools for coding, debugging, and testing, developers spend more time on manual or repetitive tasks. * **Scope Creep:** When the scope of a project expands beyond the original plan, developers must spend additional time coding features or making adjustments. * **Frequent Context Switching:** Developers who are interrupted frequently or required to switch between tasks lose productivity as they need time to refocus. * **Dependencies on External Teams or Services:** Waiting on other teams or external services to provide necessary inputs can cause delays in the coding process. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-coding-time-is-high#how-to-reduce-coding-time) How to reduce coding time? * **Clearly Define Requirements:** Collaborate closely with stakeholders to ensure all requirements are fully understood before coding begins. Use tools like user stories, acceptance criteria, and wireframes to clarify expectations. * **Manage Technical Debt:** Regularly refactor code to eliminate unnecessary complexity and address known issues. Prioritize paying down technical debt as part of the development process. * **Invest in Training and Skill Development:** Provide ongoing training, workshops, and access to resources that help developers stay up-to-date with the latest tools and technologies. * **Minimize Context Switching:** Organize work in a way that allows developers to focus on one task at a time. Avoid assigning multiple high-priority tasks simultaneously, and batch similar tasks together. * **Leverage Code Reuse:** Create and maintain a library of reusable components, modules, or functions. Encourage developers to use these resources wherever possible. * **Encourage Pair Programming and Knowledge Sharing:** Implement pair programming for complex tasks or as a regular practice to encourage knowledge sharing and reduce the time needed to resolve issues. [PreviousWhat to do if my Cycle Time is high?chevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high) [NextWhat to do if my Review Time is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-review-time-is-high) Last updated 1 year ago * [Identify which team or repo](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-coding-time-is-high#identify-which-team-or-repo) * [Causes of high coding time](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-coding-time-is-high#causes-of-high-coding-time) * [How to reduce coding time?](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-coding-time-is-high#how-to-reduce-coding-time) sun-brightdesktopmoon sun-brightdesktopmoon --- # What metrics can I use to prevent developer burnout? | Hivel Using metrics effectively can help identify early signs of developer burnout and prevent it by promoting healthier work practices and ensuring a balanced workload. Here are key strategies and metrics to monitor: 1. **Track work-in-progress (WIP) limits** * **Metric**: The number of tasks a developer is working on simultaneously. * **How It Helps**: If developers consistently have too many tasks in progress, it could indicate an unsustainable workload. Setting and enforcing WIP limits can reduce context switching and workload overwhelm, preventing burnout. 2. **Monitor cycle time and lead time** * **Metric**: Cycle time measures how long it takes for work to be completed once started, while lead time measures the total time from request to delivery. * **How It Helps**: Increasing cycle times can signal delays and bottlenecks, which could frustrate developers. If lead times grow, it may suggest the team is taking on too much work, leading to stress. Monitoring these metrics helps balance workloads. 3. **Evaluate story point velocity trends** * **Metric**: The average number of story points completed per sprint or iteration. * **How It Helps**: A sudden increase in velocity may indicate that developers are rushing through tasks, potentially at the expense of quality and mental health. On the other hand, a significant drop in velocity could indicate disengagement or exhaustion. 4. **Monitor pull request (PR) size and review time** * **Metric**: The size of pull requests and the average time spent reviewing them. * **How It Helps**: Large pull requests or rushed review times can lead to cognitive overload and fatigue. Encouraging smaller, more manageable PRs allows for more efficient reviews and reduces pressure on developers. 5. **Track context switching frequency** * **Metric**: The number of times developers switch between different tasks or projects. * **How It Helps**: High levels of context switching are draining and can lead to reduced productivity and increased stress. Monitoring this can help managers limit the number of simultaneous tasks assigned to developers, promoting focus and clarity. 6. **Evaluate bug reopen rate** * **Metric**: The percentage of bugs that need to be reopened after they were marked as fixed. * **How It Helps**: A high bug reopen rate might indicate that developers are being pushed to complete work too quickly, leading to errors. Lowering the pace to allow for better quality control can reduce stress and rework. 7. **Track unplanned work** * **Metric**: The amount of time developers spend on unplanned tasks such as emergency bug fixes or ad hoc requests. * **How It Helps**: An increase in unplanned work may lead to unpredictable schedules and stress, disrupting the developer’s flow. Monitoring this can help teams create buffer time or reorganize their sprint planning to accommodate these tasks without causing burnout. 8. **Use employee satisfaction surveys** * **Metric**: Regularly gather feedback through pulse surveys or anonymous questionnaires that ask developers about their stress levels, workload, and general well-being. * **How It Helps**: Direct feedback from developers provides insights that numbers alone can't capture. Regularly checking in with developers helps identify potential burnout risks before they become serious. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-planning-and-throughput/what-metrics-can-i-use-to-prevent-developer-burnout#proactive-steps-beyond-metrics) Proactive Steps Beyond Metrics: * **Foster an open culture**: Beyond tracking, I’d create a safe environment where developers feel comfortable voicing concerns. Burnout often goes unspoken until it’s too late. Regular 1-on-1s help spot early signs of fatigue. * **Encourage breaks and time off**: I’d actively encourage developers to take breaks and use their vacation days. Healthy work habits are essential for long-term productivity. * **Set clear boundaries on working hours**: I’d set and model expectations around not working after hours, unless in exceptional cases. This ensures a healthier balance between work and personal time. * **Implement capacity-based sprint planning**: I’d ensure that sprint planning is based on actual team capacity and historical velocity, rather than idealized goals. Under-promise, over-deliver should be the approach to avoid unrealistic expectations. By combining these metrics and cultural practices, we can proactively manage workloads, create a healthier work environment, and help prevent developer burnout before it becomes a serious issue. [PreviousLeveraging data for more effective sprint planningchevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-planning-and-throughput/leveraging-data-for-more-effective-sprint-planning) [NextHow to track, manage, and reduce technical debt?chevron-right](https://docs.hivel.ai/improve-performance/how-to-track-manage-and-reduce-technical-debt) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # What to do if my Merge Time is high? | Hivel ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-merge-time-is-high#identify-which-team-or-repo) Identify which team or repo As a first step we should understand which team or repo is facing high merge times so that we can evaluate if that is expected or not given the business context and focus on them. You can do this in the Cockpit, by switching to tabular view and sorting on merge time column. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F99TAv4v2sUBVZ4jjblbL%252FGIF%2520Recording%2520Aug%252012%2520from%2520Jumpshare%2520%281%29.gif%3Falt%3Dmedia%26token%3D410ae94d-9bbe-455c-a922-a71adfb3fa9c&width=768&dpr=3&quality=100&sign=e873c4f6&sv=2) ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-merge-time-is-high#causes-for-high-merge-time) Causes for high merge time * **Merge Conflicts:** Conflicts between the branch being merged and the main codebase can occur, particularly if the branch has been out of sync for a while. Resolving these conflicts can take time, especially in large or complex projects. * **Multiple Stakeholder Reviews:** Involving multiple stakeholders or requiring approvals from different departments can add layers of complexity and delay the merging process. * **Technical Debt:** High levels of technical debt can make merging more difficult, as changes may need to work around or refactor existing code, which can slow down the review and merge process. * **Prioritization Issues:** If reviewing and merging PRs is not prioritized, they may sit in the queue for longer, leading to higher merge times. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-merge-time-is-high#how-to-reduce-merge-time) How to reduce merge time * **Automate Testing and CI/CD Pipelines:** Implement comprehensive automated testing (unit, integration, end-to-end) and continuous integration/continuous deployment (CI/CD) pipelines to catch issues early and streamline the merging process. * **Use Feature Flags for Incremental Releases:** Implement feature flags to merge changes incrementally, even if the full feature is not yet complete. This keeps the codebase up-to-date and reduces the risk of merge conflicts. * **Address Merge Conflicts Early:** Encourage developers to regularly rebase or merge the main branch into their feature branches to identify and resolve conflicts early. * **Optimize Codebase for Merge Efficiency:** Refactor and modularize the codebase where possible to ensure that changes in one area have minimal impact on others, reducing merge complexity. [PreviousWhat to do if my Review Time is high?chevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-review-time-is-high) [NextHow to improve Qualitychevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality) Last updated 1 year ago * [Identify which team or repo](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-merge-time-is-high#identify-which-team-or-repo) * [Causes for high merge time](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-merge-time-is-high#causes-for-high-merge-time) * [How to reduce merge time](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-merge-time-is-high#how-to-reduce-merge-time) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to track, manage, and reduce technical debt? | Hivel Tracking and managing technical debt while balancing it with the development of new features is a critical responsibility for any engineering leader. Left unchecked, technical debt can slow down development, introduce bugs, and frustrate developers, but focusing too much on it can delay the delivery of new features. Here’s a structured approach to both tracking and reducing technical debt while managing the trade-offs with feature development. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-track-manage-and-reduce-technical-debt#tracking-technical-debt) **Tracking Technical Debt** **A. Define and categorize technical debt** * **Action**: Break down technical debt into categories such as: * **Code debt** (e.g., complex or poorly structured code), * **Architecture debt** (e.g., outdated design decisions), * **Test debt** (e.g., insufficient test coverage), * **Documentation debt** (e.g., missing or outdated documentation). * **Benefit**: Categorizing helps you quantify and prioritize different types of debt more effectively, ensuring teams are aware of where the most serious debt lies. **B. Use automated code quality tools** * **Action**: Leverage tools such as **SonarQube**, **Code Climate**, or **ESLint** to track code complexity, duplicated code, and other quality issues automatically. * **Benefit**: These tools continuously analyze the codebase, giving you real-time data on the level of technical debt, making it easier to track debt trends over time. **C. Create a technical debt backlog** * **Action**: Maintain a separate backlog for technical debt items in your project management tool (e.g., Jira, Trello). Ensure that this backlog is reviewed and prioritized regularly. * **Benefit**: This allows for visibility into the debt and ensures that it's actively considered when planning future sprints or releases. **D. Measure debt impact** * **Action**: Assign an **impact score** to each piece of technical debt (e.g., how much it affects performance, maintenance, or feature development). Track metrics like: * Time developers spend on maintenance or fixing bugs caused by technical debt. * Time-to-market delays due to outdated systems or poorly structured code. * **Benefit**: Quantifying the impact helps to make data-driven decisions when prioritizing debt reduction versus feature development. **E. Use debt ratio metrics** * **Action**: Calculate and track **debt ratio metrics**, such as the ratio of time spent on technical debt versus new feature development or the ratio of bugs to features. * **Benefit**: These ratios help teams maintain a balance and ensure debt is kept at manageable levels. * * * ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-track-manage-and-reduce-technical-debt#reducing-technical-debt) **Reducing Technical Debt** **A. Adopt refactoring as a continuous process** * **Action**: Encourage developers to refactor code as part of their daily workflow rather than leaving it as a separate task. Set guidelines for small, incremental refactoring with every new feature or bug fix. * **Benefit**: This keeps technical debt from growing and makes it easier to manage without significant resource allocation. **B. Allocate specific time for technical debt** * **Action**: Dedicate a percentage of each sprint (e.g., 10-20%) specifically for technical debt reduction, such as refactoring, improving test coverage, or updating documentation. * **Benefit**: Regular attention ensures debt doesn’t accumulate unchecked and prevents major disruptions later on. **C. Focus on high-impact areas first** * **Action**: Prioritize technical debt in areas that are touched most frequently (e.g., critical parts of the codebase or components that are prone to bugs). * **Benefit**: This maximizes the ROI of debt reduction efforts by focusing on areas that will improve future development speed and reliability the most. **D. Include technical debt in the definition of done** * **Action**: Modify your team’s **definition of done** to include addressing any newly introduced technical debt before a feature or task is marked complete. * **Benefit**: This prevents the buildup of new debt while working on new features and encourages accountability for clean code. **E. Regularly review technical debt with the team** * **Action**: During retrospectives or sprint planning, review technical debt issues with the team. Ensure the debt backlog is visible and prioritized alongside features. * **Benefit**: Constant visibility and regular discussions help to ensure that debt doesn’t get deprioritized indefinitely. * * * ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-track-manage-and-reduce-technical-debt#managing-the-balance-between-technical-debt-and-new-features) **Managing the balance between technical debt and new features** **A. Establish a balance between debt and features (Debt-to-Feature Ratio)** * **Action**: Decide on a ratio of time to be spent on technical debt versus feature development. For example, allocate 70-80% of the sprint for feature work and 20-30% for technical debt, or adjust depending on the current state of the codebase. * **Benefit**: This keeps the team focused on delivering new features while also addressing debt on a regular basis, reducing the risk of long-term debt accumulation. **B. Use business value to prioritize debt reduction vs. new features** * **Action**: Collaborate with stakeholders to assess the business value of new features versus the potential productivity gains or risk reduction from addressing technical debt. * **Benefit**: When business impact is considered, it becomes easier to make the case for technical debt reduction when it's necessary, especially when debt starts affecting customer experience or development speed. **C. Schedule periodic "debt-only" sprints** * **Action**: Occasionally dedicate an entire sprint or cycle to addressing technical debt, especially when it starts affecting productivity or when there is downtime between major feature releases. * **Benefit**: This allows the team to focus purely on cleanup and optimization without the pressure of delivering new features, significantly reducing accumulated debt. **D. Monitor technical debt against velocity** * **Action**: Track how much technical debt is affecting your team’s velocity over time. If velocity is dropping due to excessive rework, bugs, or maintenance, it may be time to shift focus towards technical debt. * **Benefit**: This ensures that technical debt is addressed before it impacts delivery timelines and development speed. **E. Communicate trade-offs clearly with stakeholders** * **Action**: Keep stakeholders informed about the trade-offs between reducing technical debt and delivering new features. Use metrics (like defect rates, velocity drops, or time spent on maintenance) to demonstrate the long-term benefits of debt reduction. * **Benefit**: Transparency helps stakeholders understand why some features may be delayed and allows them to weigh the short-term gain of features against long-term productivity gains from debt reduction. * * * #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-track-manage-and-reduce-technical-debt#conclusion) **Conclusion:** Tracking and reducing technical debt while balancing feature development requires both structured processes and flexibility. By categorizing, monitoring, and prioritizing technical debt alongside feature work, and by maintaining clear communication with stakeholders, you can manage both effectively. Technical debt reduction should be seen as an investment in the long-term health of the codebase, and when managed correctly, it enables faster, more reliable feature development in the future. [PreviousWhat metrics can I use to prevent developer burnout?chevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-planning-and-throughput/what-metrics-can-i-use-to-prevent-developer-burnout) [NextWhat are the impacts of context switching on developer productivity and how to reduce it?chevron-right](https://docs.hivel.ai/improve-performance/what-are-the-impacts-of-context-switching-on-developer-productivity-and-how-to-reduce-it) Last updated 1 year ago * [Tracking Technical Debt](https://docs.hivel.ai/improve-performance/how-to-track-manage-and-reduce-technical-debt#tracking-technical-debt) * [Reducing Technical Debt](https://docs.hivel.ai/improve-performance/how-to-track-manage-and-reduce-technical-debt#reducing-technical-debt) * [Managing the balance between technical debt and new features](https://docs.hivel.ai/improve-performance/how-to-track-manage-and-reduce-technical-debt#managing-the-balance-between-technical-debt-and-new-features) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to Use Hivel Support | Hivel At Hivel, we are committed to providing our customers with the best possible experience, and we are thrilled to introduce **Hivel Support** designed to make your interactions with us even easier and more efficient. You can now: 1. **Access Our Knowledge Base Anytime** Find helpful articles, guides, and answers to common questions through our easy-to-navigate Knowledge Base. Whether you're looking for troubleshooting tips, how-to guides, or product updates, everything is just a few clicks away. 2. **Contact Us for Any Questions or Concerns** Have a question or need assistance? Our team is ready to help. You can reach out to us directly and we’ll ensure all your concerns are addressed quickly. ### [hashtag](https://docs.hivel.ai/hivel-support/how-to-use-hivel-support#getting-started) Getting Started To get started, simply **access the support widget** from within the platform. Go to your home page and click on the bubble in the bottom right corner of your screen. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FiyEHdTB4yywT9gt8BIEw%252Fimage.png%3Falt%3Dmedia%26token%3D6054f437-6b85-422b-a685-82ad6ea106fc&width=768&dpr=3&quality=100&sign=2944bfdc&sv=2) A window will open up, as shown below ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FimoWdtKBGXamibeXbeD0%252Fimage.png%3Falt%3Dmedia%26token%3D05a8226c-376f-43a1-a195-08ea2b02f710&width=768&dpr=3&quality=100&sign=8b10b6b3&sv=2) You can type your question to access relevant information or view our Knowledge Base here. Click on **“Raise a Ticket”**, fill in the required details, attach screenshots of the issue, and click **Submit**. Our support team will review your request and get back to you as soon as possible. circle-info _**Note**__: If the support widget doesn't load automatically, try refreshing the page or logging back into your account._ **Visit our customer Portal to view open tickets -** [support.hivel.aiarrow-up-right](https://support.hivel.ai/) Here you can view different tickets raised and their statuses, access our support widget, and browse our knowledge base. See the screenshot below: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FQY67SyRJA7aB6mrokPwC%252Fimagsdsdase.png%3Falt%3Dmedia%26token%3D3a9785d3-9c4b-4d23-bfbd-e51127040f56&width=768&dpr=3&quality=100&sign=84ac248a&sv=2) ### [hashtag](https://docs.hivel.ai/hivel-support/how-to-use-hivel-support#using-slack-to-raise-tickets) **Using Slack to Raise Tickets** We'll configure an extension in the Slack channel you share with Hivel. You can also **raise a ticket or ask a question using Slack**. To do so, simply: 1. Type your issue or query in the chat and tag **@Hivel Support**. 2. Monitor your slack channel for responses from Hivel. Sample attached below: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FPA6WMNsfSy51xTLtehos%252Fimage.png%3Falt%3Dmedia%26token%3D250dfb0f-14b4-46b2-bea1-658a3c6fd568&width=768&dpr=3&quality=100&sign=d9a4b439&sv=2) ### [hashtag](https://docs.hivel.ai/hivel-support/how-to-use-hivel-support#using-microsoft-teams-to-raise-tickets) **Using Microsoft Teams to Raise Tickets** We'll configure an extension in the Microsoft Teams channel you share with Hivel. You can raise a ticket or ask a question using Teams. To do so, simply: 1. Type your issue/ query in the chat and **react to your query with a 🎫 (ticket emoji)** 2. Monitor your Teams Channel for responses from Hivel. Sample attached below: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FstxA6YIoWashKwCRG8Ai%252Fimage.png%3Falt%3Dmedia%26token%3Da2a33456-617c-46b7-9916-d6dfee77867b&width=768&dpr=3&quality=100&sign=35026abf&sv=2) _**Please reach out to us if you have any questions.**_ [PreviousMarco - Code Review Agentchevron-left](https://docs.hivel.ai/faqs/marco-code-review-agent) Last updated 1 month ago * [Getting Started](https://docs.hivel.ai/hivel-support/how-to-use-hivel-support#getting-started) * [Using Slack to Raise Tickets](https://docs.hivel.ai/hivel-support/how-to-use-hivel-support#using-slack-to-raise-tickets) * [Using Microsoft Teams to Raise Tickets](https://docs.hivel.ai/hivel-support/how-to-use-hivel-support#using-microsoft-teams-to-raise-tickets) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to mark leaves & absences? | Hivel Leaves and absences can be marked in the Activity screen. These can be marked for the current day, the next day, or a custom duration along with a note. Both past and future dates can be selected for marking leaves and absences. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FP6aU3p7CDrPy3aKKLS7E%252FGIF%2520Recording%25202024-09-26%2520at%25204.47.50%2520PM.gif%3Falt%3Dmedia%26token%3D68ccc3f3-8d90-48f2-84cc-5a353a61ea62&width=768&dpr=3&quality=100&sign=f5835b4d&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fd12iBtfd9OyooDdffgn6%252Fimage.png%3Falt%3Dmedia%26token%3D196be409-a2b1-4d7d-9569-45e92c0cee27&width=768&dpr=3&quality=100&sign=42aa10ec&sv=2) Please note that this metric is for representational purposes only. Marking a team member as absent or on leave **does not exclude** their contributions from any calculation. Even if a person is marked as absent or on leave, any work they do—such as commits, PR reviews, or PR merges—**will still count** toward the overall delivery. This ensures that any effort made during their leave is recognized and contributes to the team's performance metrics, ensuring accuracy and reflecting the actual work done during the selected duration. This approach ensures that no contribution is overlooked, regardless of a person's official attendance status, leading to a more accurate representation of the team’s overall efforts and delivery. [PreviousHow to change a team owner?chevron-left](https://docs.hivel.ai/faqs/team-and-user-management-faqs/how-to-change-a-team-owner) [NextWhy do I see "No existing user found" message while loginchevron-right](https://docs.hivel.ai/faqs/team-and-user-management-faqs/why-do-i-see-no-existing-user-found-message-while-login) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # CI/CD | Hivel [Jenkinschevron-right](https://docs.hivel.ai/integrations/ci-cd/jenkins) [Jenkins Freestyle Integration with Ansible and Hivel Webhookchevron-right](https://docs.hivel.ai/integrations/ci-cd/jenkins-freestyle-integration-with-ansible-and-hivel-webhook) [PreviousMicrosoft Outlookchevron-left](https://docs.hivel.ai/integrations/calendar/microsoft-outlook) [NextJenkinschevron-right](https://docs.hivel.ai/integrations/ci-cd/jenkins) sun-brightdesktopmoon sun-brightdesktopmoon --- # Why can't I remove a user from a team? | Hivel Removing users from a team is only prohibited when the user is a team owner. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F7FAUsLUCidVPQeo6SJpd%252Fimage.png%3Falt%3Dmedia%26token%3D62b26872-e96e-43c6-90b4-bd187536ca13&width=768&dpr=3&quality=100&sign=49432ed0&sv=2) circle-info Refer [here](https://docs.hivel.ai/faqs/team-and-user-management-faqs/how-to-change-a-team-owner) to know how to change team owners. [How to change a team owner?chevron-right](https://docs.hivel.ai/faqs/team-and-user-management-faqs/how-to-change-a-team-owner) [What to do if my Cycle Time is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high) [PreviousTeam & User Management FAQschevron-left](https://docs.hivel.ai/faqs/team-and-user-management-faqs) [NextHow to change a team owner?chevron-right](https://docs.hivel.ai/faqs/team-and-user-management-faqs/how-to-change-a-team-owner) Last updated 8 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Leveraging data for more effective sprint planning | Hivel Leveraging data from tools like Jira and Git can significantly enhance sprint planning by providing insights into team performance, work patterns, and potential bottlenecks. Here are some key points on how to use data from both platforms for more effective sprint planning: 1. **Analyze historical performance** * **Jira**: Review past sprints in Jira to evaluate the completion rates, story point accuracy, and types of tasks that frequently roll over to the next sprint. * **Git**: Look at commit logs and merge activity to assess the volume and complexity of code changes, and how they correlate with task completion. * **Benefit**: Understanding historical trends helps in setting realistic expectations and improving future sprint planning accuracy. 2. **Measure cycle time and lead time** * **Jira**: Track how long it takes for a task to move from 'To Do' to 'Done' and how long tasks sit in each status. * **Git**: Use data from pull requests and branches to analyze how long code changes take to be merged and deployed after initial commit. * **Benefit**: Shortening cycle time and lead time can improve sprint velocity and reduce time-to-market. 3. **Assess work in progress (WIP) limits** * **Jira**: Monitor the number of tasks in progress at any given time to ensure that WIP limits are adhered to, promoting a smooth flow of work. * **Git**: Analyze branch activity to identify bottlenecks where work is piling up or stalling. * **Benefit**: Maintaining optimal WIP limits can help in reducing bottlenecks and improving team focus and productivity. 4. **Review pull request size and quality** * **Git**: Analyze the size and complexity of pull requests to ensure that they align with the task estimates and are manageable within the sprint timeframe. * **Benefit**: Smaller, well-defined pull requests are generally easier to review and integrate, leading to fewer errors and faster deployment. 5. **Conduct code review analytics** * **Git**: Review metrics from code reviews, such as time to review, number of iterations, and comments per pull request. * **Benefit**: Insights from code review analytics can help in improving code quality and identifying areas where developers may need additional support or training. 6. **Identify frequent contributors and bottlenecks** * **Git**: Identify who is committing code and how often, which can help in understanding individual workloads and contributions. * **Jira**: Look at task assignment patterns to see if work is being evenly distributed among team members. * **Benefit**: This can help in balancing workloads more effectively and pinpointing where additional resources or adjustments are needed. 7. **Monitor issue types and priorities** * **Jira**: Analyze the types of issues being logged and their priorities to ensure alignment with sprint goals and strategic objectives. * **Benefit**: This helps in prioritizing work that delivers the most value and aligns with long-term project goals. 8. **Facilitate continuous feedback** * **Both**: Implement a system for continuous feedback using data from both Jira and Git to inform daily stand-ups and retrospective meetings. * **Benefit**: Continuous feedback helps in making real-time adjustments to sprints and improving team dynamics and efficiency. By integrating data from both Jira and Git, teams can gain a comprehensive view of their development process, enabling more informed and effective sprint planning. This approach not only enhances productivity but also helps in achieving higher quality outputs and meeting project deadlines more consistently. [PreviousHow to improve planning and throughputchevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-planning-and-throughput) [NextWhat metrics can I use to prevent developer burnout?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-planning-and-throughput/what-metrics-can-i-use-to-prevent-developer-burnout) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to build a data-driven culture of Engineering? | Hivel Building a data-driven engineering culture is essential for making informed decisions, improving efficiency, and fostering innovation. Here are key points you can cover to guide organizations in fostering a culture where decisions are backed by data rather than intuition: #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering#id-1.-start-with-leadership-buy-in) 1\. **Start with Leadership Buy-In** * **Action**: Ensure that leadership supports and champions the use of data for decision-making across all levels. * **Why it matters**: Leadership sets the tone for the rest of the organization. When leaders prioritize data-driven approaches, it becomes part of the company’s values and practices. * **How to implement**: Encourage leadership to use engineering metrics and data during strategic meetings and planning sessions to demonstrate its value. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering#id-2.-define-key-metrics-and-kpis) 2\. **Define Key Metrics and KPIs** * **Action**: Identify the key metrics that matter most for your engineering team, such as cycle time, deployment frequency, mean time to repair (MTTR), change failure rate (CFR), and more. * **Why it matters**: Without clear and relevant metrics, teams won’t know what data to focus on or how to measure success. * **How to implement**: Collaborate with product, design, and engineering leadership to establish the most important metrics that align with both business goals and team performance. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering#id-3.-foster-a-culture-of-transparency-and-openness) 3\. **Foster a Culture of Transparency and Openness** * **Action**: Make engineering metrics visible and accessible to the entire team, from junior developers to executives. * **Why it matters**: Transparency encourages accountability and makes everyone feel responsible for improving metrics. It also helps team members understand how their work impacts overall goals. * **How to implement**: Use shared dashboards, regular team meetings, and retrospective discussions to review metrics and progress openly. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering#id-4.-encourage-data-driven-decision-making-at-every-level) 4\. **Encourage Data-Driven Decision Making at Every Level** * **Action**: Empower developers, team leads, and managers to make decisions based on data rather than intuition or past practices. * **Why it matters**: Building a data-driven culture means that all levels of the organization rely on data for decision-making, not just leadership. * **How to implement**: Encourage team members to ask, "What does the data say?" before making technical or strategic decisions. Provide training on interpreting and acting on the data. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering#id-5.-use-metrics-to-set-and-achieve-clear-goals) 5\. **Use Metrics to Set and Achieve Clear Goals** * **Action**: Align team and individual goals with specific, measurable metrics and KPIs to drive improvement. * **Why it matters**: Teams need measurable goals to work toward, and data-driven goals help clarify what success looks like. * **How to implement**: Implement OKRs (Objectives and Key Results) where each objective is tied to specific, data-driven key results (e.g., reduce cycle time by 20%, improve test coverage by 15%). #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering#id-6.-incorporate-data-into-retrospectives) 6\. **Incorporate Data into Retrospectives** * **Action**: Use engineering metrics as a central part of sprint retrospectives to review performance, bottlenecks, and areas of improvement. * **Why it matters**: Retrospectives are an ideal time to reflect on past performance. Data gives teams concrete evidence of what went well and what needs to improve, rather than relying on anecdotal feedback. * **How to implement**: Regularly review key metrics at the end of each sprint and use them to identify improvement areas or process changes. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering#id-7.-provide-continuous-education-and-training) 7\. **Provide Continuous Education and Training** * **Action**: Educate teams on the importance of data-driven decision-making and how to use data effectively. * **Why it matters**: Not everyone in the organization may be comfortable interpreting data, so providing the right training ensures teams can take advantage of analytics tools. * **How to implement**: Organize workshops, lunch-and-learns, or provide online resources for training team members on analytics tools, data interpretation, and best practices. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering#id-8.-promote-accountability-and-ownership) 8\. **Promote Accountability and Ownership** * **Action**: Hold teams and individuals accountable for the data, encouraging ownership over both successes and areas needing improvement. * **Why it matters**: Accountability drives performance improvement. When teams own their metrics, they are more likely to focus on achieving results. * **How to implement**: Tie individual and team performance reviews to data-driven metrics. Regularly recognize teams that achieve goals based on data insights. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering#id-9.-balance-data-with-context) 9\. **Balance Data with Context** * **Action**: Encourage teams to use data as a tool for decision-making while also understanding the context behind the data. * **Why it matters**: Data can sometimes lack the nuances of human judgment. Understanding the story behind the data ensures that decisions are both data-driven and contextually informed. * **How to implement**: Encourage teams to dig deeper when anomalies or surprising data points arise and combine qualitative insights with quantitative data for well-rounded decisions. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering#id-10.-make-data-driven-improvements-incremental) 10\. **Make Data-Driven Improvements Incremental** * **Action**: Use data to drive continuous, incremental improvements rather than chasing perfection all at once. * **Why it matters**: Small, data-driven adjustments can lead to significant long-term improvements. Trying to change everything at once can overwhelm teams and dilute the effectiveness of data insights. * **How to implement**: Set small, achievable data-driven goals for each sprint and regularly evaluate progress. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-build-a-data-driven-culture-of-engineering#id-11.-celebrate-data-driven-wins) 11\. **Celebrate Data-Driven Wins** * **Action**: Recognize and reward teams when they achieve success through data-driven initiatives. * **Why it matters**: Celebrating wins helps reinforce the value of using data to drive decisions and motivates teams to continue using data to guide their work. * **How to implement**: Highlight metrics improvements during team meetings or company-wide updates and tie these successes to data-backed strategies. By fostering a culture that relies on data for decision-making, organizations can reduce guesswork, improve efficiency, and drive performance improvements. Data-driven engineering ensures that every decision, from small technical choices to large strategic moves, is grounded in measurable, reliable information, leading to better outcomes. [PreviousWhat are the impacts of context switching on developer productivity and how to reduce it?chevron-left](https://docs.hivel.ai/improve-performance/what-are-the-impacts-of-context-switching-on-developer-productivity-and-how-to-reduce-it) [NextHow to balance speed and quality?chevron-right](https://docs.hivel.ai/improve-performance/how-to-balance-speed-and-quality) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Marco - Code Review Agent | Hivel [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#product-overview-and-differentiation) Product Overview & Differentiation ------------------------------------------------------------------------------------------------------------------------------------------ ### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#what-is-marco-hivels-code-review-agent) What is Marco - Hivel’s Code Review agent? Marco uses machine learning and advanced foundational Large Language Models (LLMs) to automatically analyze code changes for bugs, security vulnerabilities, and performance issues. Unlike traditional static analysis, Marco understands the deep context of your codebase, learns your team’s patterns, and provides actionable feedback directly within your pull requests (PRs). ### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#how-accurate-is-the-feedback-provided) How accurate is the feedback provided? By using built-in intelligence that analyzes codebase dependencies and learns from your specific coding style, Marco can provide highly relevant feedback that identifies over 95%+ of bugs in most cases, and catches critical issues that often slip past manual reviews. However, Marco is designed to complement human reviewers, not replace them, allowing humans to focus on high-level architecture and business logic after the first pass by AI code review. ### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#can-the-agent-catch-issues-that-humans-typically-miss) Can the agent catch issues that humans typically miss? Yes. Human reviewers often experience fatigue, which can lead to significant quality gaps, especially when reviews are rushed or when dealing with larger, more complex pull requests. By automating the "repetitive task" of routine checks, Marco provides a consistent quality layer that doesn't get tired. This reduces reviewer fatigue by allowing your engineers to offload tedious syntax and standard checks to the AI, ensuring they can focus their mental energy on high-level architecture and business logic where human intuition is most valuable. ### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#how-does-the-complexity-score-help-clear-the-pr-backlog) How does the Complexity Score help clear the PR backlog? Marco assigns a 1-10 score to every pull request by scanning for review bottlenecks—such as intricate pointer logic, deep structural nesting, and complex dependencies. This score transforms your review process from a "repetitive task" into a prioritized, review-ready queue. By identifying "big PR" blind spots at a glance, you can ensure logically dense changes receive the senior-level attention they require while allowing routine updates to move quickly. This data-driven approach reduces reviewer fatigue, prevents engineers from becoming bottlenecks, and allows your team to allocate their focus effectively—shortening review cycles without lowering the quality bar. ### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#technical-capabilities) Technical Capabilities #### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#which-programming-languages-are-supported) Which programming languages are supported? Marco is designed to support all major programming languages, including Python, JavaScript, Java, C++, Go, Ruby, and TypeScript. While proficiency may be highest in the most popular languages, advanced context engines allow Marco to work across entire stacks, including frontends, backends, and even Infrastructure-as-code like Terraform. #### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#how-does-marco-understand-my-entire-codebase) How does Marco understand my entire codebase? Marco analyzes your codebase by examining each file for dependencies and coding standards. It creates summaries at both the file and folder levels, capturing necessary context like dependencies, architectural standards, and functionality. Marco tracks bidirectional dependencies, identifying both the files that your code depends on and those that depend on it. Marco selectively provides only the most relevant context - avoiding information overload by focusing on key pieces of information rather than feeding in irrelevant data. This approach ensures high accuracy and avoids performance degradation. Marco uses advanced LLMs combined with custom algorithms to maintain efficient code organization and ensure optimal performance. ### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#security-and-data-privacy) Security & Data Privacy #### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#is-my-code-secure-and-private) Is my code secure and private? Security is a primary focus. Marco utilizes industry-standard encryption and adheres to compliance standards - ISO 27001, SOC 2 Type II and GDPR. Data isolation ensures that no unauthorized parties have access to your code during the review process. #### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#do-you-store-my-code) Do you store my code? No, we do not. Code collected for a review is typically disposed of as soon as the review is finished.By default, our tool automatically opts you out of data storage. ### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#workflow-and-integration) Workflow & Integration #### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#where-does-marco-fit-into-my-development-workflow) Where does Marco fit into my development workflow? The agent integrates seamlessly into existing workflows without requiring context switching. Key integration points include: Git Platforms: Automated reviews on GitHub & GitLab. #### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#can-marco-enforce-our-organizations-specific-coding-standards) Can Marco enforce our organization’s specific coding standards? Yes. You can define custom rulesets for architecture patterns, security policies, and style. Marco learns from your PR history and past comments to understand what "good code" looks like for your specific team, enforcing these standards consistently across all contributors. ### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#roi-measuring-success) ROI : Measuring Success #### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#what-kind-of-efficiency-gains-should-i-expect) What kind of efficiency gains should I expect? By pre-reviewing every pull request and surfacing high-signal issues, teams can significantly reduce review time. Automating routine checks frees up valuable time, allowing developers to focus on more complex tasks and high-level decision-making, leading to overall productivity improvements across the team. #### [hashtag](https://docs.hivel.ai/faqs/marco-code-review-agent#how-do-i-measure-the-success-of-hivels-marco) How do I measure the success of Hivel’s Marco? Success can be tracked through several key metrics: * Reduction in production bugs and "bug escape" rates. * Decreased review time and PR backlog. * Improved security, such as catching hardcoded credentials or SQL injection early. * Developer satisfaction and increased velocity. [PreviousHow is unaccounted work calculated and how to address it?chevron-left](https://docs.hivel.ai/faqs/metrics-and-data-faqs/how-is-unaccounted-work-calculated-and-how-to-address-it) [NextHow to Use Hivel Supportchevron-right](https://docs.hivel.ai/hivel-support/how-to-use-hivel-support) Last updated 1 month ago * [Product Overview & Differentiation](https://docs.hivel.ai/faqs/marco-code-review-agent#product-overview-and-differentiation) * [What is Marco - Hivel’s Code Review agent?](https://docs.hivel.ai/faqs/marco-code-review-agent#what-is-marco-hivels-code-review-agent) * [How accurate is the feedback provided?](https://docs.hivel.ai/faqs/marco-code-review-agent#how-accurate-is-the-feedback-provided) * [Can the agent catch issues that humans typically miss?](https://docs.hivel.ai/faqs/marco-code-review-agent#can-the-agent-catch-issues-that-humans-typically-miss) * [How does the Complexity Score help clear the PR backlog?](https://docs.hivel.ai/faqs/marco-code-review-agent#how-does-the-complexity-score-help-clear-the-pr-backlog) * [Technical Capabilities](https://docs.hivel.ai/faqs/marco-code-review-agent#technical-capabilities) * [Security & Data Privacy](https://docs.hivel.ai/faqs/marco-code-review-agent#security-and-data-privacy) * [Workflow & Integration](https://docs.hivel.ai/faqs/marco-code-review-agent#workflow-and-integration) * [ROI : Measuring Success](https://docs.hivel.ai/faqs/marco-code-review-agent#roi-measuring-success) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to integrate Google Calendar in Hivel | Hivel Integrating Google Calendar with Hivel involves a few key steps to ensure that all necessary calendars are accessible and synced properly. Below is a step-by-step guide to help you through the process: #### [hashtag](https://docs.hivel.ai/integrations/calendar/google-calendar/how-to-integrate-google-calendar-in-hivel#create-a-google-account) Create a Google account Create an account for Hivel which has at least "View" access to all the applicable developer's Google accounts. * You have the option to use either a normal user account with access to other calendars or a service account, but it is recommended to use a service account. #### [hashtag](https://docs.hivel.ai/integrations/calendar/google-calendar/how-to-integrate-google-calendar-in-hivel#integrate-google-calendar-with-hivel) Integrate Google Calendar with Hivel 1\. Log in to the Hivel platform using the service account. 2\. Navigate to the Settings -> Integrations section from the dashboard. 3\. Find Google Calendar in the list of available integrations and click on Connect. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FAV7aUHCTqZ44VfRTyTxL%252FCapture-2025-02-28-145206.png%3Falt%3Dmedia%26token%3Daaa4fb58-6ef8-4d34-8dd4-f1eba8ec97cd&width=768&dpr=3&quality=100&sign=91275c69&sv=2) Follow the on-screen prompts to allow permissions for Hivel to access your Google Calendar data. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FoNlnkyvpMwgYOsJ98EB7%252Fimage.png%3Falt%3Dmedia%26token%3Dfc51af7d-b023-4dce-b975-1469e4ea92a7&width=768&dpr=3&quality=100&sign=e80bcdb&sv=2) This should help you seamlessly integrate Google Calendar with Hivel, allowing you to understand the schedule of your team effectively within the platform. For further assistance or any issues encountered during the integration, please contact our support team at [\[email protected\].envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#7704020707180503371f1e01121b59161e59) [PreviousGoogle Calendarchevron-left](https://docs.hivel.ai/integrations/calendar/google-calendar) [NextMicrosoft Outlookchevron-right](https://docs.hivel.ai/integrations/calendar/microsoft-outlook) Last updated 5 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to change a team owner? | Hivel To change the team owner of a team, follow the below steps: 1. Go to Settings screen -> Teams -> Select the particular team 2. Click on the three dots on top 3. Change the team owner and save ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F3HY3m790T9V6uRisTf7n%252FScreen%2520Cast%25202026-01-30%2520at%25204.37.45%2520PM.gif%3Falt%3Dmedia%26token%3Dc0dde368-f80a-4ef9-a3c9-e3d14293483f&width=768&dpr=3&quality=100&sign=e4470efc&sv=2) All done!🙌 [PreviousWhy can't I remove a user from a team?chevron-left](https://docs.hivel.ai/faqs/team-and-user-management-faqs/why-cant-i-remove-a-user-from-a-team) [NextHow to mark leaves & absences?chevron-right](https://docs.hivel.ai/faqs/team-and-user-management-faqs/how-to-mark-leaves-and-absences) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Azure | Hivel [Azure DevOpschevron-right](https://docs.hivel.ai/integrations/scm/azure/azure-devops) [Azure GIT Serverchevron-right](https://docs.hivel.ai/integrations/scm/azure/azure-git-server) [PreviousValidation at a metric level for BitBucketchevron-left](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket) [NextAzure DevOpschevron-right](https://docs.hivel.ai/integrations/scm/azure/azure-devops) sun-brightdesktopmoon sun-brightdesktopmoon --- # What to do if my Review Time is high? | Hivel ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-review-time-is-high#identify-which-team-or-repo) Identify which team or repo As a first step we should understand which team or repo is facing high review times so that we can evaluate if that is expected or not given the business context and focus on them. You can do this in the Cockpit, by switching to tabular view and sorting on review time column. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F99TAv4v2sUBVZ4jjblbL%252FGIF%2520Recording%2520Aug%252012%2520from%2520Jumpshare%2520%281%29.gif%3Falt%3Dmedia%26token%3D410ae94d-9bbe-455c-a922-a71adfb3fa9c&width=768&dpr=3&quality=100&sign=e873c4f6&sv=2) ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-review-time-is-high#causes-for-high-review-time) Causes for high review time * **Complex Code**: If the code submitted for review is overly complex or lacks proper documentation, it can take longer for reviewers to understand and evaluate it. * **Code Smells**: Issues like code duplication, lack of modularization, and poor naming conventions can slow down the review process. * **Limited Reviewer Availability**: If there are not enough qualified reviewers available, the review queue can become backlogged. * **Inconsistent Review Standards**: If the team does not have clear guidelines or standards for code reviews, different reviewers might have varying expectations, leading to longer discussions and revisions. * **Ambiguous Feedback**: If reviewers provide vague or unclear feedback, the author might need to go back and forth multiple times to understand and address the issues. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-review-time-is-high#how-to-reduce-review-time) How to reduce review time After identifying the teams, users, or repositories having high review times, it's essential to take proactive steps to reduce them. Below are some recommended strategies to help improve review time: * **Limit PR Size:** Smaller PRs are easier and faster to review. Encourage developers to break down large features or fixes into smaller, manageable pieces. * **Incremental Changes:** Adopt a workflow where changes are submitted and reviewed incrementally rather than in large, monolithic chunks. * **Define Review Scope:** Clearly define what reviewers should focus on (e.g., logic, performance, security, readability) to prevent them from getting bogged down in less critical issues. * **Feedback Loop:** Establish an efficient feedback loop between reviewers and developers to clarify any issues or concerns rapidly, reducing back-and-forth delays. * **Encourage Timely and Quality Reviews:** Foster a culture where timely reviews are a priority. Acknowledge and reward team members who consistently contribute to swift and thorough reviews. * **Rotating Reviewers:** Rotate reviewers to avoid bottlenecks caused by one person being unavailable. [PreviousWhat to do if my Coding Time is high?chevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-coding-time-is-high) [NextWhat to do if my Merge Time is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-merge-time-is-high) Last updated 1 year ago * [Identify which team or repo](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-review-time-is-high#identify-which-team-or-repo) * [Causes for high review time](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-review-time-is-high#causes-for-high-review-time) * [How to reduce review time](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-review-time-is-high#how-to-reduce-review-time) sun-brightdesktopmoon sun-brightdesktopmoon --- # Why do I see "No existing user found" message while login | Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FkNieRtMnWSf2zHBDzKVA%252Fimage.png%3Falt%3Dmedia%26token%3Dd1f82960-206c-402c-9a30-808240635abe&width=768&dpr=3&quality=100&sign=89e9e95d&sv=2) If this is your first time logging into Hivel, you may encounter a message prompting you to complete the setup. To proceed, follow these steps: 1. **Check your email for an invitation**: * Look for an invite email from your Hivel admin in your inbox. * Accept the invitation to activate your account. 2. **No invite? No problem**: * Click on **"Get Started"** on the login screen. * Sign up using your organization credentials. * Once registered, you should be able to log in without issues. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FartRTXX7TUHpWbODGxuO%252Fimage.png%3Falt%3Dmedia%26token%3D34e0a214-2695-492a-b1d8-83b0dc94be40&width=768&dpr=3&quality=100&sign=bc4855a7&sv=2) If you run into any trouble, feel free to contact us at **[\[email protected\]](https://docs.hivel.ai/cdn-cgi/l/email-protection) ** for assistance. [PreviousHow to mark leaves & absences?chevron-left](https://docs.hivel.ai/faqs/team-and-user-management-faqs/how-to-mark-leaves-and-absences) [NextPR, Issues & Workflow FAQschevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # BitBucket | Hivel [BitBucket Integrationchevron-right](https://docs.hivel.ai/integrations/scm/bitbucket/bitbucket-integration) [Validation at a metric level for BitBucketchevron-right](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket) [PreviousHow to ensure Gitlab token has access to required groups/repositorieschevron-left](https://docs.hivel.ai/integrations/scm/gitlab/how-to-ensure-gitlab-token-has-access-to-required-groups-repositories) [NextBitBucket Integrationchevron-right](https://docs.hivel.ai/integrations/scm/bitbucket/bitbucket-integration) sun-brightdesktopmoon sun-brightdesktopmoon --- # Jira | Hivel [How to Integrate Jira with OAuth 2.0chevron-right](https://docs.hivel.ai/integrations/project-management/jira/how-to-integrate-jira-with-oauth-2.0) [How to Re-authorize Jira with OAuth 2.0chevron-right](https://docs.hivel.ai/integrations/project-management/jira/how-to-re-authorize-jira-with-oauth-2.0) [How to integrate Jira Server with Hivelchevron-right](https://docs.hivel.ai/integrations/project-management/jira/how-to-integrate-jira-server-with-hivel) [PreviousProject Managementchevron-left](https://docs.hivel.ai/integrations/project-management) [NextHow to Integrate Jira with OAuth 2.0chevron-right](https://docs.hivel.ai/integrations/project-management/jira/how-to-integrate-jira-with-oauth-2.0) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Azure Boards | Hivel **Data Access by Hivel** * Hivel accesses the past 60-90 days of commits and pull requests from active repositories during the initial sync. **Authorization Mechanism** * Hivel gets access using a Personal Access Token, which can be created using this [linkarrow-up-right](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows#create-a-pat) . * Users maintain full control and can withdraw access anytime by revoking the Personal Access Token. * Ensure '**All accessible organizations'** is selected while creating the Personal Access Token. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FWQ23CAsvj8bRFQTgfyw0%252Fimage.png%3Falt%3Dmedia%26token%3Dc576014f-0e52-4f44-b6d0-48350b76afb0&width=300&dpr=3&quality=100&sign=eb68633c&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDI3qRLMqzJogW2VKSQ51%252Fimage.png%3Falt%3Dmedia%26token%3Daa7a48e4-3c2d-4c53-8b9f-23c237d98c46&width=300&dpr=3&quality=100&sign=48e1c3c0&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F6QVTdt5mgSnX6FhKspRJ%252Fimage.png%3Falt%3Dmedia%26token%3D5a55fa48-b093-40a4-84b5-03713683899d&width=300&dpr=3&quality=100&sign=9d105af3&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F0vccKgvrZradW7UZ5FWB%252Fimage.png%3Falt%3Dmedia%26token%3Db930bc69-052a-4717-af63-c44e321cc522&width=768&dpr=3&quality=100&sign=f376b9b0&sv=2) **Requirements** * Ensure to create the Personal Access Token from an account that has "Project Administrator" permissions for all relevant projects and repositories. **Best Practice** * Opt for a service account rather than an individual-linked account. * Service accounts are typically overseen by the company's admin. **Personal Access Token Permissions** * Please ensure you select all the options below while creating a Personal Access Token. * **Project And Team**: Read * **User Profile**: Read * **Code**: Read * **Build**: Read * **Graph:** Read * **Work Items:** Read ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fbvzlj9oxA4zEMkKSLa6S%252Fimage.png%3Falt%3Dmedia%26token%3D6dfe77b0-8342-4692-be62-801df0224749&width=300&dpr=3&quality=100&sign=57fef77b&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F05fLXq4XnHbDXgIB9rEN%252Fimage.png%3Falt%3Dmedia%26token%3D1550c531-0a79-46cb-86bb-366b6ff12041&width=300&dpr=3&quality=100&sign=7e061d34&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FC1tDnhhlCe2nBzUwHPCF%252Fimage.png%3Falt%3Dmedia%26token%3D75885a07-7f18-4598-8134-7d35b19bcf17&width=300&dpr=3&quality=100&sign=ffd76eea&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FPIqxw6g5fSl2dAtCLNoy%252Fimage.png%3Falt%3Dmedia%26token%3D86a43ff4-44b4-4d0d-ba6c-2b9ee2febcb9&width=300&dpr=3&quality=100&sign=11a1ebbe&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FRkS5YqtDTaONUGEIiCy1%252Fimage.png%3Falt%3Dmedia%26token%3Da17f527d-4bca-4a02-86fe-2db9244191e9&width=300&dpr=3&quality=100&sign=28352300&sv=2) **You are almost done.** * Once a Personal Access Token is created, please copy it and share it with the Hivel team. * You will receive an email from the Hivel team once your data is all up and running. [PreviousHow to integrate Jira Server with Hivelchevron-left](https://docs.hivel.ai/integrations/project-management/jira/how-to-integrate-jira-server-with-hivel) [NextClickUpchevron-right](https://docs.hivel.ai/integrations/project-management/clickup) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # API Documentation | Hivel [Deployment Events APIchevron-right](https://docs.hivel.ai/integrations/api-documentation/deployment-events-api) [Create Incident APIchevron-right](https://docs.hivel.ai/integrations/api-documentation/create-incident-api) [DORA Metrics Powered by New APIs in Hivelchevron-right](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel) [PreviousSlack Integration with Hivelchevron-left](https://docs.hivel.ai/integrations/slack-integration-with-hivel) [NextDeployment Events APIchevron-right](https://docs.hivel.ai/integrations/api-documentation/deployment-events-api) sun-brightdesktopmoon sun-brightdesktopmoon --- # Gitlab | Hivel [Gitlab Serverchevron-right](https://docs.hivel.ai/integrations/scm/gitlab/gitlab-server) [Gitlab Cloudchevron-right](https://docs.hivel.ai/integrations/scm/gitlab/gitlab-cloud) [How to ensure Gitlab token has access to required groups/repositorieschevron-right](https://docs.hivel.ai/integrations/scm/gitlab/how-to-ensure-gitlab-token-has-access-to-required-groups-repositories) [PreviousHow to reauthorize Github with a classic token?chevron-left](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-reauthorize-github-with-a-classic-token) [NextGitlab Serverchevron-right](https://docs.hivel.ai/integrations/scm/gitlab/gitlab-server) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to ensure Gitlab token has access to required groups/repositories | Hivel Follow these steps to grant a service account access to required repositories: #### [hashtag](https://docs.hivel.ai/integrations/scm/gitlab/how-to-ensure-gitlab-token-has-access-to-required-groups-repositories#navigate-to-the-gitlab-group) **Navigate to the GitLab Group** 1. Log in to GitLab. 2. In the left sidebar, click **"Groups"** → **"Your Groups"**. 3. Select the Group where you want to add the service account. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FRMsY4JlEmBXFZKupVN87%252Fimage%2520%2843%29.png%3Falt%3Dmedia%26token%3D11ff1b0d-f5ad-4a6d-b589-6316bc0f79b2&width=768&dpr=3&quality=100&sign=cf9e1cf6&sv=2) #### [hashtag](https://docs.hivel.ai/integrations/scm/gitlab/how-to-ensure-gitlab-token-has-access-to-required-groups-repositories#open-the-groups-members-settings) **Open the Group’s Members Settings** 1. In the Group Dashboard, go to the left sidebar. 2. Click **"Settings"** → **"Members"**. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fdh8rUvMjdaVmLeCfacjy%252Fimage%2520%2844%29.png%3Falt%3Dmedia%26token%3D347bde98-47d3-47bc-acd2-99ee06b78f36&width=768&dpr=3&quality=100&sign=3b717155&sv=2) #### [hashtag](https://docs.hivel.ai/integrations/scm/gitlab/how-to-ensure-gitlab-token-has-access-to-required-groups-repositories#invite-the-service-account) **Invite the Service Account** 1. Click **"Invite Member"** (top right corner). 2. In the **"Select members or email address"** field, enter the service account username or email. 3. Assign a "Reporter" or "Developer" role as required. 4. Click **"Invite"**. Repeat the steps for all required groups. Once added, the service account will inherit access to all repositories within the groups. [PreviousGitlab Cloudchevron-left](https://docs.hivel.ai/integrations/scm/gitlab/gitlab-cloud) [NextBitBucketchevron-right](https://docs.hivel.ai/integrations/scm/bitbucket) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # PR, Issues & Workflow FAQs | Hivel [Why do some Jira issues show as spillover in Hivel even though they were completed in Jira?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-do-some-jira-issues-show-as-spillover-in-hivel-even-though-they-were-completed-in-jira) [How do I exclude a PR from rework/maintenance/new work calculation?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/how-do-i-exclude-a-pr-from-rework-maintenance-new-work-calculation) [Why Product and Allocation's previous data is not reflecting?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-product-and-allocations-previous-data-is-not-reflecting) [Why don't I see delivery accuracy for Kanban boards?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-dont-i-see-delivery-accuracy-for-kanban-boards) [Why some of the repositories are not imported or synced?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-some-of-the-repositories-are-not-imported-or-synced) [How can I add a template in dashboards for my org to follow?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/how-can-i-add-a-template-in-dashboards-for-my-org-to-follow) [PreviousWhy do I see "No existing user found" message while loginchevron-left](https://docs.hivel.ai/faqs/team-and-user-management-faqs/why-do-i-see-no-existing-user-found-message-while-login) [NextWhy do some Jira issues show as spillover in Hivel even though they were completed in Jira?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-do-some-jira-issues-show-as-spillover-in-hivel-even-though-they-were-completed-in-jira) sun-brightdesktopmoon sun-brightdesktopmoon --- # Microsoft Outlook | Hivel Integrating Outlook with Hivel involves a few key steps to ensure that all necessary calendars are accessible and synced properly. Below is a step-by-step guide to help you through the process: #### [hashtag](https://docs.hivel.ai/integrations/calendar/microsoft-outlook#use-an-outlook-account-with-admin-access) Use an Outlook account with Admin access circle-info **Use an Admin account which has at least "View" access to all the applicable developer's Outlook accounts.** #### [hashtag](https://docs.hivel.ai/integrations/calendar/microsoft-outlook#integrate-outlook-with-hivel) Integrate Outlook with Hivel 1\. Log into Hivel using the admin account. 2\. Navigate to the Settings -> Integrations section from the dashboard. 3\. Find Outlook in the list of available integrations and click on Connect. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FxEtHpAR0CE7yaZBznarW%252Fimage.png%3Falt%3Dmedia%26token%3D9077b40c-1080-4799-992f-3a077e38da43&width=768&dpr=3&quality=100&sign=557da313&sv=2) Follow the on-screen prompts to allow permissions for Hivel to access your Outlook data. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FpIlvpQcqXOpu9r8JrEq0%252Fimage.png%3Falt%3Dmedia%26token%3D6b0859ab-1a45-44bd-9ae1-b6d81e7b1bc4&width=768&dpr=3&quality=100&sign=639cc8ce&sv=2) This should help you seamlessly integrate Outlook with Hivel, allowing you to understand the schedule of your team effectively within the platform. #### [hashtag](https://docs.hivel.ai/integrations/calendar/microsoft-outlook#data-collected-from-calendars) Data Collected from Calendars Once authorization is complete, Hivel will read calendar data for all users under the admin account. The specific data points fetched from each calendar include: * **id:** Unique identifier of the calendar event. * **iCalUId:** Unique identifier for the event across calendar clients. * **start:** Start time of the event. * **end:** End time of the event. * **isCancelled:** Indicates if the event has been canceled. * **organizer:** The person who created or owns the event. * **attendees:** List of participants invited to the event. #### [hashtag](https://docs.hivel.ai/integrations/calendar/microsoft-outlook#sync-frequency) Sync Frequency * **Initial Sync:** Fetches calendar data for the past 90 days. * **Incremental Sync:** Nightly updates to fetch events for the past 1 day. For further assistance or any issues encountered during the integration, please contact our support team at [\[email protected\].envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#c1b2b4b1b1aeb3b581a9a8b7a4adefa0a8ef) [PreviousHow to integrate Google Calendar in Hivelchevron-left](https://docs.hivel.ai/integrations/calendar/google-calendar/how-to-integrate-google-calendar-in-hivel) [NextCI/CDchevron-right](https://docs.hivel.ai/integrations/ci-cd) Last updated 9 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # What happens if there are too many Flashy Reviews and how to prevent them? | Hivel circle-info A Pull Request larger than 200 Lines of Code merged with less than 5 minutes is considered as a Flashy Review PR. This is [configurablearrow-up-right](https://hivel.gitbook.io/knowlegebase/setup/configurations-explained/branch-configurations#flashy-review) in the Settings screen. To filter out on the PRs with Flashy Reviews, simply apply the filter in Pull Request screen. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDmdcMW4RYWA2SK6MKRHt%252Fimage.png%3Falt%3Dmedia%26token%3D59cf1263-892a-432f-8044-61821b16c757&width=768&dpr=3&quality=100&sign=fdf44afc&sv=2) ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-happens-if-there-are-too-many-flashy-reviews-and-how-to-prevent-them#when-there-are-too-many-flashy-reviews-some-issues-that-can-potentially-arise-are) When there are too many flashy reviews, some issues that can potentially arise are * **Reduced Code Quality**: Quick approvals of large PRs may lead to overlooked bugs and security issues due to insufficient review. * **Increased Technical Debt**: Quick reviews can result in code that doesn’t meet best practices or project standards, increasing maintenance challenges. * **Decreased Team Accountability**: Minimal scrutiny of PRs can promote a culture where developers expect fast approvals, reducing overall discipline and accountability. * **Knowledge Silos**: Quick approvals might limit the opportunity for team members to fully understand the changes, creating knowledge gaps within the team. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-happens-if-there-are-too-many-flashy-reviews-and-how-to-prevent-them#to-prevent-an-excess-of-flashy-review-prs-and-encourage-more-thorough-code-reviews-consider-the-foll) To prevent an excess of Flashy Review PRs and encourage more thorough code reviews, consider the following strategies * **Limit Size of PRs:** Encourage developers to keep PRs manageable by limiting the number of lines of code or changes included. Smaller, more focused PRs are easier to review thoroughly than large batches of changes. * **Set Clear Review Policies:** Establish and enforce a policy that requires sufficient time for code review, especially for larger PRs. This policy could include specific time frames based on the size of the PR. * **Use Code Review Checklists:** Develop checklists that reviewers can use to guide their review process, ensuring they cover all necessary aspects of the code. * **Mandatory Reviewer Assignments:** Require that PRs be reviewed by at least one senior developer. Assign reviews based on the areas of the codebase affected to ensure knowledgeable feedback. [PreviousWhat to do if my Rework is high?chevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high) [NextBest Practices for Ensuring Strong Pull Request Review Coveragechevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage) Last updated 1 year ago * [When there are too many flashy reviews, some issues that can potentially arise are](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-happens-if-there-are-too-many-flashy-reviews-and-how-to-prevent-them#when-there-are-too-many-flashy-reviews-some-issues-that-can-potentially-arise-are) * [To prevent an excess of Flashy Review PRs and encourage more thorough code reviews, consider the following strategies](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-happens-if-there-are-too-many-flashy-reviews-and-how-to-prevent-them#to-prevent-an-excess-of-flashy-review-prs-and-encourage-more-thorough-code-reviews-consider-the-foll) sun-brightdesktopmoon sun-brightdesktopmoon --- # Why Product and Allocation's previous data is not reflecting? | Hivel After configuring the [**Product** and **Allocation**arrow-up-right](https://hivel.gitbook.io/knowlegebase/using-hivel/investment/how-to-set-up-products-and-allocation-tabs-in-the-investment-screen) fields in Hivel: * **Ongoing and Incremental Issues**: The data starts reflecting automatically for new and ongoing issues. * **Previous Issues**: Historical data does not appear automatically and requires a manual backend process to sync. If you have historical data for the **Product** and **Allocation** fields and need it to reflect in Hivel: 1. Reach out to us at [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#c3b0b6b3b3acb1b783abaab5a6afeda2aa) . 2. We will manually run the backend process to sync the data. 3. The updated data will be available in Hivel within 24 hours. [PreviousHow do I exclude a PR from rework/maintenance/new work calculation?chevron-left](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/how-do-i-exclude-a-pr-from-rework-maintenance-new-work-calculation) [NextWhy don't I see delivery accuracy for Kanban boards?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-dont-i-see-delivery-accuracy-for-kanban-boards) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Reporting & Goal Tracking FAQs | Hivel [How can I see the progress against my goals?chevron-right](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/how-can-i-see-the-progress-against-my-goals) [How to measure impact of Copilots using Hivel?chevron-right](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/how-to-measure-impact-of-copilots-using-hivel) [Easing into Kanban: How to set your team up for successchevron-right](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success) [PreviousWhy does the filters change when I move to dashboards but in other screen it remains same?chevron-left](https://docs.hivel.ai/faqs/system-behavior-and-limitations-faqs/why-does-the-filters-change-when-i-move-to-dashboards-but-in-other-screen-it-remains-same) [NextHow can I see the progress against my goals?chevron-right](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/how-can-i-see-the-progress-against-my-goals) sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Notes - December 2024 | Hivel As the year wraps up, we’ve kept things steady this December. With the holidays in full swing, we’ve been focusing on smooth operations and making sure everything stays stable while we recharge for 2025. No major updates this month, but behind the scenes, we're ensuring your experience is as seamless and efficient as ever. **Time to enjoy the winter, sip some cocoa, and pretend to be productive!** 😎☕✨ [PreviousRelease Notes - January 2025chevron-left](https://docs.hivel.ai/release-notes/release-notes-january-2025) [NextRelease Notes - November 2024chevron-right](https://docs.hivel.ai/release-notes/release-notes-november-2024) Last updated 11 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # AI Tools | Hivel [Github Copilot Integrationchevron-right](https://docs.hivel.ai/integrations/ai-tools/github-copilot-integration) [Github Copilot - Enterprisechevron-right](https://docs.hivel.ai/integrations/ai-tools/github-copilot-enterprise) [GitHub Copilot Reauthorizationchevron-right](https://docs.hivel.ai/integrations/ai-tools/github-copilot-reauthorization) [Cursor Integrationchevron-right](https://docs.hivel.ai/integrations/ai-tools/cursor-integration) [Claude Codechevron-right](https://docs.hivel.ai/integrations/ai-tools/claude-code) [Setting up your own key for AI featureschevron-right](https://docs.hivel.ai/integrations/ai-tools/setting-up-your-own-key-for-ai-features) [PreviousClickUpchevron-left](https://docs.hivel.ai/integrations/project-management/clickup) [NextGithub Copilot Integrationchevron-right](https://docs.hivel.ai/integrations/ai-tools/github-copilot-integration) sun-brightdesktopmoon sun-brightdesktopmoon --- # BitBucket Integration | Hivel **What data does Hivel require access to?** Hivel securely accesses the last 60-90 days of commits and pull requests from active repositories. **Authorization Control** We utilize Bitbucket's OAuth for secure login. You retain full control and can revoke access at any time via Bitbucket's authorized apps settings. **Pre-requisites** A service account with _write_ access to all applicable Bitbucket repositories.Write access is essential for publishing webhooks, enabling real-time data synchronization. **Sign in to Hivel** 1. Navigate to the Hivel [sign-up pagearrow-up-right](https://app.hivel.ai/signup) 2. Add your work email id (If you'd like to use your personal email id please contact [\[email protected\])envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#ef9c9a9f9f809d9baf8786998a83c18e86c6) 3. Now, you can use your Google or Microsoft login with your work email id; or create a password. 4. Create your Company Profile, and click '**Get Started**'. 5. Once you've successfully created your Company Profile you will be redirected to the Integrations Page. 6. Select Bitbucket, and log in to your company's Bitbucket account using a service account. 7. Authorize Hivel on the ensuing Bitbucket redirect. 8. Click "Grant" for desired workspaces. 9. After authorization, you'll be redirected back to Hivel. 10. Once your Bitbucket is successfully integrated, we will start to pull data. It will take between 2 - 48 hours for the complete sync, depending on the volume of the data. #### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/bitbucket-integration#below-are-step-by-step-screenshots-of-instructions-you-can-refer-to-if-needed) Below are step-by-step screenshots of instructions you can refer to if needed: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FEgtVdyFeQ6ZOHMXUsUdX%252Fimage.png%3Falt%3Dmedia%26token%3D99e16bfc-989c-4161-99ae-1b351832b329&width=768&dpr=3&quality=100&sign=d43d387&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F9Al1RETLnRQZ4jI3yVlL%252Fimage%2520%2820%29.png%3Falt%3Dmedia%26token%3D6497821d-9343-48c0-9151-01eb6a9ccb06&width=768&dpr=3&quality=100&sign=f1c39fb7&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FdejuQx5xvnK79sqk8SYq%252Fimage%2520%2821%29.png%3Falt%3Dmedia%26token%3D50e0fdff-46ea-40d1-ba37-f2869e69131b&width=768&dpr=3&quality=100&sign=d3da3fb2&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FSpAhrIsXJv5LVvY62qcG%252Fimage.png%3Falt%3Dmedia%26token%3D463bd30b-e084-41c2-b36d-31783fbd483e&width=768&dpr=3&quality=100&sign=f80ff10d&sv=2) [PreviousBitBucketchevron-left](https://docs.hivel.ai/integrations/scm/bitbucket) [NextValidation at a metric level for BitBucketchevron-right](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to Re-authorize Jira with OAuth 2.0 | Hivel **Here's a quick guide on how to re-authorize your Jira integration with Hivel:** 1. Log in to your Hivel account. 2. In the left panel, select **Settings** and go to the **Integrations** tab. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FiXFAYVLwayDew5VTMBGW%252Fimage%2520%281%29.png%3Falt%3Dmedia%26token%3D26529b0f-d7e0-42d6-8665-9908182bd399&width=768&dpr=3&quality=100&sign=30e65c92&sv=2) 1. Find the Jira card and click the **'Reauthorize'** button. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F4GzFFMG8W9IDWb68SJYv%252Fimage%2520%282%29.png%3Falt%3Dmedia%26token%3D322fe9a2-74a9-4502-b810-10e043953068&width=768&dpr=3&quality=100&sign=a467e55c&sv=2) 1. Click on Accept ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FAbZywrtFogVq8kxz5uuC%252Fimage%2520%283%29.png%3Falt%3Dmedia%26token%3Db7797dba-8a1d-4ad5-9035-efd9bed54fac&width=768&dpr=3&quality=100&sign=e15271de&sv=2) **Once reauthorized, we’ll automatically resume fetching your latest Jira data.** [PreviousHow to Integrate Jira with OAuth 2.0chevron-left](https://docs.hivel.ai/integrations/project-management/jira/how-to-integrate-jira-with-oauth-2.0) [NextHow to integrate Jira Server with Hivelchevron-right](https://docs.hivel.ai/integrations/project-management/jira/how-to-integrate-jira-server-with-hivel) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Azure DevOps | Hivel **Data Access by Hivel** * Hivel accesses the past 60-90 days of commits and pull requests from active repositories during the initial sync. **Authorization Mechanism** * Hivel gets access using a Personal Access Token, which can be created using this [linkarrow-up-right](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows#create-a-pat) . * Users maintain full control and can withdraw access anytime by revoking the Personal Access Token. * Ensure '**All accessible organizations'** is selected while creating the Personal Access Token. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FWQ23CAsvj8bRFQTgfyw0%252Fimage.png%3Falt%3Dmedia%26token%3Dc576014f-0e52-4f44-b6d0-48350b76afb0&width=300&dpr=3&quality=100&sign=eb68633c&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDI3qRLMqzJogW2VKSQ51%252Fimage.png%3Falt%3Dmedia%26token%3Daa7a48e4-3c2d-4c53-8b9f-23c237d98c46&width=300&dpr=3&quality=100&sign=48e1c3c0&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F6QVTdt5mgSnX6FhKspRJ%252Fimage.png%3Falt%3Dmedia%26token%3D5a55fa48-b093-40a4-84b5-03713683899d&width=300&dpr=3&quality=100&sign=9d105af3&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F0vccKgvrZradW7UZ5FWB%252Fimage.png%3Falt%3Dmedia%26token%3Db930bc69-052a-4717-af63-c44e321cc522&width=768&dpr=3&quality=100&sign=f376b9b0&sv=2) **Requirements** * Ensure to create the Personal Access Token from an account that has "Project Administrator" permissions for all relevant projects and repositories. **Best Practice** * Opt for a service account rather than an individual-linked account. * Service accounts are typically overseen by the company's admin. **Personal Access Token Permissions** * Please ensure you select all the options below while creating a Personal Access Token. * **Project And Team**: Read * **User Profile**: Read * **Code**: Read * **Build**: Read * **Graph:** Read * **Work Items:** Read ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fbvzlj9oxA4zEMkKSLa6S%252Fimage.png%3Falt%3Dmedia%26token%3D6dfe77b0-8342-4692-be62-801df0224749&width=300&dpr=3&quality=100&sign=57fef77b&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F05fLXq4XnHbDXgIB9rEN%252Fimage.png%3Falt%3Dmedia%26token%3D1550c531-0a79-46cb-86bb-366b6ff12041&width=300&dpr=3&quality=100&sign=7e061d34&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FC1tDnhhlCe2nBzUwHPCF%252Fimage.png%3Falt%3Dmedia%26token%3D75885a07-7f18-4598-8134-7d35b19bcf17&width=300&dpr=3&quality=100&sign=ffd76eea&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FPIqxw6g5fSl2dAtCLNoy%252Fimage.png%3Falt%3Dmedia%26token%3D86a43ff4-44b4-4d0d-ba6c-2b9ee2febcb9&width=300&dpr=3&quality=100&sign=11a1ebbe&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FRkS5YqtDTaONUGEIiCy1%252Fimage.png%3Falt%3Dmedia%26token%3Da17f527d-4bca-4a02-86fe-2db9244191e9&width=300&dpr=3&quality=100&sign=28352300&sv=2) **You are almost done.** * Once a Personal Access Token is created, please copy it and share it with the Hivel team. * You will receive an email from the Hivel team once your data is all up and running. [PreviousAzurechevron-left](https://docs.hivel.ai/integrations/scm/azure) [NextAzure GIT Serverchevron-right](https://docs.hivel.ai/integrations/scm/azure/azure-git-server) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to identify root cases of high change failure rates? | Hivel Identifying root causes of high change failure rates is crucial for improving the stability and reliability of software deployments. Here are effective strategies for determining the underlying issues that contribute to a high rate of change failures: 1. **Conduct thorough postmortems for each failure** * After every failure, organize a detailed review or postmortem that includes everyone involved in the deployment process. Analyze what went wrong and document the findings. The goal is to identify patterns or repeated mistakes that lead to failures. 2. **Use monitoring and logging data effectively** * Leverage logs and monitoring tools to trace back the failures to their origin. Look for anomalies in logs immediately before a failure occurred. This can provide clues about system behavior and help pinpoint the problematic changes. 3. **Implement a blameless culture** * Foster an environment where team members feel safe to report and discuss errors. A blameless culture encourages openness and can lead to more accurate identification of root causes without fear of retribution or criticism. 4. **Enhance testing and quality assurance practices** * Evaluate current testing methodologies to ensure they are robust enough to catch errors before deployment. This might include increasing code coverage with automated tests, integrating static code analysis tools, and conducting more rigorous peer reviews. 5. **Review and refine deployment practices** * Assess the deployment processes to identify any steps that may contribute to failures. This can involve reviewing the staging environment, deployment scripts, and rollback procedures to ensure they match the production environment as closely as possible. 6. **Analyze configuration management** * Misconfigurations can often lead to deployment failures. Ensure that all environment configurations are managed properly with automation tools to avoid human errors and inconsistencies between environments. 7. **Investigate external dependencies** * External services and libraries can also be sources of change failures. Verify that all external dependencies are stable, well-documented, and tested within the application context before they are integrated into the production environment. 8. **Conduct regular skill and process training** * Regular training sessions for the development and operations teams can help update and sharpen their skills in coding, testing, and deploying. This helps reduce errors due to outdated practices or lack of knowledge. 9. **Seek feedback from all stakeholders** * Regularly solicit feedback from developers, testers, operations staff, and even end-users to gather different perspectives on what might be causing the failures. This comprehensive feedback can provide a broader view of the issues at hand. By systematically applying these strategies, teams can more effectively identify the root causes of high change failure rates and take corrective action to improve their deployment processes and reduce the likelihood of future failures. [PreviousBest Practices for Team Ownership in Code Reviewchevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review) [NextBuilding a feedback loop for continuous code improvementchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/building-a-feedback-loop-for-continuous-code-improvement) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Okta SSO | Hivel To integrate Okta with Hivel, follow these steps: ### [hashtag](https://docs.hivel.ai/integrations/okta-sso#id-1.-create-an-application-in-okta) 1\. Create an Application in Okta Follow these steps to set up an Okta application for Hivel authentication: 1. **Log in** to your Okta Admin Console. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FanAaNDtes7RnlYfkw6zl%252FScreenshot%25202025-02-28%2520at%25207.14.58%25E2%2580%25AFPM%2520%281%29.png%3Falt%3Dmedia%26token%3Db7632eb2-7bf5-4818-a34a-3d266971fd3a&width=768&dpr=3&quality=100&sign=85570f76&sv=2) 1. Navigate to **Applications** → Click **Create App Integration**. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FhrNf2HhLcOJ6gtvCgeNM%252FScreenshot%25202025-02-28%2520at%25207.15.44%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D028ac564-d33b-4611-b560-7a5dca537167&width=768&dpr=3&quality=100&sign=cf1d63ce&sv=2) 1. Select the **Sign-in method**: `OIDC - OpenID Connect`. 2. Choose **Application Type**: `Web`. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FRmfehVF9EuUUoqli7UFo%252FScreenshot%25202025-02-28%2520at%25207.16.20%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D619a556b-e92c-43eb-b78e-64c8a77cbf13&width=768&dpr=3&quality=100&sign=eef36078&sv=2) 1. Enter the **Redirect URI**: 1. Under **Assignments access**, configure permissions based on your organization's requirements. 2. Add the required users to the Okta application to grant them access to Hivel. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FySxghUvU5ocpMhxrhMaN%252FScreenshot%25202025-02-28%2520at%25207.18.26%25E2%2580%25AFPM%2520%282%29.png%3Falt%3Dmedia%26token%3Dc0f75871-aaed-438f-a7a7-6990cc09a03a&width=768&dpr=3&quality=100&sign=8e02ba96&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FmIxPvsaMBvasBbLdEcqJ%252FScreenshot%25202025-02-28%2520at%25207.19.26%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D38818db1-fb35-4f75-b7ea-099ce1eea447&width=768&dpr=3&quality=100&sign=6c672364&sv=2) 1. Click **Save** to generate a `Client ID` and `Client Secret`. ### [hashtag](https://docs.hivel.ai/integrations/okta-sso#id-2.-fill-the-following-details-on-hivel-ui) 2\. Fill the following details on Hivel UI After creating the application, fill the input fields on integration page on Hivel UI. Here is how: * **Log into Hivel -> Go to Settings -> Integrations -> SSO -> Okta** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FISzDLo8VgtjJ0LG7zupc%252Fimage.png%3Falt%3Dmedia%26token%3D9842c2c5-fe26-4b06-9404-40cbb234a116&width=768&dpr=3&quality=100&sign=1fa013e9&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FMB0MrV6tN9gwXo3TZdnU%252FGemini%2520Generated%2520Image%2520%282%29.png%3Falt%3Dmedia%26token%3Dfed23c37-f849-40cf-8bb9-ba17bf1b9694&width=768&dpr=3&quality=100&sign=a8af1642&sv=2) #### [hashtag](https://docs.hivel.ai/integrations/okta-sso#fill-the-following-details-on-the-popup) **Fill the following details on the popup:** * **OKTA Domain URL** – Your Okta instance URL, e.g., `https://yourcompany.okta.com`. * **OKTA API URL** - We prepopulate based on your domain URL, but it can be changed in case that is not the correct API URL. * **Client ID** – The client identifier from your Okta application. * **Client Secret** – The client secret associated with the client ID. Click on "Integrate OKTA" once done. These details will enable a seamless authentication flow between Okta and Hivel. If you have any questions or need assistance, feel free to reach out. [PreviousJenkins Freestyle Integration with Ansible and Hivel Webhookchevron-left](https://docs.hivel.ai/integrations/ci-cd/jenkins-freestyle-integration-with-ansible-and-hivel-webhook) [NextAzure AD SSOchevron-right](https://docs.hivel.ai/integrations/azure-ad-sso) Last updated 6 months ago * [1\. Create an Application in Okta](https://docs.hivel.ai/integrations/okta-sso#id-1.-create-an-application-in-okta) * [2\. Fill the following details on Hivel UI](https://docs.hivel.ai/integrations/okta-sso#id-2.-fill-the-following-details-on-hivel-ui) sun-brightdesktopmoon Copy https://app.hivel.ai sun-brightdesktopmoon --- # GitHub | Hivel ### [hashtag](https://docs.hivel.ai/integrations/scm/github#integration-with-account-wide-access) Integration with account-wide access [How to integrate GitHub with account wide access?chevron-right](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-account-wide-access) [How to re-authorize / re-initiate GitHub integration with account wide access?chevron-right](https://docs.hivel.ai/integrations/scm/github/how-to-re-authorize-re-initiate-github-integration-with-account-wide-access) ### [hashtag](https://docs.hivel.ai/integrations/scm/github#integration-with-repository-level-access) Integration with repository-level access [How to integrate GitHub with repository level access?chevron-right](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-repository-level-access) [How to re-authorize / re-initiate GitHub integration with repository level access?chevron-right](https://docs.hivel.ai/integrations/scm/github/how-to-re-authorize-re-initiate-github-integration-with-repository-level-access) #### [hashtag](https://docs.hivel.ai/integrations/scm/github#alternate-methods) Alternate methods [](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-integrate-github-with-classic-token) Integrate with Classic Token [](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-create-github-fine-grained-token-for-hivel-integration) Integrate with Fine-Grained Token [](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-reauthorize-github-with-a-classic-token) Reauthorize with Classic Token [PreviousSCMchevron-left](https://docs.hivel.ai/integrations/scm) [NextHow to integrate GitHub with account wide access?chevron-right](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-account-wide-access) Last updated 6 months ago * [Integration with account-wide access](https://docs.hivel.ai/integrations/scm/github#integration-with-account-wide-access) * [Integration with repository-level access](https://docs.hivel.ai/integrations/scm/github#integration-with-repository-level-access) sun-brightdesktopmoon sun-brightdesktopmoon --- # Setting up your own key for AI features | Hivel Model required: Model: 4 Sonnet | 4.5 Sonnet | 4.6 Sonnet Minimum Thinking budget: 3000|5000|5000 {Respectively for the models} Max Thinking Budget: 5000| 10,000| 10,000 {Respectively for the models} Steps to create the Claude API key: 1. Navigate to the "API Keys" section in your account dashboard or settings. 2. Click the "+Create Key" button. 3. Give your API key a descriptive name (e.g., "My\_First\_Claude\_App") and click "Create". 4. Immediately copy the generated key and store it in a secure location (like a password manager). For security reasons, the key will not be shown again after you leave this page. [Code Telemetry FAQschevron-right](https://docs.hivel.ai/ai-adoption/hivel-ai-impact-screen-overview-and-insights/code-telemetry-faqs) [PreviousClaude Codechevron-left](https://docs.hivel.ai/integrations/ai-tools/claude-code) [NextCalendarchevron-right](https://docs.hivel.ai/integrations/calendar) Last updated 13 days ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Cursor Integration | Hivel 1. Log in to your Hivel account. 2. In the left panel, select **Settings**, and go to the **Integrations** tab. 3. Find the **Cursor** card and click the **'Connect'** button. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fp0PKUhkO03FJwKfaRyRu%252Fimage.png%3Falt%3Dmedia%26token%3D3e099446-eff4-4faa-9939-5ee7d55ad5b6&width=768&dpr=3&quality=100&sign=94125269&sv=2) Click on the connect button 1. In the pop-up, paste the Cursor API ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDwaq0bbWJlhNcuZuTxHD%252Fimage.png%3Falt%3Dmedia%26token%3D78f0aaa3-402a-46fd-9ec8-30a7cc8e779a&width=768&dpr=3&quality=100&sign=e7584cfa&sv=2) Paste the Cursor API key and click Submit 1. To get the above Cursor API key use the following steps or refer to [https://docs.cursor.com/account/teams/admin-apiarrow-up-right](https://docs.cursor.com/account/teams/admin-api) : ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FvTaBdTdr2JAIKOKLgKwt%252FScreenshot%25202025-07-01%2520at%25203.47.45%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3De6e08db8-715c-433e-844f-6a2e2de5c4c3&width=768&dpr=3&quality=100&sign=74e9ece4&sv=2) [PreviousGitHub Copilot Reauthorizationchevron-left](https://docs.hivel.ai/integrations/ai-tools/github-copilot-reauthorization) [NextClaude Codechevron-right](https://docs.hivel.ai/integrations/ai-tools/claude-code) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to improve Quality | Hivel [What to do if my Rework is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high) [What happens if there are too many Flashy Reviews and how to prevent them?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-happens-if-there-are-too-many-flashy-reviews-and-how-to-prevent-them) [Best Practices for Ensuring Strong Pull Request Review Coveragechevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage) [Strategies to Reduce Hotfix Resolution Timechevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time) [Best Practices for Team Ownership in Code Reviewchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review) [How to identify root cases of high change failure rates?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/how-to-identify-root-cases-of-high-change-failure-rates) [Building a feedback loop for continuous code improvementchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/building-a-feedback-loop-for-continuous-code-improvement) [PreviousWhat to do if my Merge Time is high?chevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-merge-time-is-high) [NextWhat to do if my Rework is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high) sun-brightdesktopmoon sun-brightdesktopmoon --- # Building a feedback loop for continuous code improvement | Hivel Building a feedback loop for continuous code improvement is essential for fostering a culture of learning and innovation in software development teams. Here’s how you can create an effective feedback loop that promotes ongoing code quality and improvement: 1. **Integrate code reviews into development workflow** * Implement mandatory code reviews using platforms like GitHub, GitLab, or Bitbucket, ensuring issues are caught early and fostering knowledge sharing across the team. 2. **Automate code quality checks** * Utilize static analysis tools such as SonarQube, ESLint, and StyleCop to automatically review code for errors and technical debt, maintaining high quality standards while allowing reviewers to focus on complex issues. 3. **Implement pair programming** * Schedule regular pair programming sessions where two developers collaborate in real-time, enhancing code quality and team collaboration simultaneously. 4. **Use metrics to track progress** * Analyze metrics related to code quality, like bug rates and technical debt, using integrated tools to quantitatively measure and visualize improvement over time. 5. **Conduct regular refactoring sessions** * Dedicate time during development cycles specifically for refactoring, ensuring the codebase remains clean and maintainable, which minimizes long-term technical debt. 6. **Hold retrospective meetings** * Conduct retrospective meetings after each development cycle to discuss successes and areas for improvement, embedding a proactive approach to enhancing code quality and team processes. 7. **Encourage training and continuous learning** * Provide opportunities for developers to attend workshops and training sessions, keeping the team updated with the latest coding techniques and industry standards, which they can apply to their work. 8. **Implement feedback tools within the application** * Utilize feature flags, A/B testing tools, and monitor application logs to gather direct user feedback and performance data, guiding developers on where improvements are most needed. 9. **Promote a culture of open communication** * Foster an environment where feedback is welcomed and viewed as essential for personal and professional growth, improving code quality through collaborative problem-solving and shared ownership. 10. **Create a knowledge sharing platform** * Develop a central repository or wiki for sharing insights, best practices, and lessons learned, preventing repeated mistakes and promoting best practices across all projects. By establishing these practices, your team can create a robust feedback loop that not only improves code quality but also supports the ongoing development and growth of your team members. This loop fosters an environment where continuous improvement is part of the everyday process, leading to better software products and a more engaged team. [PreviousHow to identify root cases of high change failure rates?chevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-quality/how-to-identify-root-cases-of-high-change-failure-rates) [NextHow to improve planning and throughputchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-planning-and-throughput) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to Integrate Jira with OAuth 2.0 | Hivel **Here's a quick guide on how to re-authorize your Jira integration with Hivel:** 1. Log in to your Hivel account. 2. In the left panel, select **Settings** and go to the **Integrations** tab. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FiXFAYVLwayDew5VTMBGW%252Fimage%2520%281%29.png%3Falt%3Dmedia%26token%3D26529b0f-d7e0-42d6-8665-9908182bd399&width=768&dpr=3&quality=100&sign=30e65c92&sv=2) 1. Find the Jira card and click the **'Connect'** button. 2. Click on Accept ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FAbZywrtFogVq8kxz5uuC%252Fimage%2520%283%29.png%3Falt%3Dmedia%26token%3Db7797dba-8a1d-4ad5-9035-efd9bed54fac&width=768&dpr=3&quality=100&sign=e15271de&sv=2) **5\. Once connected, we’ll automatically start fetching your latest data.** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FW7YthWVhXYn77IeLeGrr%252Fimage.png%3Falt%3Dmedia%26token%3D1c2b700f-c43d-49b3-bfb8-8b3fa66f4e30&width=768&dpr=3&quality=100&sign=592d77d2&sv=2) 1. The next step is to **create a webhook** for ongoing data, and for that 2. Open a new tab and log in to your Jira application using the same admin credentials 3. Top Right corner-> **Settings** -> **System** 4. On the Left panel -> **Webhooks** 5. Top Right -> **Create webhook** 6. Now use the below details in the form: 1. **Name:** Hivel 2. **URL**\- [https://app.hivel.ai/jiraapi/webhook/processarrow-up-right](https://app.insightly.ai/jiraapi/webhook/process) ​ 3. **Events:** 1. _Issue-related events_ 1. **JQL: All issues** 2. **Issue** (select checkboxes) : created, updated, deleted 2. _User-related events_ 1. **User** (select checkboxes) : created, deleted, updated 3. _Jira Software-related events_ 1. **Sprint** (select checkboxes)**:** deleted, updated, started, closed 7. Ensure the Name, URL, and events are all checked. Click on **Create.** Done! The data will be refreshed within 24 hours. [PreviousJirachevron-left](https://docs.hivel.ai/integrations/project-management/jira) [NextHow to Re-authorize Jira with OAuth 2.0chevron-right](https://docs.hivel.ai/integrations/project-management/jira/how-to-re-authorize-jira-with-oauth-2.0) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Azure GIT Server | Hivel #### [hashtag](https://docs.hivel.ai/integrations/scm/azure/azure-git-server#data-access-by-hivel) Data Access by Hivel * Hivel accesses the past 60-90 days of commits and pull requests from active repositories during the initial sync. #### [hashtag](https://docs.hivel.ai/integrations/scm/azure/azure-git-server#h_01j3f1mcmbfjzaqwgecz0qnyxy) Whitelist Necessary IP Addresses For a secure and uninterrupted connection, make sure to whitelist the following IP addresses: * **Mandatory IPs**: * 107.23.139.76 * 3.219.89.23 * **Recommended, but Optional IPs**: * 45.119.114.218 * 183.82.116.218 #### [hashtag](https://docs.hivel.ai/integrations/scm/azure/azure-git-server#authorization-mechanism) Authorization Mechanism * Hivel gets access using a Personal Access Token, which can be created using this [linkarrow-up-right](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows#create-a-pat) . * Users maintain full control and can withdraw access anytime by revoking the Personal Access Token. * Ensure '**All accessible organizations'** is selected while creating the Personal Access Token. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FWQ23CAsvj8bRFQTgfyw0%252Fimage.png%3Falt%3Dmedia%26token%3Dc576014f-0e52-4f44-b6d0-48350b76afb0&width=300&dpr=3&quality=100&sign=eb68633c&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDI3qRLMqzJogW2VKSQ51%252Fimage.png%3Falt%3Dmedia%26token%3Daa7a48e4-3c2d-4c53-8b9f-23c237d98c46&width=300&dpr=3&quality=100&sign=48e1c3c0&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F6QVTdt5mgSnX6FhKspRJ%252Fimage.png%3Falt%3Dmedia%26token%3D5a55fa48-b093-40a4-84b5-03713683899d&width=300&dpr=3&quality=100&sign=9d105af3&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F0vccKgvrZradW7UZ5FWB%252Fimage.png%3Falt%3Dmedia%26token%3Db930bc69-052a-4717-af63-c44e321cc522&width=768&dpr=3&quality=100&sign=f376b9b0&sv=2) **Requirements** * Ensure to create the Personal Access Token from an account that has "Project Administrator" permissions for all relevant projects and repositories. **Best Practice** * Opt for a service account rather than an individual-linked account. * Service accounts are typically overseen by the company's admin. **Personal Access Token Permissions** * Please ensure you select all the options below while creating a Personal Access Token. * **Project And Team**: Read * **User Profile**: Read * **Code**: Read * **Build**: Read * **Graph:** Read * **Work Items:** Read ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fbvzlj9oxA4zEMkKSLa6S%252Fimage.png%3Falt%3Dmedia%26token%3D6dfe77b0-8342-4692-be62-801df0224749&width=300&dpr=3&quality=100&sign=57fef77b&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F05fLXq4XnHbDXgIB9rEN%252Fimage.png%3Falt%3Dmedia%26token%3D1550c531-0a79-46cb-86bb-366b6ff12041&width=300&dpr=3&quality=100&sign=7e061d34&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FC1tDnhhlCe2nBzUwHPCF%252Fimage.png%3Falt%3Dmedia%26token%3D75885a07-7f18-4598-8134-7d35b19bcf17&width=300&dpr=3&quality=100&sign=ffd76eea&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FPIqxw6g5fSl2dAtCLNoy%252Fimage.png%3Falt%3Dmedia%26token%3D86a43ff4-44b4-4d0d-ba6c-2b9ee2febcb9&width=300&dpr=3&quality=100&sign=11a1ebbe&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FRkS5YqtDTaONUGEIiCy1%252Fimage.png%3Falt%3Dmedia%26token%3Da17f527d-4bca-4a02-86fe-2db9244191e9&width=300&dpr=3&quality=100&sign=28352300&sv=2) **You are almost done.** * Once a Personal Access Token is created, please copy it and share it with the Hivel team. * You will receive an email from the Hivel team once your data is all up and running. [PreviousAzure DevOpschevron-left](https://docs.hivel.ai/integrations/scm/azure/azure-devops) [NextProject Managementchevron-right](https://docs.hivel.ai/integrations/project-management) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Notes - July 2025 | Hivel Staying safe out there in the monsoon? Whether you're cozied up with a warm drink or dodging puddles, we’ve got updates to brighten your experience on Hivel. * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-july-2025#a-more-intuitive-way-to-see-your-metrics) 💡 A more intuitive way to see your metrics We’ve given Dashboards a fresh boost - with more ways to group, view, and understand your data. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FlCqibag6lkrZ4jw02REj%252FScreen%2520Cast%25202025-08-05%2520at%25204.37.29%2520PM.gif%3Falt%3Dmedia%26token%3D194fb76b-6a2b-46db-9490-4556175a57f6&width=768&dpr=3&quality=100&sign=cc213e6f&sv=2) **📊 Grouping Made Simpler** * **Release Cycles**: Group data by release cycles that _started_ within your selected date range. * **None**: View data without any time grouping - ideal for cross-period insights (Daily / Weekly / Monthly / Quarterly / Release Cycles). **📈 Chart Options** * Choose from **Bar**, **Line**, or **Area** charts to match your data storytelling style. **🧩 Smarter Toggles for Deeper Control** * **Teams Toggle**: Break down graphs by individual teams. * **Aggregate Toggle**: View the big picture with combined team data. These upgrades mean less digging and more clarity. [_Try it out!_arrow-up-right](https://app.hivel.ai/overview/cycle-time) * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-july-2025#cascade-team-selection) 🌐 Cascade Team Selection You asked for more flexibility in team selections - we delivered! ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FL1w1TBozheEDwZnvXPXO%252FScreen%2520Cast%25202025-08-05%2520at%25204.46.18%2520PM.gif%3Falt%3Dmedia%26token%3D676af324-ea1a-462b-9f1f-ed262ee4a21b&width=768&dpr=3&quality=100&sign=d2e7039f&sv=2) **Cascade Toggle Behavior:** * **ON (default)**: Select all sub-teams under a parent, and the parent gets auto-selected too. * **OFF**: Only the teams you explicitly pick (parent or sub) are included. This gives you tighter control over how your data is sliced and diced across team structures. * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-july-2025#a-fresh-look-for-integrations-and-configurations) 🛠️ A Fresh look for Integrations & Configurations The Integrations and Configuration pages have been fully revamped. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F9GPh0hijfr5tYlG1E4Zp%252FScreen%2520Cast%25202025-08-05%2520at%25204.49.11%2520PM.gif%3Falt%3Dmedia%26token%3Dcff20887-d295-4df7-82b8-61e20b4a1af1&width=768&dpr=3&quality=100&sign=3f0c63cc&sv=2) You’ll find: * All key settings and details in one place * A cleaner experience for faster, smoother setups This makes it easier to plug in and configure exactly how you need - no confusion, no fuss. * * * `**🌧️ Whether it’s raining outside or just in your inbox, we hope these updates make your day a little clearer. Today’s feature animal is the duck. They're waterproof. Be like the duck.**` **🦆** `**Stay dry and see you next month!**` [PreviousRelease Notes - August 2025chevron-left](https://docs.hivel.ai/release-notes/release-notes-august-2025) [NextRelease Notes - May + June 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-may-+-june-2025) Last updated 7 months ago * [💡 A more intuitive way to see your metrics](https://docs.hivel.ai/release-notes/release-notes-july-2025#a-more-intuitive-way-to-see-your-metrics) * [🌐 Cascade Team Selection](https://docs.hivel.ai/release-notes/release-notes-july-2025#cascade-team-selection) * [🛠️ A Fresh look for Integrations & Configurations](https://docs.hivel.ai/release-notes/release-notes-july-2025#a-fresh-look-for-integrations-and-configurations) sun-brightdesktopmoon sun-brightdesktopmoon --- # How do I exclude a PR from rework/maintenance/new work calculation? | Hivel **Excluding commits on the Coding Screen**: * On the **Coding** screen, you can exclude **commits** but not pull requests (PRs). * This approach provides a more granular view, allowing you to drill down into specific commits responsible for spikes in **rework**, **maintenance**, or **new work**. **Excluding pull requests**: * To exclude an entire PR, use the **Process** screen or the **Pull Request** screen. * These sections are designed for managing PR-level exclusions, offering a broader view of work at the PR level. This differentiation ensures that you can focus on the level of detail most relevant to your analysis i.e. commit-level insights on the Coding screen and PR-level actions on the Process or Pull Request screens. [PreviousWhy do some Jira issues show as spillover in Hivel even though they were completed in Jira?chevron-left](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-do-some-jira-issues-show-as-spillover-in-hivel-even-though-they-were-completed-in-jira) [NextWhy Product and Allocation's previous data is not reflecting?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-product-and-allocations-previous-data-is-not-reflecting) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Alternate methods | Hivel [How to integrate GitHub with Classic Token?chevron-right](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-integrate-github-with-classic-token) [How to create Github fine-grained token for Hivel Integration?chevron-right](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-create-github-fine-grained-token-for-hivel-integration) [How to reauthorize Github with a classic token?chevron-right](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-reauthorize-github-with-a-classic-token) [PreviousHow to integrate GitHub with repository level access?chevron-left](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-repository-level-access) [NextHow to integrate GitHub with Classic Token?chevron-right](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-integrate-github-with-classic-token) sun-brightdesktopmoon sun-brightdesktopmoon --- # What to do if my Rework is high? | Hivel ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high#identify-which-team-or-repo) Identify which team or repo As a first step we should understand which team or repo is having high rework so that we can evaluate if that is expected or not given the business context and focus on them. You can do this in the Cockpit, by switching to tabular view and sorting on rework column. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FVdS28QDgBREPY77uJx9n%252FGIF%2520Recording%2520Aug%252021%2520from%2520Jumpshare%2520%281%29.gif%3Falt%3Dmedia%26token%3D7bf7a4c9-f868-461f-ad47-d2dbe487fa78&width=768&dpr=3&quality=100&sign=dc359931&sv=2) ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high#identify-which-team-or-repo-1) Drilldown further to identify user or PR You can drill down and identify which users or PRs had the most rework by applying filters on the Coding screen. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FhLVfKxTfuwlV6wZi5u27%252FGIF%2520Recording%2520Aug%252021%2520from%2520Jumpshare.gif%3Falt%3Dmedia%26token%3D891acb53-475d-4206-9744-09fa07b3d8e0&width=768&dpr=3&quality=100&sign=4cf2470e&sv=2) ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high#causes-of-high-rework) Causes of high rework * **Incomplete or Evolving Requirements:** If requirements are not fully defined or evolve after coding has started, developers may need to revisit and modify code to accommodate new or refined expectations. * **Poor Initial Design or Implementation:** If the code is not well-designed or optimally implemented from the start, it may need to be refactored or rewritten shortly after being introduced. * **Bug Fixes Post-Release:** Bugs that are discovered after the code has been deployed often need to be fixed quickly, leading to rework within a short timeframe. * **Technical Debt Payoff:** If the initial implementation was rushed or done with known technical debt, there may be a need to revisit and clean up the code shortly after it was written. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high#ways-to-address-high-rework) Ways to address high rework * **Improve Requirement Gathering and Stakeholder Alignment:** Engage stakeholders early and frequently to ensure that all requirements are thoroughly understood and documented. Use user stories, acceptance criteria, and wireframes to clearly define expectations. * **Invest in Design and Code Reviews:** Allocate time for thorough design before implementation. Conduct design reviews with peers to identify potential issues early. Follow up with regular code reviews to ensure that the implementation aligns with the design and best practices. * **Improve Release and Monitoring Processes:** Implement a more rigorous testing and staging process before release to catch bugs earlier. Use continuous deployment practices with canary releases or blue-green deployments to minimize the impact of bugs. * **Allocate Time for Refactoring and Debt Reduction:** Regularly schedule time within sprints specifically for addressing technical debt. Encourage developers to refactor code as part of their daily work, rather than postponing it. [PreviousHow to improve Qualitychevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-quality) [NextWhat happens if there are too many Flashy Reviews and how to prevent them?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-happens-if-there-are-too-many-flashy-reviews-and-how-to-prevent-them) Last updated 1 year ago * [Identify which team or repo](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high#identify-which-team-or-repo) * [Drilldown further to identify user or PR](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high#identify-which-team-or-repo-1) * [Causes of high rework](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high#causes-of-high-rework) * [Ways to address high rework](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-to-do-if-my-rework-is-high#ways-to-address-high-rework) sun-brightdesktopmoon sun-brightdesktopmoon --- # Why don't I see delivery accuracy for Kanban boards? | Hivel #### [hashtag](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-dont-i-see-delivery-accuracy-for-kanban-boards#why-delivery-accuracy-isnt-shown-for-kanban-boards) Why Delivery Accuracy isn’t shown for kanban boards: 1. **Sprint-Based Metrics**: * Delivery Accuracy calculates the planned vs. completed work based on a **sprint cycle**. This includes determining the percentage of tickets completed relative to those planned for the sprint. * Since Kanban does not operate with defined time-boxed sprints, this metric is incompatible with its continuous delivery flow. 2. **Kanban’s continuous nature**: * Kanban focuses on **workflow optimization and throughput**, with no strict boundaries like sprint start or end dates. * Without those boundaries, measuring planned vs. completed work over a set timeframe (as required for Delivery Accuracy) would yield incomplete or misleading results. circle-info You may notice sprints appearing in the sprint filter for Kanban boards; these are weekly dummy sprints generated from the backend to provide a trend representation in the Issue tab. [PreviousWhy Product and Allocation's previous data is not reflecting?chevron-left](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-product-and-allocations-previous-data-is-not-reflecting) [NextWhy some of the repositories are not imported or synced?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-some-of-the-repositories-are-not-imported-or-synced) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Slack Integration with Hivel | Hivel No need to jump between 10 different dashboards to figure out your top priorities or spot potential problems. Whether it’s reminders about pending PRs, or a quick summary of what happened in the week, you can stay on top of things right where you work. Hivel will send timely notifications to your preferred Slack channel(s), so you can act on issues before they turn into bigger problems. #### [hashtag](https://docs.hivel.ai/integrations/slack-integration-with-hivel#how-to-integrate-slack-with-hivel) **How to Integrate Slack with Hivel** * Go to _**Settings →**_ [_**Integrations**_arrow-up-right](https://app.hivel.ai/settings/integrations) _**→ Slack**_ and click on "Connect". ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F42x7kBgZhFk9K7BxtnIO%252Fimage.png%3Falt%3Dmedia%26token%3D4a65b626-c15e-4b9a-b567-45d0619f97ab&width=768&dpr=3&quality=100&sign=22c7ca9&sv=2) * A prompt will appear asking you to review the app’s access permissions. Click **Allow** to confirm. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FcBLsFgZlicliNRzkeRy5%252Fimage.png%3Falt%3Dmedia%26token%3D947e55a9-a3d3-4875-ae9a-9fd2f2874dff&width=768&dpr=3&quality=100&sign=4f8ab8c8&sv=2) circle-info **Note:** You’ll need to be a **Slack Workspace Admin** to complete this integration. **Ta-da! You’re all set. Hivel is now connected to Slack.** For Hivel to start sending alerts to your preferred Slack channel, follow the steps outlined in [this guidearrow-up-right](https://docs.hivel.ai/using-hivel/alerts-in-hivel/setting-up-the-slack-channel-for-alerts) . Let us know if you need any help setting this up! Contact us at [\[email protected\]](https://docs.hivel.ai/cdn-cgi/l/email-protection) . [PreviousAzure AD SSOchevron-left](https://docs.hivel.ai/integrations/azure-ad-sso) [NextAPI Documentationchevron-right](https://docs.hivel.ai/integrations/api-documentation) Last updated 3 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Notes | Hivel [Release Notes - Q1 2026chevron-right](https://docs.hivel.ai/release-notes/release-notes-q1-2026) [Release Notes - November 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-november-2025) [Release Notes - October 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-october-2025) [Release Notes - September 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-september-2025) [Release Notes - August 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-august-2025) [Release Notes - July 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-july-2025) [Release Notes - May + June 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-may-+-june-2025) [Release Notes - April 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-april-2025) [Release Notes - March 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-march-2025) [Release Notes - February 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-february-2025) [Release Notes - January 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-january-2025) [Release Notes - December 2024chevron-right](https://docs.hivel.ai/release-notes/release-notes-december-2024) [Release Notes - November 2024chevron-right](https://docs.hivel.ai/release-notes/release-notes-november-2024) [Release Notes - October 2024chevron-right](https://docs.hivel.ai/release-notes/release-notes-october-2024) [PreviousHow to balance speed and quality?chevron-left](https://docs.hivel.ai/improve-performance/how-to-balance-speed-and-quality) [NextRelease Notes - Q1 2026chevron-right](https://docs.hivel.ai/release-notes/release-notes-q1-2026) sun-brightdesktopmoon sun-brightdesktopmoon --- # Why do some Jira issues show as spillover in Hivel even though they were completed in Jira? | Hivel In Hivel, we identify completed issues by the issue status category and resolution date of the issues i.e. 1. If the resolution date is on of before the sprint end date, then they are considered as completed. 2. If the resolution date is not set or is after the sprint end date, then it is considered as spillover. As a result of certain Jira configurations, some completed issues may lack a resolution date. Hence even if their status falls under the "Closed" category, these issues are still classified as spillovers in Hivel. circle-info To configure the issues to have resolutions and resolution dates set while closing, please refer to this [documentationarrow-up-right](https://confluence.atlassian.com/jirakb/jira-issues-need-a-resolution-826873869.html) from Atlassian on the same. [PreviousPR, Issues & Workflow FAQschevron-left](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs) [NextHow do I exclude a PR from rework/maintenance/new work calculation?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/how-do-i-exclude-a-pr-from-rework-maintenance-new-work-calculation) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Easing into Kanban: How to set your team up for success | Hivel As a team begins to shift from Scrum to Kanban, it's important to remember that this is not just a process change - it's a mindset shift! Kanban emphasizes continuous flow, transparency, and incremental improvement rather than sprint-based planning and velocity. This transition doesn’t need to be abrupt. In fact, the most effective shifts happen gradually, building on what your team already knows and does well. In this guide, we’ve outlined practical, low-friction steps to help your team ease into Kanban. ### [hashtag](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#start-small-support-your-team-and-grow-together) Start small, Support your team, and Grow together Making the shift to Kanban works best when done gradually, with empathy for your team and clarity on the _why_. Here’s how to set a strong foundation: **a) Begin with what’s familiar** Instead of reinventing your workflow from day one, just visualize your current process on a Kanban board. No need to change how you work immediately - just observe and get a shared view of how work flows. **b) Invest in readiness, not perfection** Before diving deep, check how confident your team feels about Kanban. Share simple training, clarify common misconceptions, and create a safe space for questions. The goal isn’t perfection - it’s comfort and clarity. **c) Encourage everyone to lead** Empower team members to call out blockers, suggest process tweaks, and take ownership of improvements. Leadership isn’t a title here - it’s a behavior. Recognizing these efforts helps build trust and keeps momentum going. * * * ### [hashtag](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#consider-a-hybrid-approach-scrumban-during-transition) Consider a hybrid approach (Scrumban) during transition **Why:** Combining elements of Scrum and Kanban can ease the transition and allow teams to retain beneficial practices from both methodologies. **What to do:** * Implement a Scrumban approach by maintaining certain Scrum rituals (like daily stand-ups) while adopting Kanban's continuous flow. * Gradually shift towards a full Kanban system as the team becomes more comfortable. * An intro to Scrumban by [Asanaarrow-up-right](https://asana.com/resources/scrumban?utm_source=chatgpt.com) . * * * ### [hashtag](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#focus-on-how-long-work-takes-not-sprint-velocity) Focus on how long work takes (Not Sprint Velocity) **Why:** In Kanban, there are no sprints - so speed should be measured by how long each task or bug fix takes to complete. **What to do:** * Track **Cycle Time** and identify if there are an bottlenecks in any stage. * * * ### [hashtag](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#visualize-blocked-work-or-on-hold-items) Visualize Blocked Work or On Hold items **Why:** Making stalled tasks visible helps teams identify and address issues promptly. **What to do:** * Use visual indicators (like color codes or tags) to mark tasks that are blocked or waiting. * Create specific columns or areas on the Kanban board for tasks that are on hold or awaiting input. * * * ### [hashtag](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#limit-work-in-progress-to-avoid-overload) Limit Work in Progress (to avoid overload) **Why:** If teams take on too much at once, nothing gets done quickly. **What to do:** * Set a limit on how many tasks or PRs are “in progress” at the same time. * Use Hivel to see how many things each developer is juggling. * A guide on [WIP limitsarrow-up-right](https://www.atlassian.com/agile/kanban/wip-limits) by Atlassian * * * ### [hashtag](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#separate-planned-and-unplanned-work) Separate Planned and Unplanned work **Why:** Without sprints, unexpected work can sneak in and cause delays. **What to do:** * In Hivel, to represent the work item volume, we create auto 2-week sprints. And we categorize each work item into planned or unplanned depending on whether they were created before the sprint start date or after. * Another approach to identify planned and unplanned work is to maintain a separate field to capture the info. * * * ### [hashtag](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#encourage-smaller-faster-code-changes) Encourage smaller, faster code changes **Why:** In a continuous flow model, large PRs slow everything down. **What to do:** * Recommend smaller PRs that are easier to review. * Hivel shows PR size and how long reviews take. * * * ### [hashtag](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#prevent-work-from-getting-stuck) Prevent work from getting stuck **Why:** In Kanban, there’s no sprint deadline to push things along. **What to do:** * Use Hivel to: * Identify work items with high issue age * Tasks sitting without activity for a few days * PRs not reviewed or merged * This keeps things moving. `**The shift to Kanban is a journey and with the right mindset, your team will not only adapt but thrive.**` [PreviousHow to measure impact of Copilots using Hivel?chevron-left](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/how-to-measure-impact-of-copilots-using-hivel) [NextMetrics & Data FAQschevron-right](https://docs.hivel.ai/faqs/metrics-and-data-faqs) Last updated 9 months ago * [Start small, Support your team, and Grow together](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#start-small-support-your-team-and-grow-together) * [Consider a hybrid approach (Scrumban) during transition](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#consider-a-hybrid-approach-scrumban-during-transition) * [Focus on how long work takes (Not Sprint Velocity)](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#focus-on-how-long-work-takes-not-sprint-velocity) * [Visualize Blocked Work or On Hold items](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#visualize-blocked-work-or-on-hold-items) * [Limit Work in Progress (to avoid overload)](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#limit-work-in-progress-to-avoid-overload) * [Separate Planned and Unplanned work](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#separate-planned-and-unplanned-work) * [Encourage smaller, faster code changes](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#encourage-smaller-faster-code-changes) * [Prevent work from getting stuck](https://docs.hivel.ai/faqs/reporting-and-goal-tracking-faqs/easing-into-kanban-how-to-set-your-team-up-for-success#prevent-work-from-getting-stuck) sun-brightdesktopmoon sun-brightdesktopmoon --- # What to do if my Cycle Time is high? | Hivel circle-check #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high#cycle-time-is-the-time-it-takes-from-the-first-commit-to-pr-merged) Cycle time is the time it takes from the first commit to PR merged. High cycle time means that it takes a longer than desirable duration to complete tasks, such as features or bug fixes, from the start of development to delivery. This can indicate inefficiencies in the process, such as bottlenecks, poor resource allocation, or overly complex tasks. High cycle times often lead to slower delivery of value, reduced productivity, and a lack of responsiveness to changes, which can impact overall project success and stakeholder satisfaction. Reducing the org's cycle time is crucial for maintaining agility and ensuring timely, cost-effective delivery of quality software. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high#identify-which-team-or-repo) Identify which team or repo As a first step we should understand which team or repo is facing high cycle times so that we can evaluate if that is expected or not given the business context and focus on them. You can do this in the Cockpit, by switiching to tabular view and sorting on cycle time column. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F99TAv4v2sUBVZ4jjblbL%252FGIF%2520Recording%2520Aug%252012%2520from%2520Jumpshare%2520%281%29.gif%3Falt%3Dmedia%26token%3D410ae94d-9bbe-455c-a922-a71adfb3fa9c&width=768&dpr=3&quality=100&sign=e873c4f6&sv=2) ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high#identify-the-bottlenecks-whether-coding-review-or-merge) Identify the bottlenecks - whether coding, review, or merge To understand what is causing the cycle time to be high, it is important to identify which phases of the development are taking the longest. We can do this by going to the Process screen, filtering on any particular teams, and understanding from the trendline which phase is taking longer. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F4zfcHMdq0Ep18dnTfZTn%252FGIF%2520Recording%2520Aug%252012%2520from%2520Jumpshare.gif%3Falt%3Dmedia%26token%3Dac6ecacb-db21-436d-9c7c-6031382cf87b&width=768&dpr=3&quality=100&sign=ec5e894d&sv=2) _In this case, the Cycle Time was mainly influenced by Coding Time_ ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high#causes-for-high-cycle-time) Causes for high cycle time * **Review and testing bottlenecks:** Delays in specific stages like code reviews, testing, or approvals can create bottlenecks, slowing down the overall process. * **Lack of Automation:** Manual processes for testing, deployment, or integration can significantly increase cycle time. Lack of CI/CD pipelines can contribute to this. * **Overloaded Team Members:** If team members are juggling too many tasks or are overburdened, it can delay progress on their assigned tasks. * **Unclear Prioritization:** When tasks are not clearly prioritized, developers may focus on less critical work, delaying more important tasks. * **Scope Creep:** Continuously adding new requirements or features during the development process can extend the cycle time. circle-info To know more on understanding and addressing high [Coding times](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-coding-time-is-high) , high [Merge times](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-merge-time-is-high) , and high [Review times](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-review-time-is-high) , please refer to the linked articles. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high#how-to-reduce-cycle-time) How to reduce Cycle Time? * **Optimize Code Reviews:** Streamline code review processes by setting clear guidelines, automating checks, and ensuring timely reviews. Consider implementing a review rotation to evenly distribute the workload. * **Automate Testing and Deployment:** Automate repetitive tasks such as unit testing, integration testing, and deployment to reduce manual effort and minimize errors. * **Prioritize Work Effectively:** Use tools like Kanban boards or sprint planning to prioritize tasks based on their importance and impact. Focus on high-value tasks that can be delivered quickly. * **Limit Work in Progress (WIP):** Avoid overloading developers with too many tasks at once. Limiting WIP helps maintain focus and reduces context switching, leading to faster completion of individual tasks. * **Refactor Code Regularly:** Dedicate time to refactoring and cleaning up code to reduce technical debt. Cleaner code is easier to work with, leading to faster development and fewer bugs. If you need additional help, feel free to reach out to [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#e794929797889593a78f8e91828bc9868e) . [PreviousHow to improve Speed?chevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-speed) [NextWhat to do if my Coding Time is high?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-coding-time-is-high) Last updated 1 year ago * [Identify which team or repo](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high#identify-which-team-or-repo) * [Identify the bottlenecks - whether coding, review, or merge](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high#identify-the-bottlenecks-whether-coding-review-or-merge) * [Causes for high cycle time](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high#causes-for-high-cycle-time) * [How to reduce Cycle Time?](https://docs.hivel.ai/improve-performance/how-to-improve-speed/what-to-do-if-my-cycle-time-is-high#how-to-reduce-cycle-time) sun-brightdesktopmoon sun-brightdesktopmoon --- # Claude Code | Hivel 1. Log in to your Hivel account. 2. In the left panel, select **Settings**, and go to the **Integrations** tab. 3. Find the **Claude Code** card and click the **'Connect'** button. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FWpgCfqAydU9cRr3IIKZK%252Fimage%2520%28118%29.png%3Falt%3Dmedia%26token%3D53250a61-579c-498a-b7d4-86ca6f5f05f7&width=768&dpr=3&quality=100&sign=cbfb9007&sv=2) 4. In the pop-up, paste the Claude Code API ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F0zNg29TUiWdoJqiGfqzh%252Fimage%2520%28119%29.png%3Falt%3Dmedia%26token%3D5d51b546-bb5a-4a18-b0ba-0b7b49ef079e&width=768&dpr=3&quality=100&sign=4de30692&sv=2) * To get the above Claude Code API key, use the following steps: * Go to the Settings tab, click API keys on the left-side menu. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FOqLz5rCFW8fKbDl9gnXW%252Funknown.png%3Falt%3Dmedia%26token%3Dc3c8f214-bb1f-4f60-84a6-9dae01b58c26&width=768&dpr=3&quality=100&sign=b3a4d2e0&sv=2) * Click Create Key. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Ft3YmgUexgerjwKM72udu%252Funknown.png%3Falt%3Dmedia%26token%3Dc4bb9fd8-41aa-4b69-8583-cfcf6fd186b1&width=768&dpr=3&quality=100&sign=ead7c1a1&sv=2) * **Name your key as Hivel, and click Create Key to finish the process.** circle-exclamation Please ensure that the API key is an Admin API key (done from an Admin account), which starts with `sk-ant-admin...` and differs from standard API keys. [PreviousCursor Integrationchevron-left](https://docs.hivel.ai/integrations/ai-tools/cursor-integration) [NextSetting up your own key for AI featureschevron-right](https://docs.hivel.ai/integrations/ai-tools/setting-up-your-own-key-for-ai-features) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # On-Prem Setup | Hivel [On-Prem Installation Guidechevron-right](https://docs.hivel.ai/integrations/on-prem-setup/on-prem-installation-guide) [Application Setup Guide: User Sign-up and Integrationchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/application-setup-guide-user-sign-up-and-integration) [Gitlab On-Premchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/gitlab-on-prem) [Jira On-Premchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/jira-on-prem) [SonarQube On-Premchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/sonarqube-on-prem) [Creating a Bitbucket App Passwordchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password) [On-Prem Outlook Integrationchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/on-prem-outlook-integration) [Coding Metrics Setupchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/coding-metrics-setup) [PreviousDORA Metrics Powered by New APIs in Hivelchevron-left](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel) [NextOn-Prem Installation Guidechevron-right](https://docs.hivel.ai/integrations/on-prem-setup/on-prem-installation-guide) sun-brightdesktopmoon sun-brightdesktopmoon --- # Gitlab Server | Hivel **Data Access by Hivel** * Hivel accesses the past 60-90 days of commits and pull requests from active repositories during the initial sync. **Authorization Mechanism** * Hivel employs GitLab Server's OAuth for authentication. * Users maintain full control and can withdraw access by revoking the Personal Access Token. **Effortlessly Connect Your GitLab Server with Hivel** This easy-to-follow guide will lead you through each step, ensuring a smooth and efficient integration process to unlock efficiency insights across your org. **Step 1: Gather Your GitLab Server Details** First things first, let's get some essential information from your GitLab Server: * **GitLab Server URL**: This is your gateway to accessing your GitLab Server. Look for an address in the format of `https://{your-git-domain}.com/`. Don't forget to replace `{your-git-domain}` with your actual domain. * **GitLab Server Version**: Compatibility is key, and knowing your GitLab Server version is crucial. Here's how to find it: * Head over to your GitLab Server interface. * Click on the 'Help' section. It’s usually at the end of your GitLab URL, like this: `/help`. * You'll see your version info displayed, typically in the format of "GitLab Community Edition {x.x.x} / GitLab Enterprise Edition {x.x.x}". **Step 2: Whitelist Necessary IP Addresses** For a secure and uninterrupted connection, make sure to whitelist the following IP addresses: * **Mandatory IPs**: * 107.23.139.76 * 3.219.89.23 * **Recommended but Optional IPs**: * 45.119.114.218 * 183.82.116.218 **Step 3: Creating a Personal Access Token (PAT):** Let's create your PAT in GitLab: * Select 'Preferences'. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FwSRdR4516GeE2HUNRYqz%252Fimage%2520%287%29.png%3Falt%3Dmedia%26token%3Dc57ebffc-c262-43ca-9250-42a6ef3b5dbd&width=768&dpr=3&quality=100&sign=b50bd3f2&sv=2) * Navigate to 'Access Tokens' in the left sidebar. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F3Hqyn7emceKVROnC67Nq%252Fimage%2520%288%29.png%3Falt%3Dmedia%26token%3Daaa7031a-f383-41e5-9b84-b023b7072aed&width=768&dpr=3&quality=100&sign=d0bb354d&sv=2) * Enter a token name and opt not to set an expiry date. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F1BqmBcgXqEzaFuW8vOML%252FScreenshot%25202025-02-19%2520at%25204.26.01%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Db709f10d-9e86-467b-83bd-9069f4fe9c10&width=768&dpr=3&quality=100&sign=1ebdd528&sv=2) * Select the following scopes: `api, read_api, read_user, read_repository`. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FvdlQM7ApkHv730hIQJdx%252Fimage%2520%289%29.png%3Falt%3Dmedia%26token%3D9a236f70-80b1-4005-be33-5edbbe566f14&width=768&dpr=3&quality=100&sign=76dbc3dc&sv=2) * Click 'Create personal access token'. **Note these scopes as they're crucial for integration** **Step 4:** Navigate to the Hivel [sign-up pagearrow-up-right](https://app.hivel.ai/signup) **Step 5:** Add your work email id (If you'd like to use your personal email id please contact [\[email protected\])envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#2754525757485553674f4e51424b09464e0e) **Step 6:** Now, you can use your Google or Microsoft login with your work email id; or create a password. **Step 7:** Create your Company Profile, and click '**Get Started**'. **Step 8:** Once you've successfully created your Company Profile, you will be redirected to the Integrations Page. **Step 9:** Select Gitlab and log in to your company's Gitlab account using a service account. **Step 10: Share Your Details** You’ll need to provide the following: * Email, preferably a service account such as \[[\[email protected\]](https://docs.hivel.ai/cdn-cgi/l/email-protection)\ \] * Username * Personal Access Token (PAT) - return to the Hivel application, paste the personal access token, and hit **Submit.** **Below are some screenshots of the steps you can refer to if needed:** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F9Al1RETLnRQZ4jI3yVlL%252Fimage%2520%2820%29.png%3Falt%3Dmedia%26token%3D6497821d-9343-48c0-9151-01eb6a9ccb06&width=768&dpr=3&quality=100&sign=f1c39fb7&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FdejuQx5xvnK79sqk8SYq%252Fimage%2520%2821%29.png%3Falt%3Dmedia%26token%3D50e0fdff-46ea-40d1-ba37-f2869e69131b&width=768&dpr=3&quality=100&sign=d3da3fb2&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FIfGHZJHIeObwoc1LdWPc%252Fimage%2520%2822%29.png%3Falt%3Dmedia%26token%3D840f3ed7-cbef-476f-8dd0-9ac00d19a701&width=768&dpr=3&quality=100&sign=daf29f07&sv=2) [PreviousGitlabchevron-left](https://docs.hivel.ai/integrations/scm/gitlab) [NextGitlab Cloudchevron-right](https://docs.hivel.ai/integrations/scm/gitlab/gitlab-cloud) Last updated 7 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Github Copilot Integration | Hivel [hashtag](https://docs.hivel.ai/integrations/ai-tools/github-copilot-integration#log-in-to-hivel-through-a-copilot-admin-account) Log in to Hivel through a Copilot admin account -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1. Ensure to use a Copilot admin account, which also has access to all the workspaces applicable for Copilot. 2. Ensure the "Copilot Metrics API" in GitHub is enabled. 1. Settings >> Copilot >> Copilot Metrics API 3. Navigate to the Integrations screen in the left panel. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F3JdSXZeJGYhiC0soSStJ%252Fimage%2520%2855%29.png%3Falt%3Dmedia%26token%3D6f903e06-ad8f-4c49-88dd-5a72c8d1466f&width=768&dpr=3&quality=100&sign=64671346&sv=2) [hashtag](https://docs.hivel.ai/integrations/ai-tools/github-copilot-integration#integrate-copilot) Integrate Copilot -------------------------------------------------------------------------------------------------------------------------- 1. Click on the Copilot integration card and follow the steps to redirect to your GitHub account. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F7i5e2MqTq2HgBWH9cbMJ%252Fimage%2520%2854%29.png%3Falt%3Dmedia%26token%3Dbe1ea0eb-059f-4ed0-8a26-437279cd336f&width=768&dpr=3&quality=100&sign=a3c1075&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F9SUOAxFK1NUCTpCZA9BW%252Fimage%2520%2853%29.png%3Falt%3Dmedia%26token%3Df71c2cb0-91b3-4044-a358-4cc5cc99a653&width=768&dpr=3&quality=100&sign=49da9775&sv=2) [hashtag](https://docs.hivel.ai/integrations/ai-tools/github-copilot-integration#grant-permissions-to-the-required-workspaces) Grant permissions to the required workspaces -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Once redirected to GitHub, authorize your organization's access by clicking on "Grant" against your organization. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F3L7eHybcEvUtPLJRlyQO%252Fimage.png%3Falt%3Dmedia%26token%3D1e939050-ce9f-4012-a062-6cae4448a710&width=768&dpr=3&quality=100&sign=8cf7e691&sv=2) All done! The data will be processed within 24 hours and you should be able to view the metrics in [Copilot Adoption screenarrow-up-right](https://docs.hivel.ai/copilot-adoption) . circle-info In initial sync, we only have access to 28 days of historical data [PreviousAI Toolschevron-left](https://docs.hivel.ai/integrations/ai-tools) [NextGithub Copilot - Enterprisechevron-right](https://docs.hivel.ai/integrations/ai-tools/github-copilot-enterprise) Last updated 1 month ago * [Log in to Hivel through a Copilot admin account](https://docs.hivel.ai/integrations/ai-tools/github-copilot-integration#log-in-to-hivel-through-a-copilot-admin-account) * [Integrate Copilot](https://docs.hivel.ai/integrations/ai-tools/github-copilot-integration#integrate-copilot) * [Grant permissions to the required workspaces](https://docs.hivel.ai/integrations/ai-tools/github-copilot-integration#grant-permissions-to-the-required-workspaces) sun-brightdesktopmoon sun-brightdesktopmoon --- # Why some of the repositories are not imported or synced? | Hivel Sometimes, you might notice that certain repositories are listed as **not synced** in Hivel. This can happen due to the following reasons: 1. **Lost Access**: Hivel no longer has access to the workspace or repository due to expired or revoked token permissions. 2. **Inactivity**: The repository hasn’t had any recent activity, so no new data has been synced. #### [hashtag](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-some-of-the-repositories-are-not-imported-or-synced#steps-to-fix-unsynced-repositories) Steps to Fix Unsynced Repositories To resolve this issue: 1. **Reauthorize Hivel**: If access has been lost, reauthorize Hivel with the necessary permissions to the workspace or repository. This will restore synchronization and ensure data is up to date. 2. **Check Repository Activity**: For inactive repositories, verify if they are expected to remain dormant or should have recent updates. If you need further help, please contact our support team at [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#33404643435c4147735b5a45565f1d525a) . [How to reauthorize Github with a classic token?chevron-right](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-reauthorize-github-with-a-classic-token) [How to re-authorize / re-initiate GitHub integration with account wide access?chevron-right](https://docs.hivel.ai/integrations/scm/github/how-to-re-authorize-re-initiate-github-integration-with-account-wide-access) [BitBucket Integrationchevron-right](https://docs.hivel.ai/integrations/scm/bitbucket/bitbucket-integration) [Gitlabchevron-right](https://docs.hivel.ai/integrations/scm/gitlab) [PreviousWhy don't I see delivery accuracy for Kanban boards?chevron-left](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-dont-i-see-delivery-accuracy-for-kanban-boards) [NextHow can I add a template in dashboards for my org to follow?chevron-right](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/how-can-i-add-a-template-in-dashboards-for-my-org-to-follow) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Notes - January 2025 | Hivel We’re kicking off the year with a bang (well, a focused one)! January’s update brings a couple of exciting additions to start your 2025 on the right foot. #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-january-2025#coding-hotspots-beta) **Coding Hotspots (Beta)** Our new _Coding Hotspots_ feature is here to help engineering teams identify the areas in the codebase that see the most bug activity. By analyzing JIRA issues, PRs, and commit history, it highlights the files most often modified due to bug fixes. This will help you focus on the right areas, improve code stability, and boost your team's efficiency. _It’s currently available through a flag as we continue to iterate and enhance it. If you want to be an early adopter, please reach out to us🙌_ ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FrgywFOJN5Vcy81HATPjm%252Fimage.png%3Falt%3Dmedia%26token%3D3f3baed2-5e36-4ca8-a933-ea182b7a4621&width=768&dpr=3&quality=100&sign=e8300237&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FLb8uEYqU0tvmygObnvJD%252FScreen%2520Cast%25202025-04-01%2520at%25202.40.22%2520PM.gif%3Falt%3Dmedia%26token%3D44b28733-399f-4fb0-9970-30b3cde0c39f&width=768&dpr=3&quality=100&sign=53bdf745&sv=2) #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-january-2025#id-2024-wrapped) **2024 Wrapped**: Need a little end-of-year reflection? _2024 Wrapped_ brings you a summary of key metrics and highlights from last year - perfect for reflecting on accomplishments while you’re planning your 2025 goals. It’s like a year-in-review, but with more fun stats! ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FKOG1u12CpqKucZ0sSR9I%252Fimage.png%3Falt%3Dmedia%26token%3D08e8da05-005f-4f44-942c-1cd385cc6245&width=768&dpr=3&quality=100&sign=382e1694&sv=2) That's a wrap! Other than that, we’ve been hard at work planning the roadmap and making sure everything stays stable so you can hit the ground running in the new year. 🚀 **Time to debug your code and your caffeine levels for the new year** ☕️⚡️ [PreviousRelease Notes - February 2025chevron-left](https://docs.hivel.ai/release-notes/release-notes-february-2025) [NextRelease Notes - December 2024chevron-right](https://docs.hivel.ai/release-notes/release-notes-december-2024) Last updated 11 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Notes - March 2025 | Hivel Spring is here 🌱, and so is a fresh new set of updates! In March, we’ve been heads-down working on some major upgrades and a whole bunch of thoughtful enhancements to make your workflows smoother and smarter. ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-march-2025#introducing-cockpit-pro) **🚀 Introducing Cockpit Pro** We’ve combined the best of _Cockpit_ and _Dashboards_ into a unified, intuitive experience called **Cockpit Pro**. It’s your go-to command center for metrics and insights. Here’s what’s new: * ✅ **Unified Boards & Templates** - All in one place with clear labels. * ⭐ **Favorites** - Pin your go-tos for quick access. * 📊 **Metrics Preview** - Hover on templates to peek at the included metrics. * 👥 **Board Ownership** - Instantly see who created a board and when. ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-march-2025#other-enhancements-youll-love) **Other enhancements you’ll love** #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-march-2025#hivel-quadrant-now-with-a-sleeker-ui) Hivel Quadrant – Now with a sleeker UI Access directly from the [_left panel_arrow-up-right](https://app.hivel.ai/dashboard/hivel-quadrant) and toggle between _Speed x Quality_ and _Speed x Throughput_. Updated logic ensures a better reflection of the ideal states. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fb3qjkaM4ZhY1E4ctpqUZ%252Fimage.png%3Falt%3Dmedia%26token%3Dfd7509a0-2cd6-4f6f-a246-fca0cf3c45f9&width=768&dpr=3&quality=100&sign=22e415ca&sv=2) #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-march-2025#coding-hotspots-by-workspaces) Coding Hotspots by Workspaces Get deeper insights by analyzing hotspot data at the _workspace_ level - perfect for teams with grouped repositories. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FsNk6tnhL00y2GfOkfnep%252FScreen%2520Cast%25202025-04-01%2520at%25203.46.35%2520PM.gif%3Falt%3Dmedia%26token%3D918b1829-0f19-4d9b-8b7e-04f580503155&width=768&dpr=3&quality=100&sign=6e84e099&sv=2) #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-march-2025#improved-team-search) Improved Team Search Navigating the [_Teams_arrow-up-right](https://app.hivel.ai/settings/teams) page just got easier with better support for teams, sub-teams, and even sub-sub-teams. #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-march-2025#active-days-metric-now-standardized) Active Days Metric – Now Standardized Weekly average active days are now consistent across all views. Need total days? You’ll still find that in your Activity reports. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FROeAfu1rcySu1zVuS7UZ%252Fimage.png%3Falt%3Dmedia%26token%3D7a0d39bd-8f51-402a-92f6-44dc777fff8b&width=768&dpr=3&quality=100&sign=7b0fff48&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FA5OxxipKriX2R3gxAAy8%252Fimage.png%3Falt%3Dmedia%26token%3D0dac68d0-37ae-45e9-bcaf-04f8c710a412&width=768&dpr=3&quality=100&sign=da15e3a5&sv=2) #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-march-2025#enhanced-git-metric-filtering) Enhanced Git Metric Filtering We’ve expanded the filters across Git pages: * Added **Labels** and **Workspaces** filters across Cockpit Pro, Process, Dev360, and more. * The Workspace filter will be available based on whether you have configured any Workspaces in the Settings. * Want Labels enabled? Just let us know - we'll flip the switch! ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FRVcqs3HznLYRX6TtVSz2%252FScreen%2520Cast%25202025-04-01%2520at%25203.50.01%2520PM.gif%3Falt%3Dmedia%26token%3Dcadeafa6-9c21-46a0-abd9-7c7d1d3cd7c9&width=768&dpr=3&quality=100&sign=cf905193&sv=2) That’s all for March - one big revamp, and a whole lot of polish. **May your metrics align, your builds stay green, and your posture remain slightly better than yesterday** 💻🌤️ [PreviousRelease Notes - April 2025chevron-left](https://docs.hivel.ai/release-notes/release-notes-april-2025) [NextRelease Notes - February 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-february-2025) Last updated 11 months ago * [🚀 Introducing Cockpit Pro](https://docs.hivel.ai/release-notes/release-notes-march-2025#introducing-cockpit-pro) * [Other enhancements you’ll love](https://docs.hivel.ai/release-notes/release-notes-march-2025#other-enhancements-youll-love) sun-brightdesktopmoon sun-brightdesktopmoon --- # How can I add a template in dashboards for my org to follow? | Hivel **Custom Templates**: * The **Template** section in Dashboards does not currently support adding custom templates directly. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F1kP0uewI5VeYBsdGJ4Tz%252Fimage.png%3Falt%3Dmedia%26token%3D28f91783-3959-488d-9aef-9d70e0469232&width=768&dpr=3&quality=100&sign=894b3367&sv=2) * However, you can reach out to our team, and we’ll configure the custom template for you. Contact us at **[\[email protected\]](https://docs.hivel.ai/cdn-cgi/l/email-protection) ** for assistance. **Creating and Sharing Dashboards**: * Alternatively, you can create a **public dashboard**, which can be shared and accessed by other users. * **Note**: Only the **dashboard owner** has the ability to edit the dashboard, ensuring control over its content and structure. For further questions or support, feel free to get in touch with our team! [PreviousWhy some of the repositories are not imported or synced?chevron-left](https://docs.hivel.ai/faqs/pr-issues-and-workflow-faqs/why-some-of-the-repositories-are-not-imported-or-synced) [NextSystem Behavior & Limitations FAQschevron-right](https://docs.hivel.ai/faqs/system-behavior-and-limitations-faqs) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Gitlab Cloud | Hivel **Data Access by Hivel** * Hivel accesses the past 60-90 days of commits and pull requests from active repositories during the initial sync. **Authorization Mechanism** * Hivel employs GitLab's OAuth for authentication. * Users maintain full control and can withdraw access anytime via GitLab's authorized apps section. **Requirements** * Ensure to log in with an account possessing write permissions to relevant GitLab repositories. * Write permissions are mandatory for webhook publication, facilitating real-time data sync. **Best Practice** * Opt for a service account rather than an individual-linked account. * Service accounts are typically overseen by the company's admin. **Create your Hivel Account** 1. Navigate to the Hivel [sign-up pagearrow-up-right](https://app.hivel.ai/signup) 2. Add your work email id. 3. Now, you can use your Google or Microsoft login with your work email id; or create a password. 4. Create your Company Profile, and click '**Get Started**'. 5. Once you've successfully created your Company Profile, you will be redirected to the Integrations Page. 6. Select GitLab, and log in to your company's GitLab account using a service account. **Connect GitLab** 1. Next, you will be redirected to Hivel and prompted to add a **Personal Access Token.** 2. To create a Personal Access Token, return to your GitLab account, and in the top-right corner, click your avatar. 3. Select **Preferences** 4. On the left sidebar, select **Access Tokens**. 5. Enter a name, and do not set any expiry date for the token. 6. Select the [desired scopesarrow-up-right](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#personal-access-token-scopes) - api, read\_api, read\_user, read\_repository 7. Select **Create personal access token**, and copy it. 8. Return to the Hivel application, paste the personal access token, and hit **Submit**. Once the token is validated, and your GitLab is successfully integrated, we will start to pull data. It will take between 2 - 48 hours for the complete sync, depending on the volume of the data. **Below are some screenshots of the steps you can refer to if needed:** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FEgtVdyFeQ6ZOHMXUsUdX%252Fimage.png%3Falt%3Dmedia%26token%3D99e16bfc-989c-4161-99ae-1b351832b329&width=768&dpr=3&quality=100&sign=d43d387&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F9Al1RETLnRQZ4jI3yVlL%252Fimage%2520%2820%29.png%3Falt%3Dmedia%26token%3D6497821d-9343-48c0-9151-01eb6a9ccb06&width=768&dpr=3&quality=100&sign=f1c39fb7&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FdejuQx5xvnK79sqk8SYq%252Fimage%2520%2821%29.png%3Falt%3Dmedia%26token%3D50e0fdff-46ea-40d1-ba37-f2869e69131b&width=768&dpr=3&quality=100&sign=d3da3fb2&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FIfGHZJHIeObwoc1LdWPc%252Fimage%2520%2822%29.png%3Falt%3Dmedia%26token%3D840f3ed7-cbef-476f-8dd0-9ac00d19a701&width=768&dpr=3&quality=100&sign=daf29f07&sv=2) [PreviousGitlab Serverchevron-left](https://docs.hivel.ai/integrations/scm/gitlab/gitlab-server) [NextHow to ensure Gitlab token has access to required groups/repositorieschevron-right](https://docs.hivel.ai/integrations/scm/gitlab/how-to-ensure-gitlab-token-has-access-to-required-groups-repositories) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon --- # DORA Metrics Powered by New APIs in Hivel | Hivel We’ve launched two new APIs - Deployment API and Incident API - to improve how DORA metrics are calculated in Hivel. These updates make the metrics more accurate, reliable, and real-time, giving you better insights into your team’s delivery and reliability. With these new APIs, you can now integrate Hivel with any tool in your workflow, and the DORA metrics will be calculated consistently based on real-time data. [hashtag](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel#whats-changed) What’s Changed? -------------------------------------------------------------------------------------------------------------------------------------------- ### [hashtag](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel#new-api-powered-dora-metrics) New API-Powered DORA Metrics With the launch of the new APIs, we’ve introduced new API-powered DORA metrics for even greater accuracy. These metrics give you real-time visibility into your delivery pipeline: Metric What It Means Data Source Change Failure Rate (CFR) The percentage of deployments that result in a failure. Incident API Mean Time to Restore (MTTR) The time taken to restore a service from a production failure. Incident API Deployment Frequency (DF) The number of times that code changes are successfully deployed to production. Deployment API Delivery Lead Time The time from code commit to successful deployment in production. Deployment API #### [hashtag](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel#weve-also-renamed-some-of-the-older-dora-metrics-to-reflect-this-update.-heres-a-quick-look) We’ve also renamed some of the older DORA metrics to reflect this update. Here’s a quick look: Old Name New Name What It Means CFR (Change Failure Rate) Hotfix Rate PRs merged to release branches with the hotfix pattern as configured. MTTR (Mean Time to Restore) Hotfix Resolution Time Cycle time of all PRs merged to release branches with the hotfix pattern as configured. Deployment Frequency Release Merge Frequency No. of PRs merged to release branches as per configuration. [hashtag](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel#how-to-enable-these-metrics) How to Enable These Metrics ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- To start viewing the new API-powered DORA metrics, make sure you’ve connected both the Deployment API and Incident API to your workspace. 1. In Hivel application navigate to Integrations → **CI/CD Section** 2. Connect the Deployment API for the following metrics: 1. Deployment Frequency 2. Delivery Lead Time 👉 [View Integration Guidearrow-up-right](https://docs.hivel.ai/integrations/api-documentation/deployment-events-api) 3. Connect the Incident API for the following metrics: 1. Hotfix Rate 2. Hotfix Resolution Time 👉 [View Integration Guidearrow-up-right](https://docs.hivel.ai/integrations/api-documentation/create-incident-api) Once the APIs are connected, your DORA metrics will automatically update with data from these integrations. [hashtag](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel#where-youll-see-these-changes) Where You’ll See These Changes --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The newly calculated DORA metrics will appear wherever DORA metrics are displayed. For areas that previously used the old calculation method, you’ll now see the renamed metrics. Here’s where the changes apply: 1. **Cockpit** 1. The DORA DASHBOARD - NEW board will include the metrics powered from Deployment and Incident API 2. The old metrics will appear in other boards renamed to Hotfix Rate, Hotfix Resolution Time, Release Merge Frequency. 3. These changes will be reflected in all the dashboards, graphical and tabular views 2. **PR Screen** 1. In the Pull Request screen, the top-level metric cards have been renamed to match the updated terminology. 2. They now align with the same logic used in the Cockpit, providing consistency across views. [hashtag](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel#why-this-change-matters) Why This Change Matters -------------------------------------------------------------------------------------------------------------------------------------------------------------- By using the Deployment API and Incident API, DORA metrics in Hivel are now more accurate, real-time, and consistent across tools. You can integrate any tool with Hivel, and your metrics will follow a standard calculation method every time. The renamed old metrics remain available for those who prefer the earlier approach, while the new APIs ensure your DORA insights stay aligned with modern engineering practices. [PreviousCreate Incident APIchevron-left](https://docs.hivel.ai/integrations/api-documentation/create-incident-api) [NextOn-Prem Setupchevron-right](https://docs.hivel.ai/integrations/on-prem-setup) Last updated 4 months ago * [What’s Changed?](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel#whats-changed) * [New API-Powered DORA Metrics](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel#new-api-powered-dora-metrics) * [How to Enable These Metrics](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel#how-to-enable-these-metrics) * [Where You’ll See These Changes](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel#where-youll-see-these-changes) * [Why This Change Matters](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel#why-this-change-matters) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to integrate GitHub with account wide access? | Hivel #### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-account-wide-access#data-access-by-hivel) Data Access by Hivel * Hivel accesses the past 60-90 days of commits and pull requests from active repositories during the initial sync. #### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-account-wide-access#authorization-mechanism) Authorization Mechanism * Hivel employs GitHub's OAuth for authentication. * Users maintain full control and can withdraw access anytime via GitHub's authorized apps section. #### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-account-wide-access#requirements) Requirements * Ensure to log in with an account possessing write permissions to relevant GitHub repositories. * Write permissions are mandatory for webhook publication, facilitating real-time data sync. #### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-account-wide-access#best-practice) Best Practice * Opt for a service account rather than an individual-linked account. * Service accounts are typically overseen by the company's admin. **Permissions Required** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FfuGFYrIfn5oKmyDnw7jx%252Fimage.png%3Falt%3Dmedia%26token%3D0c265b13-9ca8-453d-aac0-66fa167d5b25&width=768&dpr=3&quality=100&sign=1b6c22aa&sv=2) circle-check **You can either create a service account or use one with access to only the required workspaces.** ### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-account-wide-access#how-to-create-a-service-account-and-give-access-to-the-required-workspaces) How to create a service account and give access to the required workspaces circle-info Skip this section if you are using an existing account with required access. 1. Sign up on [github.comarrow-up-right](https://github.com/) using a generic email ID which does not belong to any developer and can be accessed by the admin. 2. Once created, open the required workspace using an admin account. 3. Under **People** section, click on **Invite member** to invite the newly created service account. 4. Do the same for **all the required workspaces**. 5. Once invited, log into the account mail and **accept the invite**. This will give the service account permission for only the required workspaces. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDmotpSsSvrB8r1MBb0T5%252Fimage.png%3Falt%3Dmedia%26token%3Dc92a0ff2-6213-4940-bce6-63d9ae5057d8&width=768&dpr=3&quality=100&sign=4ce3bf79&sv=2) ### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-account-wide-access#sign-in-to-hivel) **Sign in to Hivel** 1. Navigate to the Hivel [sign-up pagearrow-up-right](https://app.hivel.ai/signup) 2. Add your work email id (If you'd like to use your personal email id please contact [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#7a090f0a0a15080e3a12130c1f16541b13) 3. Now, you can use your Google or Microsoft login with your work email id; or create a password. 4. Create your Company Profile, and click '**Get Started**'. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FfVfy42xatexMl1W1PPI9%252Fimage.png%3Falt%3Dmedia%26token%3Df9f44662-e81f-4b21-b7cf-8704c7a24322&width=768&dpr=3&quality=100&sign=71c8eb56&sv=2) 5. Once you've successfully created your Company Profile you will be redirected to the Integrations Page under **Settings.** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FnJ0BKgHQiKefu7VRE9lr%252Fimage.png%3Falt%3Dmedia%26token%3Dee8a5e0a-82a8-4cc0-9baa-5aa656b52b74&width=768&dpr=3&quality=100&sign=e622d9fa&sv=2) 6. Select GitHub, and use your company's GitHub account (**either service account or the account which has access to the required workspaces**). 7. Click on **Connect.** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FUQAoNSCeIcGUzlnNLtbP%252Fimage.png%3Falt%3Dmedia%26token%3D4ba1f406-10f8-4eaa-ac5f-5a91dbb7d506&width=768&dpr=3&quality=100&sign=535b945c&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDxJ4nfVPl7dPBiS9zIor%252Fimage.png%3Falt%3Dmedia%26token%3D2527cee4-5417-47f8-b07f-cbf97f74ec00&width=768&dpr=3&quality=100&sign=fd151182&sv=2) 8. Click '**Integrate Github**' . 9. Make sure you click on '**Gran**t' all the organization you want to integrate with Hivel. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FhqkNBgy8OVtUGxOWy10H%252Fimage.png%3Falt%3Dmedia%26token%3D31cb29df-456e-4635-a852-fe8950a24d72&width=768&dpr=3&quality=100&sign=86328a10&sv=2) 10. After authorization, you'll be redirected back to Hivel. Once your GitHub is successfully integrated, we will start to pull data. It will take between 2 - 48 hours for the complete sync, depending on the volume of the data. [PreviousGitHubchevron-left](https://docs.hivel.ai/integrations/scm/github) [NextHow to re-authorize / re-initiate GitHub integration with account wide access?chevron-right](https://docs.hivel.ai/integrations/scm/github/how-to-re-authorize-re-initiate-github-integration-with-account-wide-access) Last updated 7 months ago * [How to create a service account and give access to the required workspaces](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-account-wide-access#how-to-create-a-service-account-and-give-access-to-the-required-workspaces) * [Sign in to Hivel](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-account-wide-access#sign-in-to-hivel) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to integrate GitHub with repository level access? | Hivel #### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-repository-level-access#data-access-by-hivel) Data Access by Hivel * Hivel accesses the past 60-90 days of commits and pull requests from active repositories during the initial sync. #### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-repository-level-access#authorization-mechanism) Authorization Mechanism * In this method, Hivel uses the GitHub app flow for the integration * Users maintain full control and can withdraw access anytime via GitHub's authorized apps section. #### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-repository-level-access#requirements) Requirements * Ensure to log in with an account possessing write permissions to relevant GitHub repositories. * Write permissions are mandatory for webhook publication, facilitating real-time data sync. #### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-repository-level-access#best-practice) Best Practice * Opt for a service account rather than an individual-linked account. * Service accounts are typically overseen by the company's admin. **Permissions Required** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FABRVnlQnvDwT3ruSrAO8%252Fimage.png%3Falt%3Dmedia%26token%3D76b2eea4-8e43-4bc4-a2c1-c2306d331969&width=768&dpr=3&quality=100&sign=1cc366b9&sv=2) circle-check **You can either create a service account or use one with access to only the required workspaces.** ### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-repository-level-access#how-to-create-a-service-account-and-give-access-to-the-required-workspaces) How to create a service account and give access to the required workspaces circle-info Skip this section if you are using an existing account with required access. 1. Sign up on [github.comarrow-up-right](https://github.com/) using a generic email ID which does not belong to any developer and can be accessed by the admin. 2. Once created, open the required workspace using an admin account. 3. Under **People** section, click on **Invite member** to invite the newly created service account. 4. Do the same for **all the required workspaces**. 5. Once invited, log into the account mail and **accept the invite**. This will give the service account permission for only the required workspaces. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDmotpSsSvrB8r1MBb0T5%252Fimage.png%3Falt%3Dmedia%26token%3Dc92a0ff2-6213-4940-bce6-63d9ae5057d8&width=768&dpr=3&quality=100&sign=4ce3bf79&sv=2) ### [hashtag](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-repository-level-access#sign-in-to-hivel) **Sign in to Hivel** 1. Navigate to the Hivel [sign-up pagearrow-up-right](https://app.hivel.ai/signup) 2. Add your work email id (If you'd like to use your personal email id please contact [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#afdcdadfdfc0dddbefc7c6d9cac381cec6) 3. Now, you can use your Google or Microsoft login with your work email ID, or create a password. 4. Create your Company Profile, and click '**Get Started**'. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FfVfy42xatexMl1W1PPI9%252Fimage.png%3Falt%3Dmedia%26token%3Df9f44662-e81f-4b21-b7cf-8704c7a24322&width=768&dpr=3&quality=100&sign=71c8eb56&sv=2) 5. Once you've successfully created your Company Profile you will be redirected to the Integrations Page under **Settings.** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FnJ0BKgHQiKefu7VRE9lr%252Fimage.png%3Falt%3Dmedia%26token%3Dee8a5e0a-82a8-4cc0-9baa-5aa656b52b74&width=768&dpr=3&quality=100&sign=e622d9fa&sv=2) 6. Select GitHub, and use your company's GitHub account (**either service account or the account which has access to the required workspaces**). 7. Click on **Connect.** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FUQAoNSCeIcGUzlnNLtbP%252Fimage.png%3Falt%3Dmedia%26token%3D4ba1f406-10f8-4eaa-ac5f-5a91dbb7d506&width=768&dpr=3&quality=100&sign=535b945c&sv=2) 8. Select **"Repository-level Access"** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FXXgJEQ9Dot4A7BHWRdrW%252Fimage.png%3Falt%3Dmedia%26token%3D9a2a513f-8e46-42d6-ae24-c5fb07043a05&width=768&dpr=3&quality=100&sign=29d18fee&sv=2) 9. You will be redirected to the Github app installation page where you have to click on **"Install"** for the Hivel app. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FCq09HXVFl6P3WsU4rl1V%252Fimage.png%3Falt%3Dmedia%26token%3Da2b21731-5919-4164-89a8-e48135e7094b&width=768&dpr=3&quality=100&sign=427a8699&sv=2) 10. Select the org where you want to integrate Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FLP5apfvYnVDl5ueb9wmw%252Fimage.png%3Falt%3Dmedia%26token%3Df5924cae-b659-4814-a53d-ec70cbdd87c1&width=768&dpr=3&quality=100&sign=bcb38c30&sv=2) 11. You can either select to give access to all repositories or a few select repositories as required. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fbojnf2r0vYiSxg9B2UkW%252Fimage.png%3Falt%3Dmedia%26token%3De3fa83c2-f8fb-49e6-9210-80c06cebf92a&width=768&dpr=3&quality=100&sign=970708b5&sv=2) 12. Click '**Install & Authorize'**. 13. After authorization, you'll be redirected back to Hivel. Once your GitHub is successfully integrated, we will start to pull data. It will take between 2 - 48 hours for the complete sync, depending on the volume of the data. [PreviousHow to re-authorize / re-initiate GitHub integration with repository level access?chevron-left](https://docs.hivel.ai/integrations/scm/github/how-to-re-authorize-re-initiate-github-integration-with-repository-level-access) [NextAlternate methodschevron-right](https://docs.hivel.ai/integrations/scm/github/alternate-methods) Last updated 6 months ago * [How to create a service account and give access to the required workspaces](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-repository-level-access#how-to-create-a-service-account-and-give-access-to-the-required-workspaces) * [Sign in to Hivel](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-repository-level-access#sign-in-to-hivel) sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Notes - October 2025 | Hivel October’s updates are all about **clarity and control**. From knowing exactly how fresh your data is, to drilling into commits behind every sprint, to tracking rework vs new work goals - these changes help you make faster, data-backed decisions with full context. #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-october-2025#know-exactly-when-your-data-was-last-synced) **Know Exactly When Your Data Was Last Synced** A new **“Last Date Refreshed”** label now appears on every integration card, so you can instantly see when your data last synced. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F3Fv2oxwOW4DJK2gAviTn%252FScreenshot%25202025-11-07%2520at%25202.48.07%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D5af742ab-41a7-4894-a832-c6e08d23b41b&width=768&dpr=3&quality=100&sign=3a388853&sv=2) You don't need to guess anymore if your Git or PM tool is up to date. If it hasn’t refreshed in a week, you’ll see: > _“Data refreshed more than a week ago. Please contact support.”_ This helps you catch stale data early and keep your dashboards reliable. **Works with:** GitHub, GitLab, Bitbucket, Azure, Jira, Freshrelease, Cursor, Copilot, Sonar, Google Calendar, and Outlook Calendar. 👉 [**Check it out**arrow-up-right](https://app.hivel.ai/settings/integrations) #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-october-2025#go-deeper-in-the-investment-screen) **Go Deeper in the Investment Screen** The **Investment** screen now lets you open up what’s behind the numbers. Both **PR counts** and **commit counts** are clickable, so you can jump straight from a metric to the actual work that drove it. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FsRSNKJKOkYQcMVBXosGr%252FScreenshot%25202025-11-07%2520at%25202.52.21%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D1a8571d2-ffd7-4aef-b42f-5119256d5627&width=768&dpr=3&quality=100&sign=4d4435fb&sv=2) Perfect for sprint reviews or team retros when you want to connect outcomes to the effort that went into them. **Available for:** Jira Cloud, Jira Server, Azure, and Freshrelease users. 👉 [**Try it out**arrow-up-right](https://app.hivel.ai/dashboard/investment-profile) #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-october-2025#goals-pro-now-tracks-new-work-and-rework) **Goals PRO Now Tracks New Work and Rework** We’ve added **New Work** and **Rework** metrics to **Goals PRO**, to help you see how your teams balance building new features vs fixing or maintaining existing ones. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FhNfLTnY1w8d9lhRMJZkM%252FScreenshot%25202025-11-07%2520at%25202.56.17%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D2afe6b45-477c-4538-81cf-7c1faa59f04c&width=768&dpr=3&quality=100&sign=8c5337d&sv=2) You can now set more meaningful targets, like reducing rework over time or increasing the share of new work in a sprint. 👉 [**Explore it now**arrow-up-right](https://app.hivel.ai/dashboard/goals) #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-october-2025#wrapping-up-october) ☕ **Wrapping Up October** Hope this month’s updates help you with sharper visibility, up-to-date data, and metrics that tell a fuller story. As the year winds down, remember this: sustainable pace beats sprinting to burnout. So take a breather, review your wins, and let the data guide your next move. Here’s to finishing 2025 strong 💪✨ [PreviousRelease Notes - November 2025chevron-left](https://docs.hivel.ai/release-notes/release-notes-november-2025) [NextRelease Notes - September 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-september-2025) Last updated 2 hours ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Strategies to Reduce Hotfix Resolution Time | Hivel [Hotfix Resolution Time](https://docs.hivel.ai/metrics-and-definitions/quality/hotfix-resolution-time) is the average time taken to resolve any bugs or push hotfixes to production. Here are some actionable strategies to reduce the average cycle time for hotfix PRs, ensuring quick resolution of production bugs and maintaining system reliability: ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-1.-create-a-rapid-code-review-process-for-hotfix-prs) **1\. Create a Rapid Code Review Process for Hotfix PRs** * **Why It's Important**: Code reviews can become bottlenecks. Streamlining this process for hotfixes ensures that fixes are approved and merged quickly. * **Impact**: Speeds up the transition from code completion to deployment, reducing waiting times in the pipeline. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-2.-automate-testing-and-deployment-pipelines-for-hotfixes) **2\. Automate Testing and Deployment Pipelines for Hotfixes** * **Why It's Important**: Automation eliminates manual steps that can introduce delays and errors. Automated pipelines validate and deploy hotfixes swiftly. * **Impact**: Significantly cuts down the time between code submission and deployment to production. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-3.-enhance-logging-monitoring-and-alerting-systems) **3\. Enhance Logging, Monitoring, and Alerting Systems** * **Why It's Important**: Quickly identifying and diagnosing issues is half the battle. Enhanced observability tools help teams pinpoint problems faster. * **Impact**: Reduces the time spent on root cause analysis, allowing fixes to be developed sooner. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-4.-establish-a-dedicated-hotfix-workflow) **4\. Establish a Dedicated Hotfix Workflow** * **Why It's Important**: A separate workflow for hotfixes prevents interference with ongoing development and simplifies the process. * **Impact**: Streamlines the hotfix process, reducing complexity and potential delays. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-5.-implement-feature-flags-and-toggle-systems) **5\. Implement Feature Flags and Toggle Systems** * **Why It's Important**: Feature flags allow you to disable problematic features immediately without a full deployment. * **Impact**: Provides an immediate mitigation strategy, reducing the urgency and pressure on the hotfix cycle. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-6.-maintain-an-up-to-date-knowledge-base-and-runbooks) **6\. Maintain an Up-to-Date Knowledge Base and Runbooks** * **Why It's Important**: Documentation of previous issues and solutions aids in faster troubleshooting. * **Impact**: Decreases the time engineers spend figuring out fixes by leveraging existing knowledge. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-7.-conduct-regular-post-incident-reviews-and-implement-improvements) **7\. Conduct Regular Post-Incident Reviews and Implement Improvements** * **Why It's Important**: Learning from past incidents helps identify process weaknesses. * **Impact**: Leads to continuous improvement, gradually reducing cycle times over the long term. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-8.-allocate-buffer-time-in-sprints-for-unplanned-work) **8\. Allocate Buffer Time in Sprints for Unplanned Work** * **Why It's Important**: Recognizing that unplanned work will occur allows teams to handle it without derailing planned tasks. * **Impact**: Ensures that hotfixes can be addressed promptly without significant impact on other deliverables. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#summary-of-priorities) **Summary of Priorities**: * **Immediate Response**: Start by ensuring that issues are addressed as soon as they occur. * **Process Efficiency**: Streamline the processes that get fixes from development to production quickly. * **Effective Communication**: Keep everyone informed and coordinated to prevent delays. * **Preventative Measures**: Use tools and practices that minimize the need for hotfixes or mitigate their impact. * **Continuous Improvement**: Learn from each incident to improve future responses. By prioritizing and focusing on these strategies, you'll address the most critical factors that impact the cycle time of hotfix PRs. Implementing them will lead to faster resolution of production bugs and a more resilient system overall. [PreviousBest Practices for Ensuring Strong Pull Request Review Coveragechevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage) [NextBest Practices for Team Ownership in Code Reviewchevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review) Last updated 3 months ago * [1\. Create a Rapid Code Review Process for Hotfix PRs](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-1.-create-a-rapid-code-review-process-for-hotfix-prs) * [2\. Automate Testing and Deployment Pipelines for Hotfixes](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-2.-automate-testing-and-deployment-pipelines-for-hotfixes) * [3\. Enhance Logging, Monitoring, and Alerting Systems](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-3.-enhance-logging-monitoring-and-alerting-systems) * [4\. Establish a Dedicated Hotfix Workflow](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-4.-establish-a-dedicated-hotfix-workflow) * [5\. Implement Feature Flags and Toggle Systems](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-5.-implement-feature-flags-and-toggle-systems) * [6\. Maintain an Up-to-Date Knowledge Base and Runbooks](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-6.-maintain-an-up-to-date-knowledge-base-and-runbooks) * [7\. Conduct Regular Post-Incident Reviews and Implement Improvements](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-7.-conduct-regular-post-incident-reviews-and-implement-improvements) * [8\. Allocate Buffer Time in Sprints for Unplanned Work](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time#id-8.-allocate-buffer-time-in-sprints-for-unplanned-work) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to re-authorize / re-initiate GitHub integration with repository level access? | Hivel Hivel currently only supports GitHub accounts that are associated with an organization. Often, this step is missed when setting up a GitHub account, and you may have run into an error when creating an account on Hivel. When you encounter this error during the initial process, we recommend you follow the below steps to create an organization and link your current users to the organization. To re-initiate/reauthorize GitHub integration with Hivel, follow these steps: 1. Log in to your GitHub account. 2. Revoke the Hivel app access from your GitHub account by going to **Settings** > **Account Settings** > **Third Party apps** > **GitHub apps** \> **Hivel**. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FcteoWfRBaqHlWm9Vdnyn%252Fimage.png%3Falt%3Dmedia%26token%3Dcc9ee32c-2e1d-40dc-9508-d794927394c6&width=768&dpr=3&quality=100&sign=7d8b0a53&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FUwzhvjlXRSzcMmYx3rk5%252Fimage.png%3Falt%3Dmedia%26token%3D1b1b3c19-04cc-4fe2-99a2-083b55865540&width=768&dpr=3&quality=100&sign=393d94ab&sv=2) 3. Click on **Configure** -> Scroll down and **uninstall** the app. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FfmZrATleOdb5uBDuYPG5%252Fimage.png%3Falt%3Dmedia%26token%3Db7ee2f2c-fda4-48bd-a1d3-520c5ecaef89&width=768&dpr=3&quality=100&sign=14d88dda&sv=2) 4. Return to your Hivel account. Go to **Settings > Integrations**. You will see a "**Reauthorize**" button on the GitHub card. (If you're not able to see it, please reach out to [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#87f4f2f7f7e8f5f3c7efeef1e2eba9e6ee) ) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fy5wce2u7JLmBK47b8ORs%252Fimage.png%3Falt%3Dmedia%26token%3D9f39c82b-ff80-4836-bc11-8ee4d4d4686a&width=768&dpr=3&quality=100&sign=cdba05a1&sv=2) 1. Select **"Repository-level Access"** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FXXgJEQ9Dot4A7BHWRdrW%252Fimage.png%3Falt%3Dmedia%26token%3D9a2a513f-8e46-42d6-ae24-c5fb07043a05&width=768&dpr=3&quality=100&sign=29d18fee&sv=2) 2. You will be redirected to the Github app installation page where you have to click on **"Install"** for the Hivel app. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FCq09HXVFl6P3WsU4rl1V%252Fimage.png%3Falt%3Dmedia%26token%3Da2b21731-5919-4164-89a8-e48135e7094b&width=768&dpr=3&quality=100&sign=427a8699&sv=2) 3. Select the org where you want to integrate Hivel ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FLP5apfvYnVDl5ueb9wmw%252Fimage.png%3Falt%3Dmedia%26token%3Df5924cae-b659-4814-a53d-ec70cbdd87c1&width=768&dpr=3&quality=100&sign=bcb38c30&sv=2) 4. You can either select to give access to all repositories or a few select repositories as required. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fbojnf2r0vYiSxg9B2UkW%252Fimage.png%3Falt%3Dmedia%26token%3De3fa83c2-f8fb-49e6-9210-80c06cebf92a&width=768&dpr=3&quality=100&sign=970708b5&sv=2) 5. Click '**Install & Authorize'**. 6. After authorization, you'll be redirected back to Hivel. [PreviousHow to re-authorize / re-initiate GitHub integration with account wide access?chevron-left](https://docs.hivel.ai/integrations/scm/github/how-to-re-authorize-re-initiate-github-integration-with-account-wide-access) [NextHow to integrate GitHub with repository level access?chevron-right](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-repository-level-access) Last updated 6 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to re-authorize / re-initiate GitHub integration with account wide access? | Hivel Hivel currently only supports GitHub accounts that are associated with an organization. Often, this step is missed when setting up a GitHub account, and you may have run into an error when creating an account on Hivel. When you encounter this error during the initial process, we recommend you follow the below steps to create an organization and link your current users to the organization. To re-initiate/reauthorize GitHub integration with Hivel, follow these steps: 1. Log in to your GitHub account. 2. Revoke the Hivel app access from your GitHub account by going to **Settings** > **Account Settings** > **Applications** > **Authorized OAuth Apps** \> **Hivel**. Then click "**Revoke"**. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FmdmKmvrBd42oy7MFJV3D%252Fimage%2520%28115%29.png%3Falt%3Dmedia%26token%3D1b8b6811-455b-4a40-862b-fe0c34a214c2&width=768&dpr=3&quality=100&sign=3d0dc8d4&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FnHONk4pl0tBPIeNJKemM%252Fimage%2520%28116%29.png%3Falt%3Dmedia%26token%3D9eed5aca-8c57-4b80-bf37-97ccdbd3c242&width=768&dpr=3&quality=100&sign=c16dad20&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FYgCOafHi69Z2f8DAof53%252Fimage%2520%28117%29.png%3Falt%3Dmedia%26token%3D31e89b39-bbee-44b2-bdc5-2037593b76d1&width=768&dpr=3&quality=100&sign=2bda332d&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdO0aQ1F_fo-mKURqlUU_hC6mYFRamiPBEEjh1M-84GVDUza2ZEyW5KF-JNp6VYEr3VcB7AcNl8MANHvHG6VKPqaU7ccqGpxxzgdsoDh9NNpa4Uuhsz9Mli6-wxbMZslfwTVgw5PXsaDudUVyQaAfCLzuA%3Fkey%3D7e-FYm3-NHwQUjNXOPEkIw&width=768&dpr=3&quality=100&sign=45133139&sv=2) 1. Return to your Hivel account. Go to **Settings > Integrations**. You will see a "**Reauthorize**" button on the GitHub card. (If you're not able to see it, please reach out to [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#a2d1d7d2d2cdd0d6e2cacbd4c7ce8cc3cb) ) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fy5wce2u7JLmBK47b8ORs%252Fimage.png%3Falt%3Dmedia%26token%3D9f39c82b-ff80-4836-bc11-8ee4d4d4686a&width=768&dpr=3&quality=100&sign=cdba05a1&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FuZgq9AEy8MYSnDIflwh1%252Fimage%2520%2873%29.png%3Falt%3Dmedia%26token%3D6b575045-de0a-4859-936b-9fcc26dda88f&width=768&dpr=3&quality=100&sign=440643ef&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F3mdu2qUjoQ189qhFBiRk%252Fimage.png%3Falt%3Dmedia%26token%3D27f15d3f-beb9-4b3d-b31a-114695e0f119&width=768&dpr=3&quality=100&sign=402cc4bc&sv=2) circle-info To include GitHub Copilot usage data as part of the token integration, check the **"Include GitHub Copilot usage data"** in this last step. circle-info **The final step below can be easily missed, but it is very important!** `Authorize your organization's access by clicking on "``**Grant**``" against your organization.` [PreviousHow to integrate GitHub with account wide access?chevron-left](https://docs.hivel.ai/integrations/scm/github/how-to-integrate-github-with-account-wide-access) [NextHow to re-authorize / re-initiate GitHub integration with repository level access?chevron-right](https://docs.hivel.ai/integrations/scm/github/how-to-re-authorize-re-initiate-github-integration-with-repository-level-access) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # How to integrate Jira Server with Hivel | Hivel ### [hashtag](https://docs.hivel.ai/integrations/project-management/jira/how-to-integrate-jira-server-with-hivel#before-starting-integration-make-sure-to-whitelist-the-following-ip-addresses) Before starting integration, make sure to whitelist the following IP addresses: * **Recommended, but Optional IPs**: * 45.119.114.218 * 183.82.116.218 * **Mandatory IPs**: * 107.23.139.76 * 3.219.89.23 ### [hashtag](https://docs.hivel.ai/integrations/project-management/jira/how-to-integrate-jira-server-with-hivel#to-start-the-integration-follow-the-below-steps) To start the integration, follow the below steps: 1. Log in to your Hivel account. 2. In the left panel, select **Settings**, and go to the **Integrations** tab. 3. Find the Jira card and click the **'Connect'** button. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fzhy3HFBOwDRS8H4m0C0P%252Fimage.png%3Falt%3Dmedia%26token%3Deec1abce-ecf2-46e6-8c73-5b9d1c273c71&width=768&dpr=3&quality=100&sign=8a569975&sv=2) 4. In the pop-up, paste the link of your Jira domain and press "Enter" key. A link to Jira application page will be generated. Click on the link. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F3pt2idXkj8V5tRXMo2Ph%252Fimage.png%3Falt%3Dmedia%26token%3D73b0e2a0-0cff-437c-a1a4-604fed42b8c9&width=768&dpr=3&quality=100&sign=871e78c2&sv=2) 5. You'll be redirected to your Jira account. Click on **Create Link.** 6. Select **Direct Application Link** and paste our application's link - [https://app.hivel.aiarrow-up-right](https://app.hivel.ai/dashboard/cto) . Click on continue. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FIchDsFQAUqPThzOScS5b%252Fimage.png%3Falt%3Dmedia%26token%3Df63f0fa6-e496-4018-937d-30a0884fdda3&width=768&dpr=3&quality=100&sign=66635b20&sv=2) 7. Copy the **Application Name** from Hivel's integration page and paste in the recent pop-up in Jira. Select **Application Type** as "Generic Application". Click on continue. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FKtQr7pDrojLvcSLd8ZNJ%252Fimage.png%3Falt%3Dmedia%26token%3D426e32bf-6f97-49bb-9184-45859797ffa2&width=768&dpr=3&quality=100&sign=b73369c&sv=2) _From Hivel's integration page_ ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F7w6tf9QHwfAJXPABnBe2%252Fimage.png%3Falt%3Dmedia%26token%3Dcf768d90-4c3b-4527-84fc-2b34f1185d69&width=768&dpr=3&quality=100&sign=c627dc55&sv=2) _Jira pop-up_ 8. A new entry will be added in the Jira Application Link page. Click on the 3 dots in the new entry and select Configure. 9. Go to **Incoming Authentication.** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fr5nxvIffcbujOeJ6hmF6%252Fimage.png%3Falt%3Dmedia%26token%3D4df9488d-d269-44ff-9413-f6c32ed8f620&width=768&dpr=3&quality=100&sign=e69e6963&sv=2) 10. Copy the **Consumer Key**, **Consumer Name**, **Public Key**, and **Redirection Link** from Hivel integration page and paste in the Incoming Authentication tab in Jira. Then, hit “Save”. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FrEIojpX1k7VAzrX7uFVk%252Fimage.png%3Falt%3Dmedia%26token%3D876b9329-166d-462c-8ed6-7bba936fea05&width=768&dpr=3&quality=100&sign=28cc1694&sv=2) 11. Go back to the Hivel's integration page and click on **Submit.** In case an error pops up, please repeat the above processes again. If everything is set up correctly, it will get connected. Done! Data will be refreshed within 24 hours. circle-info _**Note:**_ Make sure to connect Jira with the **admin account**. For any issues or assistance, feel free to reach us at [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#ddaea8adadb2afa99db5b4abb8b1f3bcb4) . [PreviousHow to Re-authorize Jira with OAuth 2.0chevron-left](https://docs.hivel.ai/integrations/project-management/jira/how-to-re-authorize-jira-with-oauth-2.0) [NextAzure Boardschevron-right](https://docs.hivel.ai/integrations/project-management/azure-boards) Last updated 1 year ago * [Before starting integration, make sure to whitelist the following IP addresses:](https://docs.hivel.ai/integrations/project-management/jira/how-to-integrate-jira-server-with-hivel#before-starting-integration-make-sure-to-whitelist-the-following-ip-addresses) * [To start the integration, follow the below steps:](https://docs.hivel.ai/integrations/project-management/jira/how-to-integrate-jira-server-with-hivel#to-start-the-integration-follow-the-below-steps) sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Notes - February 2025 | Hivel February brought some exciting updates that we’re sure your teams will love! #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-february-2025#jenkins-pipeline-metrics-is-now-live) **Jenkins - Pipeline Metrics is Now Live!** We’re thrilled to introduce the **Jenkins Pipelines Metrics** feature, now live in production! You can track Jenkins success and failed builds directly from your Custom Dashboards page under _Pipeline Metrics_. Plus, you’ll also see the average build run duration. Not yet set up? No worries - follow the [_steps to integrate Jenkins_arrow-up-right](https://docs.hivel.ai/integrations/jenkins) and start tracking today. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FIfg9cAaYGZEvrbcwG9Ww%252FScreen%2520Cast%25202025-04-01%2520at%25202.51.50%2520PM.gif%3Falt%3Dmedia%26token%3D72847cf9-862e-4770-ae17-9a345369ec09&width=768&dpr=3&quality=100&sign=1abf4b96&sv=2) #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-february-2025#rbac-role-based-access-control) **RBAC (Role-Based Access Control)** Managing user permissions just became a breeze with our new **RBAC system**. You can now define roles and assign permissions effortlessly, including access to specific screens, editing configurations, excluding PRs, and more. If user access control is a priority for your team, this update is a must-check! [_Link to RBAC configurations_arrow-up-right](https://app.hivel.ai/settings/rbac) And that’s it for February - two major updates to streamline your workflow. **Time to refactor your permissions... and maybe your work-life balance too!** ⚙️🧘‍♂️ [PreviousRelease Notes - March 2025chevron-left](https://docs.hivel.ai/release-notes/release-notes-march-2025) [NextRelease Notes - January 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-january-2025) Last updated 11 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Best Practices for Team Ownership in Code Review | Hivel Effective code review practices are vital for maintaining high-quality code and fostering a culture of collaboration and learning within development teams. Here are some best practices for promoting team ownership in the code review process: ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#define-clear-ownership-and-responsibilities) **Define clear ownership and responsibilities** * Establish clear ownership of different modules or features within the team. Each team member should know their responsibilities and the areas of the codebase they own. * This clarity helps ensure that the right individuals are reviewing changes to the code they are most familiar with, leading to more effective and efficient reviews. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#implement-a-peer-review-system) **Implement a peer review system** * Encourage a peer review system where every piece of code must be reviewed by one or more team members before merging. * Peer reviews not only improve code quality and catch errors early but also enhance team collaboration and knowledge sharing. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#use-automated-tools) **Use automated tools** * Leverage automated code review tools (like SonarQube, CodeClimate, or GitHub’s built-in tools) to handle basic code quality checks, style enforcement, and security scans. * Automation frees human reviewers to focus on more complex aspects of the code, such as architecture and design principles, rather than syntax errors or style inconsistencies. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#establish-review-standards-and-checklists) **Establish review standards and checklists** * Develop and maintain a code review checklist that includes both general and project-specific criteria to be checked during the review. * Checklists standardize the review process and help ensure completeness in the review, reducing the chance of missing key issues. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#promote-constructive-feedback) **Promote constructive feedback** * Encourage reviewers to provide constructive, specific, and respectful feedback. Comments should be clear and actionable. * Positive and constructive feedback enhances learning and keeps the review process from becoming adversarial, fostering a supportive team environment. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#encourage-pair-programming) **Encourage pair programming** * Implement pair programming sessions, especially for complex features or bug fixes, where two developers write code together at the same workstation. * Pair programming can reduce the need for extensive code reviews later as it incorporates continuous code review and mutual learning. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#track-and-act-on-review-metrics) **Track and act on review metrics** * Monitor metrics such as [review timearrow-up-right](https://hivel.gitbook.io/knowlegebase/metrics-and-definitions/speed/review-time) , [number of iterations per PRarrow-up-right](https://hivel.gitbook.io/knowlegebase/using-hivel/pull-request/review-cycles) , and [defect ratesarrow-up-right](https://hivel.gitbook.io/knowlegebase/metrics-and-definitions/quality/change-failure-rate) . Use this data to refine the review process. * Tracking these metrics helps identify bottlenecks and areas for improvement, allowing teams to adjust practices and workload distribution effectively. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#regularly-rotate-review-roles) **Regularly rotate review roles** * Rotate code review assignments among team members to ensure that everyone stays familiar with different parts of the codebase. * This rotation promotes a more comprehensive understanding of the project and prevents silos from forming within the team. ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#review-the-review-process) **Review the review process** * Periodically review and refine the code review process itself based on team feedback and evolving project needs. * Continual improvement of the review process ensures that it remains effective and relevant as the team and project evolve. By integrating these best practices, your team can foster a sense of ownership and pride in their work, leading to higher quality software and more engaged and knowledgeable team members. [PreviousStrategies to Reduce Hotfix Resolution Timechevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time) [NextHow to identify root cases of high change failure rates?chevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/how-to-identify-root-cases-of-high-change-failure-rates) Last updated 1 year ago * [Define clear ownership and responsibilities](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#define-clear-ownership-and-responsibilities) * [Implement a peer review system](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#implement-a-peer-review-system) * [Use automated tools](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#use-automated-tools) * [Establish review standards and checklists](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#establish-review-standards-and-checklists) * [Promote constructive feedback](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#promote-constructive-feedback) * [Encourage pair programming](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#encourage-pair-programming) * [Track and act on review metrics](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#track-and-act-on-review-metrics) * [Regularly rotate review roles](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#regularly-rotate-review-roles) * [Review the review process](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review#review-the-review-process) sun-brightdesktopmoon sun-brightdesktopmoon --- # Create Incident API | Hivel [hashtag](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#overview) Overview ---------------------------------------------------------------------------------------------------------- The Hivel Incident API enables submitting incident data to Hivel, allowing for precise calculation of metrics such as CFR (Change Failure Rate) and MTTR (Mean Time to Recovery). * * * ### [hashtag](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#base-url) Base URL The base URL for accessing Hivel may vary depending on your organization's configuration. Please make sure to select the appropriate base URL according to your setup. The URL will be either of these: `**https://app.hivel.ai**` OR `**https://app.hivel.in**` * * * ### [hashtag](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#authentication) 🔑 Authentication All requests require an organization API token. Pass this in the request header: Copy Authorization: YOUR_ORGANIZATION_API_TOKEN * * * [hashtag](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#retrieving-your-api-key) Retrieving Your API Key ---------------------------------------------------------------------------------------------------------------------------------------- 1. Open Hivel and navigate to **Integrations** under the **Settings**. 2. Click on **Connect** on **Hivel API Authorization card** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FpZ80VBIdJuv8BsrwZdOI%252Fimage.png%3Falt%3Dmedia%26token%3D0869583b-b6f0-4cda-a6b1-bd1ffc53c640&width=768&dpr=3&quality=100&sign=57e2ed7c&sv=2) 3. Follow the given steps to start your integration 4. By clicking on **Generate** your API Key will be generated. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FRj7txCE1jkzHG2J822yp%252Fimage%2520%2898%29.png%3Falt%3Dmedia%26token%3D2759fa06-84bf-4094-879e-8b10ee6d4281&width=768&dpr=3&quality=100&sign=66417070&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FoXU4heOSD8LS7QSB9Ve5%252Fimage%2520%2899%29.png%3Falt%3Dmedia%26token%3Dc9958254-4dd1-4120-ba69-a1074ce45ddc&width=768&dpr=3&quality=100&sign=20742e08&sv=2) * * * [hashtag](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#incident-events-api) Incident Events API -------------------------------------------------------------------------------------------------------------------------------- ### [hashtag](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#endpoint) Endpoint `POST` `https://app.hivel.ai/api/hooks/v1/incident` ### [hashtag](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#request-parameters) **Request Parameters** Field Name Type Description Example `description` string A detailed description of the incident (max 255 chars). Database connection timeout error `severity` Required string The severity level of the incident (e.g., low, medium, high, critical) (max 255 chars). high `affected_systems` array A list of systems affected by the incident. \["database", "backend"\] `reported_time` Required string The date and time when the incident occurred (ISO 8601 format). 2024-08-01T12:34:56Z `reported_by` string The username or identifier of the person who reported the incident (max 255 chars). jdoe `resolution_time` Required string The date and time when the incident was resolved (ISO 8601 format). 2024-08-01T13:34:56Z `provider_id` string The unique identifier of the incident in your incident management provider (max 255 chars). incident-123456 `repo_url` Required string The URL of the repository related to the deployment or incident (max 255 chars). [https://github.com/your-repo/projectarrow-up-right](https://github.com/your-repo/project) `pr_number` Required string The Pull Request (PR) identifier associated with the deployment. 44 ### [hashtag](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#request-example) **Request Example** Example ### [hashtag](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#response) Response 200 - Successful * `400` - Bad Request * `401` - Unauthorized * `500` - Internal Server Error [PreviousDeployment Events APIchevron-left](https://docs.hivel.ai/integrations/api-documentation/deployment-events-api) [NextDORA Metrics Powered by New APIs in Hivelchevron-right](https://docs.hivel.ai/integrations/api-documentation/dora-metrics-powered-by-new-apis-in-hivel) Last updated 4 months ago * [Overview](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#overview) * [Base URL](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#base-url) * [🔑 Authentication](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#authentication) * [Retrieving Your API Key](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#retrieving-your-api-key) * [Incident Events API](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#incident-events-api) * [Endpoint](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#endpoint) * [Request Parameters](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#request-parameters) * [Request Example](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#request-example) * [Response](https://docs.hivel.ai/integrations/api-documentation/create-incident-api#response) sun-brightdesktopmoon Copy curl --location 'https://app.hivel.ai/api/hooks/v1/incident' \ --header 'X-API-Token: YOUR_API_TOKEN_HERE' \ --header 'Content-Type: application/json' \ --data-raw '{ "description": "Database connection timeout affecting API", "severity": "HIGH", "affected_systems": ["database", "api-gateway"], "reported_time": "2025-09-22T10:30:00Z", "reported_by": "[email protected]", "resolution_time": "2025-09-22T11:15:00Z", "provider_id": "inc-20250922-1030", "repo_url": "https://github.com/hivelai/webhook-logger", "pr_number": "71" }' Copy { "message": "Success", "incident_id": "incident-2024-08-01-12345", } sun-brightdesktopmoon --- # ClickUp | Hivel [hashtag](https://docs.hivel.ai/integrations/project-management/clickup#prerequisites) Prerequisites --------------------------------------------------------------------------------------------------------- Clickup 1. You must have a ClickUp user account that is part of the Workspace(s) you want Hivel to access. 2. Scope of access: The PAT gives the same access as the ClickUp user who generated it, if that user is in multiple Workspaces, the PAT can access them. We recommend you to create a service account with all the permissions required to give hivel and use that account to integrate hivel 3. The account used to create the PAT should be an admin for the Workspace(s) you want to integrate. This prevents permission issues when Hivel tries to access lists, tasks or other workspace resources. Hivel 1. The user whoever is integrating must have access to Hivel’s Integrations page and the permission to edit integration settings. * * * ### [hashtag](https://docs.hivel.ai/integrations/project-management/clickup#step-by-step-generate-a-clickup-personal-access-token-pat) Step-by-step: generate a ClickUp Personal Access Token (PAT) These steps follow the ClickUp UI (versions 2.0 / 3.0 may differ slightly in avatar placement). If your ClickUp layout differs, look for Settings → Apps / ClickUp API. 1. Log in to ClickUp with the account that will own the PAT. 2. Click your avatar (top-right in ClickUp 3.0; lower-left in older versions). 3. Choose Settings from the menu. In the left sidebar, click Apps (or ClickUp API in some UI versions). ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FxZki2YqZSmjpgCyHastY%252FScreenshot%25202026-01-20%2520at%25203.27.10%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D28ca0ebc-7451-4a56-867e-dbb72d338025&width=768&dpr=3&quality=100&sign=4334d996&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F4qkwrF4HrGWWdSyoDpvM%252Funknown.png%3Falt%3Dmedia%26token%3D8feb52d8-4079-487e-99d9-f48c55b54042&width=300&dpr=3&quality=100&sign=b90b5d58&sv=2) 1. Under API Token (or Personal API token), click Generate (or Generate / Create token). [hashtag](https://docs.hivel.ai/integrations/project-management/clickup#undefined) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fz02D2DIHTaHKwyVdY2qr%252Funknown.png%3Falt%3Dmedia%26token%3D940eebb3-5eca-40c1-a58a-b4b34ad86b39&width=300&dpr=3&quality=100&sign=e0c64d&sv=2) ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1. When the token appears, click Copy to copy the token to your clipboard. The token string typically starts with pk\_. 2. Store the token securely, paste it into your password manager or Hivel immediately (see next section). ClickUp personal tokens never expire unless you regenerate or revoke them. Note: If you cannot see the Apps/API Token section, confirm you are signed in with a non-guest account and that your ClickUp user has necessary permissions. * * * ### [hashtag](https://docs.hivel.ai/integrations/project-management/clickup#how-to-insert-the-pat-into-hivel) How to insert the PAT into Hivel 1. Open Hivel and go to Settings → Integrations → ClickUp (or the project management area where ClickUp is listed). ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FNJU3LLL37n4lCfJD6Tkd%252FScreenshot%25202026-01-20%2520at%25203.32.21%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D21adde02-d39e-4a97-9034-3a3366ab8bd5&width=768&dpr=3&quality=100&sign=17e7e072&sv=2) 1. Copy paste the PAT into the ClickUp PAT input field. 2. Click Integrate ClickUp. Hivel will validate the token by calling ClickUp APIs. 3. After successful validation, Hivel will be able to authorize API calls on behalf of the ClickUp user who created the PAT (so ensure that user has access to all required Workspaces / Lists / Projects). ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fjx5g5Z4k67PaBmPlk30N%252FScreenshot%25202026-01-20%2520at%25203.32.54%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3De647e318-9f09-4ec6-af97-f7302352f5a1&width=768&dpr=3&quality=100&sign=c5fbc2a3&sv=2) * * * [hashtag](https://docs.hivel.ai/integrations/project-management/clickup#how-to-reauthorize) How to reauthorize ------------------------------------------------------------------------------------------------------------------- Regenerate/revoke: If the token is compromised or you want to force re-authentication, regenerate or revoke it from ClickUp Settings → Apps → API Token and update Hivel with the new token. [PreviousAzure Boardschevron-left](https://docs.hivel.ai/integrations/project-management/azure-boards) [NextAI Toolschevron-right](https://docs.hivel.ai/integrations/ai-tools) Last updated 2 months ago * [Prerequisites](https://docs.hivel.ai/integrations/project-management/clickup#prerequisites) * [Step-by-step: generate a ClickUp Personal Access Token (PAT)](https://docs.hivel.ai/integrations/project-management/clickup#step-by-step-generate-a-clickup-personal-access-token-pat) * [](https://docs.hivel.ai/integrations/project-management/clickup#undefined) * [How to insert the PAT into Hivel](https://docs.hivel.ai/integrations/project-management/clickup#how-to-insert-the-pat-into-hivel) * [How to reauthorize](https://docs.hivel.ai/integrations/project-management/clickup#how-to-reauthorize) sun-brightdesktopmoon sun-brightdesktopmoon --- # Best Practices for Ensuring Strong Pull Request Review Coverage | Hivel Consistent, high-quality PR review coverage is one of the strongest leading indicators of engineering health. It reduces defect escape, improves knowledge sharing, and keeps delivery predictable as teams scale. This guide outlines proven strategies to ensure every Pull Request receives timely, meaningful review, followed by concrete steps teams can take using Hivel. * * * ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#improving-pr-review-coverage-actionable-strategies) Improving PR Review Coverage: Actionable Strategies #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#id-1.-mandate-reviews-with-branch-protection) 1\. Mandate Reviews with Branch Protection Make PR reviews a non-negotiable step in your delivery workflow by enforcing branch protection rules. This ensures no code reaches critical branches without at least one approved review. Most modern SCMs support this natively: * **GitHub** Require pull request reviews before merging and define minimum approvers, dismissal rules, and status checks. * **Bitbucket** Enforce merge checks such as minimum reviewers, successful builds, and resolved tasks before merge. Why this matters Branch protection removes ambiguity and social friction. Reviews are no longer optional or dependent on individual discipline. The system enforces the behavior consistently. chevron-right**Links to branch protection rules and mandatory reviews across SCMs**[hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#links-to-branch-protection-rules-and-mandatory-reviews-across-scms) [_Approving a pull request with required reviews (GitHub Docs)_arrow-up-right](https://docs.github.com/articles/approving-a-pull-request-with-required-reviews) [_About protected branches (GitHub Docs)_arrow-up-right](https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches) [_Merge request approval rules (GitLab Docs)_arrow-up-right](https://docs.gitlab.com/user/project/merge_requests/approvals/) [_Protected branches (GitLab Docs)_arrow-up-right](https://docs.gitlab.com/user/project/repository/branches/protected/) [_Code Owners (GitLab Docs)_arrow-up-right](https://docs.gitlab.com/user/project/codeowners/) [_Branch Protection (Bitbucket)_arrow-up-right](https://support.atlassian.com/bitbucket-cloud/docs/use-branch-permissions/) [_Branch Policies in Azure Repos_arrow-up-right](https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies?view=azure-devops) [_About Pull Requests and Permissions (Azure DevOps)_arrow-up-right](https://learn.microsoft.com/en-us/azure/devops/repos/git/review-pull-requests?view=azure-devops) * * * #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#id-2.-encourage-optimal-pr-sizing) 2\. Encourage Optimal PR Sizing Actively promote shipping smaller, focused Pull Requests. As a general guideline, aim to keep PRs under **400 lines of code** whenever possible. **Why this matters** Smaller PRs are easier to reason about, faster to review, and less likely to accumulate review debt. Large PRs increase cognitive load, slow feedback loops, and often lead to superficial reviews or delays. **Practical tactics:** * Break features into incremental, reviewable slices. * Separate refactors from functional changes. * Avoid bundling unrelated changes into a single PR. * * * #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#id-3.-implement-a-code-review-checklist) 3\. Implement a Code Review Checklist Provide a standard checklist that both authors and reviewers follow for every PR. This creates consistency and reduces the chance of important items being missed. **A strong checklist typically covers:** * Correctness and logic * Test coverage and test quality * Edge cases and error handling * Performance considerations * Security and access control * Documentation and comments **Why this matters** Checklists reduce reliance on memory and reviewer experience alone. They help new reviewers contribute confidently and ensure quality standards are applied uniformly across teams. * * * #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#id-4.-formalise-review-responsibilities) 4\. Formalise Review Responsibilities Make code review an explicit, scheduled responsibility rather than an ad-hoc activity. **Effective approaches include:** * Reviewer rotations to distribute load fairly * Assigned primary reviewers per repository or code area * Clear ownership for critical paths and services **Why this matters** When “everyone” is responsible for reviews, no one truly is. Clear accountability ensures PRs are picked up quickly and do not stall due to ambiguity. * * * #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#id-5.-foster-a-positive-review-culture) 5\. Foster a Positive Review Culture Strong review coverage depends as much on culture as on process. **Encourage:** * Constructive, respectful feedback * Recognition for high-quality reviews, not just code output * Lightweight gamification or shout-outs for consistent reviewers **Why this matters** When reviews are seen as collaborative and valued, participation increases naturally. Teams move from defensive reviews to shared ownership of code quality. * * * #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#id-6.-integrate-ai-assisted-code-review) 6\. Integrate AI-Assisted Code Review Where appropriate, introduce AI-powered code review tools to handle repetitive or low-level checks. **Typical use cases:** * Identifying common anti-patterns * Flagging potential bugs or security issues * Suggesting refactors or style improvements **Why this matters** AI tools free human reviewers to focus on higher-order concerns such as architecture, domain correctness, and long-term maintainability. * * * ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#steps-you-can-take-using-hivel) Steps You Can Take Using Hivel Hivel helps operationalize these best practices by making review coverage visible, measurable, and actionable. #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#id-1.-surface-and-prioritise-open-prs) 1\. Surface and Prioritise Open PRs Use Hivel to filter and surface PRs that are **Ready to Review**. This ensures reviewers focus on PRs that are unblocked and actively awaiting feedback, preventing important work from getting buried in long queues. **Outcome** Reviewers spend less time searching and more time reviewing. * * * #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#id-2.-identify-review-bottlenecks-at-pr-and-team-level) 2\. Identify Review Bottlenecks at PR and Team Level When reviews take longer than expected or PRs remain unreviewed, use Hivel’s metrics to diagnose the root cause. Key signals include: * Average PR size * Review cycle count * Number of review comments * Comment sentiment analysis **Why this matters** Instead of guessing why reviews are slow, teams can pinpoint whether the issue is PR size, reviewer load, excessive back-and-forth, or unclear expectations, and take targeted corrective action. * * * #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#id-3.-track-review-coverage-with-dashboards) 3\. Track Review Coverage with Dashboards Create shared or private dashboards in **Hivel** to track: * Review coverage * Review turnaround time * Team-level review participation **Why this matters** Visibility drives behavior. When review metrics are visible, teams naturally course-correct and leadership can spot systemic issues early. * * * #### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#id-4.-set-clear-review-goals) 4\. Set Clear Review Goals **Define explicit goals for:** * Minimum PR review coverage * Target review turnaround time Use Hivel to track progress against these goals over time and identify trends. **Why this matters** Clear goals turn reviews from a vague expectation into a measurable practice, enabling continuous improvement rather than reactive fixes. * * * ### [hashtag](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#closing-perspective) Closing Perspective Strong PR review coverage does not happen by accident. It emerges from a combination of enforced guardrails, clear ownership, healthy culture, and continuous visibility. By pairing SCM-level controls with Hivel’s insights, teams can move from reactive reviews to a predictable, scalable review system that improves both code quality and delivery velocity. [PreviousWhat happens if there are too many Flashy Reviews and how to prevent them?chevron-left](https://docs.hivel.ai/improve-performance/how-to-improve-quality/what-happens-if-there-are-too-many-flashy-reviews-and-how-to-prevent-them) [NextStrategies to Reduce Hotfix Resolution Timechevron-right](https://docs.hivel.ai/improve-performance/how-to-improve-quality/strategies-to-reduce-hotfix-resolution-time) Last updated 3 months ago * [Improving PR Review Coverage: Actionable Strategies](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#improving-pr-review-coverage-actionable-strategies) * [Steps You Can Take Using Hivel](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#steps-you-can-take-using-hivel) * [Closing Perspective](https://docs.hivel.ai/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage#closing-perspective) sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Notes - October 2024 | Hivel #### [hashtag](https://docs.hivel.ai/release-notes/release-notes-october-2024#whats-new-this-month) What’s New This Month! ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-october-2024#introducing-private-dashboards) Introducing private dashboards Your dashboard, your rules! Now, private dashboards are fully visible only to their owners, while public dashboards remain viewable but locked down for other users. Plus, an 'Access' option lets owners toggle dashboard visibility between public and private as needed. Note: all current dashboards are set as public in production. [_Go ahead and give it a try!_arrow-up-right](https://app.hivel.ai/dashboard/custom-dashboards) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F6755xICXFTYRbagQFfZ7%252FGIF%2520Recording%25202024-10-30%2520at%252012.24.18%2520PM.gif%3Falt%3Dmedia%26token%3D0e27c26c-2a47-4251-8174-8a5ac33aff1a&width=768&dpr=3&quality=100&sign=202f38b3&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FBNs0ZoE96cpNziUBXwLu%252FGIF%2520Recording%25202024-10-30%2520at%252012.26.07%2520PM.gif%3Falt%3Dmedia%26token%3D2a86e2f5-5c09-4bf1-8ff6-6313ca513e5d&width=768&dpr=3&quality=100&sign=7ee26b8e&sv=2) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-october-2024#better-navigation-with-a-new-side-menu) Better navigation with a new side menu Navigating just got easier with our organized side menu. All features are now conveniently grouped. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FERLQFvzA2nuXzzK1t8gh%252FGIF%2520Recording%25202024-10-30%2520at%252012.31.22%2520PM.gif%3Falt%3Dmedia%26token%3D119bf996-407a-46d7-a910-95d03fb1a0d3&width=768&dpr=3&quality=100&sign=98f96ec7&sv=2) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-october-2024#see-the-big-picture-with-updated-parent-child-team-displays) See the big picture with updated parent-child team displays For those working with hierarchical teams, we’ve updated how metrics reflect! Selecting a parent team now reveals all associated members—parent and sub-teams—across the app, and the metrics are aggregated across all the sub-teams. This ensures you have the full team picture wherever you need it. [_See it in action!_arrow-up-right](https://app.hivel.ai/dashboard/cto) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDucBjRSsaDPUSXFeg0fa%252Fimage.png%3Falt%3Dmedia%26token%3Dbc5b81ae-a805-49a7-9da3-31c323a1fb4b&width=768&dpr=3&quality=100&sign=b853e01e&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FAXiqPcdBaiGjUrodgszJ%252Fimage.png%3Falt%3Dmedia%26token%3Dd69ef14c-eedf-4cdf-8523-3ecd682c97ba&width=768&dpr=3&quality=100&sign=3b9edd77&sv=2) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-october-2024#team-owner-icons-and-new-permissions) Team owner icons and new permissions Spot your team owners at a glance! An icon now identifies team owners on the Teams page, ensuring transparency in team management. Note: team owners must transfer ownership before their team can be archived or deleted, keeping your team structure intact. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FiP75qi2lpS0t8UALFmnt%252Fimage.png%3Falt%3Dmedia%26token%3Db9046aab-2c0b-4d2f-bd75-a562d6eee6b0&width=768&dpr=3&quality=100&sign=3d9beb24&sv=2) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-october-2024#user-merges-made-smarter) User merges made smarter We’ve made user merges smarter and more inclusive. Now, when multiple users are merged (e.g., User 1 into User 2, and then User 2 into User 3), the final user (User 3) will inherit team memberships and data from all prior merges across parent and sub-teams. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FT6CijPCjpbg9S2zgxYKl%252Fimage%2520%2829%29.png%3Falt%3Dmedia%26token%3D23d18208-cc70-4e41-8264-61afaa25232e&width=768&dpr=3&quality=100&sign=bd44504&sv=2) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-october-2024#phased-roll-out-fine-tune-your-pr-exclusions-with-new-one-to-one-option) (Phased roll-out) Fine-tune your PR exclusions with new one-to-one option We’ve introduced a new 'One to One' option in PR Exclusions, offering precise control over branch exclusions. Now, configure up to 10 unique source-destination branch pairs, which will exclude corresponding PRs from your metrics. Prefer the traditional setup? The existing 'Many to Many' feature remains unchanged, giving you flexibility to choose the best fit for your workflow. Configuration changes apply to data processed post-save. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FjCpSOR21XHvBQcVOAZue%252Fimage.png%3Falt%3Dmedia%26token%3Dbd036d1b-2d30-4c3a-93cb-f1c38e0e3967&width=768&dpr=3&quality=100&sign=9b93f70f&sv=2) * * * Take a moment to breathe🧘‍♀️! You’re all caught up, and it’s time for a well-earned coffee break ☕. See you next month! [PreviousRelease Notes - November 2024chevron-left](https://docs.hivel.ai/release-notes/release-notes-november-2024) [NextUse Caseschevron-right](https://docs.hivel.ai/use-cases) Last updated 1 year ago * [Introducing private dashboards](https://docs.hivel.ai/release-notes/release-notes-october-2024#introducing-private-dashboards) * [Better navigation with a new side menu](https://docs.hivel.ai/release-notes/release-notes-october-2024#better-navigation-with-a-new-side-menu) * [See the big picture with updated parent-child team displays](https://docs.hivel.ai/release-notes/release-notes-october-2024#see-the-big-picture-with-updated-parent-child-team-displays) * [Team owner icons and new permissions](https://docs.hivel.ai/release-notes/release-notes-october-2024#team-owner-icons-and-new-permissions) * [User merges made smarter](https://docs.hivel.ai/release-notes/release-notes-october-2024#user-merges-made-smarter) * [(Phased roll-out) Fine-tune your PR exclusions with new one-to-one option](https://docs.hivel.ai/release-notes/release-notes-october-2024#phased-roll-out-fine-tune-your-pr-exclusions-with-new-one-to-one-option) sun-brightdesktopmoon sun-brightdesktopmoon --- # Jira On-Prem | Hivel ### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/jira-on-prem#creating-a-personal-access-token-pat-in-jira) Creating a Personal Access Token (PAT) in Jira To integrate **Hivel** with **Jira**, you need to generate a **Personal Access Token (PAT)** for authentication. Below are the detailed steps for setting up the **service account** and generating the PAT in **Jira** for successful integration: #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/jira-on-prem#prerequisites) **Prerequisites** * **Jira Service Account**: Ensure you have a **service account** with **Site Admin** access to the Jira projects you want to analyze. This account will be used to fetch data from Jira for Hivel analysis. * * * #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/jira-on-prem#steps-for-integration) **Steps for Integration** **1\. Service Account Setup** * **Create a service account** in Jira if you don’t already have one. * Ensure this service account has **Site Admin access** to the required Jira projects you want Hivel to analyze. * The service account must have sufficient permissions to read data from the Jira projects, such as issue fields, access to all boards, and any other necessary information for analysis. **2\. Generate Personal Access Token (PAT)** To authenticate Hivel with Jira, you’ll need to generate a Personal Access Token (PAT). Follow these steps: * **Step 1**: Log in to your **Jira Service Account** and go to the following URL to manage your account settings: [Jira Account API Tokensarrow-up-right](https://id.atlassian.com/manage-profile/security/api-tokens) * **Step 2**: On the **API Tokens** page, click on **Create API token**. * **Step 3**: In the **Create API token** dialog: * Enter a **label** for the token (e.g., "Hivel Integration"). * Click **Create** to generate the token. * **Step 4**: After the token is created, a new token will appear in the list. Click the **Copy** button to copy the token to your clipboard. * **Step 5**: Store this token securely, as it is the only time it will be shown. You will use this token to authenticate with Jira from Hivel. Use the token to complete the next steps as shown on the Integration screen in Hivel. [PreviousGitlab On-Premchevron-left](https://docs.hivel.ai/integrations/on-prem-setup/gitlab-on-prem) [NextSonarQube On-Premchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/sonarqube-on-prem) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Notes - September 2025 | Hivel As we close Q3, Hivel’s been busy refining the details to make your day smoother. Say hello to faster integrations, cleaner data, and sharper visibility across teams! This round of updates focuses on control, clarity, and helping you move into Q4 with momentum. ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-september-2025#a-smarter-github-integration) A Smarter GitHub Integration ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FXOW0PmSGfOzOnRZDHevb%252Fimage.png%3Falt%3Dmedia%26token%3D0ba7ee68-6816-46f9-84d9-0ec8a64211e8&width=768&dpr=3&quality=100&sign=8a489a67&sv=2) We’ve redesigned how Hivel connects with GitHub to give your org more flexibility and control. Admins can now choose between: * **OAuth**, for full workspace access. * **GitHub App**, for tighter control over selected repositories. You can switch between the two anytime, and **new users will see OAuth as the default** setup, with the App mentioned under **Advanced Options**. 👉 [_Check it out_arrow-up-right](https://app.hivel.ai/settings/integrations) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-september-2025#upgraded-teams-and-goals-pages) Upgraded Teams & Goals Pages We’ve officially moved to the upgraded Teams and Goals experience. * Teams and Users now have dedicated pages, giving you clearer visibility and the ability to drill down from team → sub-team. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Frn5Rov7SARcWxDOqjOhg%252Fimage.png%3Falt%3Dmedia%26token%3D8337b03d-f655-44d1-b433-19d85750dae3&width=768&dpr=3&quality=100&sign=e917ff40&sv=2) * Goals PRO is now the default for new users, offering a more focused view for setting objectives and tracking outcomes. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FpVO0jJ7hAlClEEepcVUd%252FScreenshot%25202025-10-08%2520at%25206.22.38%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Dfa2a93de-f059-48ef-854a-46d475b254dc&width=768&dpr=3&quality=100&sign=709771b9&sv=2) The older Goals view will be deprecated within this week. 👉 [_Explore it now_arrow-up-right](https://app.hivel.ai/dashboard/goals) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-september-2025#labels-organize-beyond-teams) Labels - Organize Beyond Teams Introducing **Labels**, a new way to tag and organize users beyond just team structures. Add labels like Location, Skill Proficiency, or Product Line, and use them to filter dashboards and reports for more flexible insights. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FVTU4le8lK6fb4FS13qFa%252FScreenshot%25202025-10-09%2520at%252010.15.29%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3D5b38f7a0-c33a-4632-8275-285182f5df2b&width=768&dpr=3&quality=100&sign=af66a3b3&sv=2) 👉 [_Try it out_arrow-up-right](https://app.hivel.ai/settings/labels) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-september-2025#repo-exclusion-focus-on-what-matters) Repo Exclusion – Focus on What Matters You can now **exclude repositories directly from Hivel** (up to ten per organization). All related commits and PRs will automatically be excluded from your analytics, keeping your reports focused on active, relevant work. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FgnSgogKI69YGMv0XeLcj%252FScreenshot%25202025-10-09%2520at%252010.17.08%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3Dc6ae8ce8-f26c-4cd0-bd0c-72e792aa66b8&width=768&dpr=3&quality=100&sign=bbc77275&sv=2) 👉 [_Try it out_arrow-up-right](https://app.hivel.ai/settings/repos) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-september-2025#smarter-pr-auto-exclusions) Smarter PR Auto-Exclusions You can now auto-exclude PRs based on **Cycle Time**, **PR Size**, or **Keyword Patterns**, in addition to the existing branch and commit filters. All exclusion settings now live under _Configuration → Exclusions_, where you can manage them for both orgs and teams. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FYyJqWd1mvDESrXjUzAdI%252FScreenshot%25202025-10-09%2520at%252010.19.52%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3Da2ab99ee-62de-4ec2-b33d-bcccbad3515b&width=768&dpr=3&quality=100&sign=c645531d&sv=2) 👉 [_Check it out_arrow-up-right](https://app.hivel.ai/settings/configuration) [hashtag](https://docs.hivel.ai/release-notes/release-notes-september-2025#minor-upgrades-to-make-navigation-easier) 🔎 Minor Upgrades to Make Navigation Easier --------------------------------------------------------------------------------------------------------------------------------------------------------------------- ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-september-2025#easier-metric-exploration) Easier Metric Exploration **Click on any metric chart from your Cockpit board**, and you’ll land on a detailed view of that metric’s trends. Now, you can: * **Quickly switch metrics:** From the top of the metric detail page, you can now search and switch to any other metric instantly - no need to head back to the dashboard. * **View deeper drill-downs:** From the trend chart, you can now open commits and PRs directly for weekly and monthly date ranges (previously only available for daily). ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FrH6361Tj0XI10icEw8NH%252FScreenshot%25202025-10-09%2520at%252010.23.17%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3Daea73d8c-0d96-47dc-810b-0c0da34e4a25&width=768&dpr=3&quality=100&sign=afdc8e5b&sv=2) 👉 [_Explore it now_arrow-up-right](https://app.hivel.ai/dashboard/custom-dashboards) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-september-2025#smoother-navigation-across-hivel) Smoother Navigation Across Hivel **Clicking on the Hivel logo** now takes you exactly where you expect — your personal default page, your admin’s org default, or your dashboards. It’s a small update, but it makes getting around a little simpler every time. [hashtag](https://docs.hivel.ai/release-notes/release-notes-september-2025#wrapping-up-september) ☕ Wrapping Up September ------------------------------------------------------------------------------------------------------------------------------ We’re ending Q3 with updates curated for better performance, flexibility, and visibility. Expect even more depth around AI-driven insights and engineering impact during the last leg of the year. Stepping into the Q4 requires a mix of focus and balance. Take a breather, stretch, and gear up for the next chapter. The best results come when effort meets a little downtime! 😉 Here's to a productive and well-paced quarter! 🍻 [PreviousRelease Notes - October 2025chevron-left](https://docs.hivel.ai/release-notes/release-notes-october-2025) [NextRelease Notes - August 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-august-2025) Last updated 5 months ago * [A Smarter GitHub Integration](https://docs.hivel.ai/release-notes/release-notes-september-2025#a-smarter-github-integration) * [Upgraded Teams & Goals Pages](https://docs.hivel.ai/release-notes/release-notes-september-2025#upgraded-teams-and-goals-pages) * [Labels - Organize Beyond Teams](https://docs.hivel.ai/release-notes/release-notes-september-2025#labels-organize-beyond-teams) * [Repo Exclusion – Focus on What Matters](https://docs.hivel.ai/release-notes/release-notes-september-2025#repo-exclusion-focus-on-what-matters) * [Smarter PR Auto-Exclusions](https://docs.hivel.ai/release-notes/release-notes-september-2025#smarter-pr-auto-exclusions) * [🔎 Minor Upgrades to Make Navigation Easier](https://docs.hivel.ai/release-notes/release-notes-september-2025#minor-upgrades-to-make-navigation-easier) * [Easier Metric Exploration](https://docs.hivel.ai/release-notes/release-notes-september-2025#easier-metric-exploration) * [Smoother Navigation Across Hivel](https://docs.hivel.ai/release-notes/release-notes-september-2025#smoother-navigation-across-hivel) * [☕ Wrapping Up September](https://docs.hivel.ai/release-notes/release-notes-september-2025#wrapping-up-september) sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Notes - August 2025 | Hivel "_And so it was foretold, that in the ninth month, features of immense power would arrive. But let us not forget the eighth - August - whose quiet strength laid the groundwork for what’s to come."_ Herein lies the tale of August’s contributions... * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-august-2025#commit-frequency-metric) Commit Frequency Metric Say hello to **Commit Frequency** – our newest Git metric that calculates the _average number of commits per developer per day_. It gives a sharper lens into engineering rhythm and behavior, derived from our core Commits metric. You’ll find it across **All Git Metrics**, **Throughput Board templates**, and **Dev360** views. Heads up: Graph values will typically hover around 0 or 1 – it’s all about daily averages per developer. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FnGLMMVG6aZPU59PIBZws%252Fimage.png%3Falt%3Dmedia%26token%3D608b801d-295e-45f2-b6a0-69cab7556682&width=768&dpr=3&quality=100&sign=6a7ab071&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FIlsMneiaxWYUc3XY3GAa%252Fimage.png%3Falt%3Dmedia%26token%3D0fcac296-414f-4d7b-aff9-1ecaf0b6de51&width=768&dpr=3&quality=100&sign=1806f6fd&sv=2) 👉 [_Check it out_arrow-up-right](https://app.hivel.ai/overview/commit-frequency) * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-august-2025#persistent-filters-in-investment-screen) Persistent Filters in Investment Screen Boards, Sub-boards, and Sprints selections now **persist** across all 5 tabs of the Investment screen. No more reapplying filters on every visit - they stay put until you refresh or log out. 👀 Coming soon: Saved Filters to make your views even smarter. 👉 [Investment Screenarrow-up-right](https://app.hivel.ai/dashboard/investment-profile) * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-august-2025#enhanced-release-cycle-filters) Enhanced Release Cycle Filters We’ve revamped how Release Cycles behave across the platform: * Default cycles always appear first. * Others are sorted by their proximity to today. * Future-only cycles are now hidden (unless you're configuring). * If a cycle spans past/future dates, data shows _only up to today_. * In **Cockpit Dashboards**, your saved filters always take precedence. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FgBdE5kVGrdOPhN42kKjI%252Fimage.png%3Falt%3Dmedia%26token%3D718f72e4-07e8-41a0-a3a4-3f95595fc416&width=768&dpr=3&quality=100&sign=6f2a77f2&sv=2) [_Also check out last month's notes to see how you can see trends over sprints/release cycles._](https://docs.hivel.ai/release-notes/release-notes-october-2024) * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-august-2025#smarter-default-landing-pages) Smarter Default Landing Pages Admins and Execs can now set default landing pages for their teams via Configuration. This update respects user preferences while giving org-wide control. The priority works like this: 1. **User session** setting (existing behavior) 2. **Admin-configured** landing page 3. Default fallback → **Dashboards (All Boards)** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F9qUbQblo1MiOCYk5AYoD%252Fimage.png%3Falt%3Dmedia%26token%3De4d41cf0-727f-42c4-b540-1c06c8a82c74&width=768&dpr=3&quality=100&sign=10398abd&sv=2) 👉 [_Here is where you can set it up_arrow-up-right](https://app.hivel.ai/settings/configuration) * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-august-2025#downloadable-cockpit-graphs) Downloadable Cockpit Graphs You can now **download graphs** in .png format from the Cockpit screen, per metric - perfect for sharing insights outside the platform. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FSxJ3nwRz9aT4E5Du5GSl%252Fimage.png%3Falt%3Dmedia%26token%3D9ffbfed0-ed12-4858-a39a-f03859e66ba8&width=768&dpr=3&quality=100&sign=f6832e07&sv=2) * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-august-2025#unmerge-user-via-ui) 👤 Unmerge User via UI The new **Unmerge** feature on the UI lets you isolate a user from their merged chain. You can select one or multiple merged users in the Teams page, and once the users are unmerged, all the accounts chained together will be separated. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FOcTqlFS5eZ9LW4iELCzo%252Fimage.png%3Falt%3Dmedia%26token%3D47e1f530-516c-4b86-9008-401c28739d97&width=768&dpr=3&quality=100&sign=310fc31c&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fw0uaVCfsMfA6xZpeMgNT%252Fimage.png%3Falt%3Dmedia%26token%3De2e315f4-c5cb-415b-8690-87f3c9f67f3e&width=768&dpr=3&quality=100&sign=fe3fc62a&sv=2) * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-august-2025#scm-workspaces-filter) 🧪 SCM Workspaces Filter On the **Repositories page**, filter by **SCM Workspaces** to better navigate and segment your repositories based on Git workspace configurations. 👉 [Check it outarrow-up-right](https://app.hivel.ai/settings/repos) * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-august-2025#investment-bar-chart-improvements) 📊 Investment Bar Chart Improvements Expanded view for **bar chart breakdowns** across all the Investment tabs - making comparisons and analysis more intuitive. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fs5dQgigVH6jlZ7BiEI2J%252Fimage.png%3Falt%3Dmedia%26token%3D823c2c70-443b-4760-888a-dffcf2988c53&width=768&dpr=3&quality=100&sign=29718fd8&sv=2) * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-august-2025#user-profile-enhancements) User Profile Enhancements The **User Profile** now lets users save favorite filters for **Teams (Git)** and **Projects (PM tools) -** and they persist across sessions! You can still change the filters during sessions, but unless updated in Profile Preferences, your favorites will remain the default when you log in. Accessible via the bottom-left menu or directly via URL. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FBdHofVJdsRL94SqfDb5Z%252Fimage.png%3Falt%3Dmedia%26token%3D32060eae-cdaa-46ac-be6e-75789dff5152&width=768&dpr=3&quality=100&sign=6ddce95a&sv=2) 👉 [Personalize your spacearrow-up-right](https://app.hivel.ai/settings/user-profile) * * * ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-august-2025#public-dashboards-as-landing-pages) Public Dashboards as Landing Pages Admins can now set **Public Dashboards and templates** as default landing pages for _any_ access role. More visibility, more flexibility. * * * `**"And thus concludes the chapter of August. Now rise from your chair, brave builder - stretch your limbs, greet your companion beast (be it dog, cat, or capybara 🐾🦫), and feast upon your chosen snack 🍿. You’ve earned your rest."**` `But ready thyself… for September brings magic of a higher order. See you then. ✨` [PreviousRelease Notes - September 2025chevron-left](https://docs.hivel.ai/release-notes/release-notes-september-2025) [NextRelease Notes - July 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-july-2025) Last updated 6 months ago * [Commit Frequency Metric](https://docs.hivel.ai/release-notes/release-notes-august-2025#commit-frequency-metric) * [Persistent Filters in Investment Screen](https://docs.hivel.ai/release-notes/release-notes-august-2025#persistent-filters-in-investment-screen) * [Enhanced Release Cycle Filters](https://docs.hivel.ai/release-notes/release-notes-august-2025#enhanced-release-cycle-filters) * [Smarter Default Landing Pages](https://docs.hivel.ai/release-notes/release-notes-august-2025#smarter-default-landing-pages) * [Downloadable Cockpit Graphs](https://docs.hivel.ai/release-notes/release-notes-august-2025#downloadable-cockpit-graphs) * [👤 Unmerge User via UI](https://docs.hivel.ai/release-notes/release-notes-august-2025#unmerge-user-via-ui) * [🧪 SCM Workspaces Filter](https://docs.hivel.ai/release-notes/release-notes-august-2025#scm-workspaces-filter) * [📊 Investment Bar Chart Improvements](https://docs.hivel.ai/release-notes/release-notes-august-2025#investment-bar-chart-improvements) * [User Profile Enhancements](https://docs.hivel.ai/release-notes/release-notes-august-2025#user-profile-enhancements) * [Public Dashboards as Landing Pages](https://docs.hivel.ai/release-notes/release-notes-august-2025#public-dashboards-as-landing-pages) sun-brightdesktopmoon sun-brightdesktopmoon --- # Release Notes - November 2024 | Hivel We’ve been busy working on some cool enhancements to make your experience smoother, faster, and more personalized. Here's what's new: ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-november-2024#user-profile-section-your-preferences-your-way) User Profile section: your preferences, your way * **Preferred landing screen**: We’ve introduced a new **Profile** section in the user menu. Now, you can set your preferred default landing screen so that whenever you log in, you land exactly where you want to. It’s your space, your style. 🛋️✨ [_Set your own landing screen!_arrow-up-right](https://app.hivel.ai/dashboard/cto) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FLLbaWr9tk3NkYSarDZpn%252Fimage.png%3Falt%3Dmedia%26token%3Db3782a04-46bd-40fc-8eb9-0f3db41780df&width=768&dpr=3&quality=100&sign=42f48bb2&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FdeijUBxCFLcZaJqZRPI5%252Fimage.png%3Falt%3Dmedia%26token%3D8f9ee7aa-3257-4aab-87d6-8807e3866df7&width=768&dpr=3&quality=100&sign=7d3b8555&sv=2) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-november-2024#save-table-settings-for-pr-screen-your-filters-your-rules) Save Table Settings for PR screen: your filters, your rules * **Personalized PR views**: The new "Save Table Settings" feature is now live on the Pull Requests (PR) screen! You can save your filter configurations, whether showing/hiding columns or reordering them. This means you get a personalized view every single time. 🚀 [_Try it out_arrow-up-right](https://app.hivel.ai/dashboard/pull-requests) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F7GmMipyd2hJG6ygXQXJX%252FGIF%2520Recording%25202024-12-06%2520at%25202.33.04%2520PM.gif%3Falt%3Dmedia%26token%3D3ab3574c-1694-42b0-84ce-4cf0e7e005b0&width=768&dpr=3&quality=100&sign=41d0513e&sv=2) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-november-2024#dev-360-and-activity-screens-a-dash-of-fun-and-functionality) Dev 360 & Activity screens: A dash of fun & functionality! * **Bubble animations**: Get ready for some eye-catching effects! We’ve added a fun animation to the bubbles on both the Dev 360 and Activity pages. It’s a small touch that adds a bit of magic to your day! 💫 ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FDvz35e3NQ9OtCdUbk4Dg%252FGIF%2520Recording%2520Dec%25206%25202024.gif%3Falt%3Dmedia%26token%3D080c03b2-145d-4f49-ab68-696320851d2d&width=768&dpr=3&quality=100&sign=9a15dff2&sv=2) * **Activity summary**: We've added a helpful info message about the activities done by the selected user on the Dev 360 page. Now, you can keep track of all actions without guesswork. [_Go ahead and give it a try!_arrow-up-right](https://app.hivel.ai/dashboard/dev-360) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FjO7jMHaHiGCSvdNCVICg%252Fimage.png%3Falt%3Dmedia%26token%3Db0473b30-d4d6-44c2-ab60-dac73b11243c&width=768&dpr=3&quality=100&sign=88e828fd&sv=2) * **Toggle the right-side activity details**: You asked for more flexibility, and we listened! Use the toggle button at the top of the page to show or hide the right-side activity section, giving you a cleaner, more focused view when you need it. [_Go ahead and give it a try!_arrow-up-right](https://app.hivel.ai/dashboard/activity) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FEuKKgvgMjR8J7r9fVxho%252FGIF%2520Recording%25202024-12-06%2520at%25201.10.14%2520PM.gif%3Falt%3Dmedia%26token%3Dcb42cab9-a12b-40e0-a108-1e190d9006cd&width=768&dpr=3&quality=100&sign=9f2b74fb&sv=2) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-november-2024#other-minor-enhancements-a-little-polish-everywhere) Other minor enhancements: A little polish everywhere * We’ve improved the flashy review definition to update seamlessly across the screen as per the configuration. It’s all in sync now! * The "Review Cycle Count" has been added to the Pull Request CSV report. * * * That’s all for now! Give these new features a spin and let us know what you think. 🏍️🐱 [PreviousRelease Notes - December 2024chevron-left](https://docs.hivel.ai/release-notes/release-notes-december-2024) [NextRelease Notes - October 2024chevron-right](https://docs.hivel.ai/release-notes/release-notes-october-2024) Last updated 1 year ago * [User Profile section: your preferences, your way](https://docs.hivel.ai/release-notes/release-notes-november-2024#user-profile-section-your-preferences-your-way) * [Save Table Settings for PR screen: your filters, your rules](https://docs.hivel.ai/release-notes/release-notes-november-2024#save-table-settings-for-pr-screen-your-filters-your-rules) * [Dev 360 & Activity screens: A dash of fun & functionality!](https://docs.hivel.ai/release-notes/release-notes-november-2024#dev-360-and-activity-screens-a-dash-of-fun-and-functionality) * [Other minor enhancements: A little polish everywhere](https://docs.hivel.ai/release-notes/release-notes-november-2024#other-minor-enhancements-a-little-polish-everywhere) sun-brightdesktopmoon sun-brightdesktopmoon --- # How to reauthorize Github with a classic token? | Hivel To ensure that personal repositories are not integrated with Hivel, it’s important to use a dedicated service account. Follow the steps below to reauthorize GitHub with a service account: **Step-by-Step Guide** 1. Make sure you have a dedicated service account on GitHub with access to the necessary repositories. 2. Use the credentials for the service account to log into GitHub. 3. Click on the profile icon located at the top-right corner of the GitHub page. 4. From the dropdown menu, select **Settings**. 5. In the left-hand sidebar of the settings page, scroll down and click on **Developer settings**. 6. Under Developer settings, select **Personal access tokens**. 7. Choose **Tokens (classic)** to proceed. 8. Click on **Generate new token**. 9. For the token type, select **Classic**. 10. Name: Add name as "Hivel". 11. Expiration: Select No expiration date. (You can revoke the token once the integration is no longer needed). 12. Ensure the following scopes are selected to provide necessary access: 1. **repo**: (all scopes) 2. **org:** (only "read:org") 3. **hooks:** (all scopes) 4. **user:** (only "read:user" and "user:email") 13. Once the token is generated, copy it immediately. You will not be able to see it again once you leave the page. Share the following information with Hivel to complete the integration: * Personal Access Token * Username * Email By following these steps, you can reauthorize GitHub with a service account, ensuring a secure and efficient setup for Hivel integration. For further assistance, contact [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#afdcdadfdfc0dddbefc7c6d9cac381cec6) . [PreviousHow to create Github fine-grained token for Hivel Integration?chevron-left](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-create-github-fine-grained-token-for-hivel-integration) [NextGitlabchevron-right](https://docs.hivel.ai/integrations/scm/gitlab) Last updated 7 months ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Creating a Bitbucket App Password | Hivel ### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password#id-1.-access-the-app-password-creation-page) 1\. Access the App Password Creation Page * Log in to your Bitbucket account * Go to: [https://bitbucket.org/account/settings/app-passwords/newarrow-up-right](https://bitbucket.org/account/settings/app-passwords/new) ### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password#id-2.-enter-basic-details) 2\. Enter Basic Details * In the "Label" field, enter a descriptive name (e.g., "Hivel" or another name that describes the purpose) ### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password#id-3.-set-permissions) 3\. Set Permissions Select the following permissions: Account: * ✓ Email Read * ✓ Read Workspace membership: * ✓ Read Repositories: * ✓ Read Pull requests: * ✓ Read ### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password#id-4.-create-the-password) 4\. Create the Password * Click the blue "Create" button at the bottom left * Bitbucket will generate a secure password circle-exclamation **IMPORTANT:** Copy this password immediately and store it securely - it will only be shown once ### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password#id-5.-using-your-app-password) 5\. Using Your App Password * Use this password along with your Bitbucket username when authenticating with the API * The app password will have only the permissions you've selected ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXcYMXTH732mvQZJatEXptiw4bfzxZ7mwl6n8xGqWzgRgvvOQoynRcBzaNJ_dpQMoIbXsNGh7PKJRJH1lmpXNqzDArNuzyM3_nc-j5wpHcHcwO_JTtSA9sfFz9VZvF2AWncn0ZGseg%3Fkey%3DKDoRtP05NudNy6wIntOgxSbd&width=768&dpr=3&quality=100&sign=55c48ae3&sv=2) [PreviousSonarQube On-Premchevron-left](https://docs.hivel.ai/integrations/on-prem-setup/sonarqube-on-prem) [NextOn-Prem Outlook Integrationchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/on-prem-outlook-integration) Last updated 10 months ago * [1\. Access the App Password Creation Page](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password#id-1.-access-the-app-password-creation-page) * [2\. Enter Basic Details](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password#id-2.-enter-basic-details) * [3\. Set Permissions](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password#id-3.-set-permissions) * [4\. Create the Password](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password#id-4.-create-the-password) * [5\. Using Your App Password](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password#id-5.-using-your-app-password) sun-brightdesktopmoon sun-brightdesktopmoon --- # Gitlab On-Prem | Hivel To integrate **Hivel** with **GitLab**, you'll need to create a **Personal Access Token (PAT)** for authentication. Below are the detailed steps to generate the token in GitLab: * * * #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/gitlab-on-prem#steps-to-create-a-personal-access-token-pat-in-gitlab) **Steps to Create a Personal Access Token (PAT) in GitLab** **1\. Access User Settings** * **Log in** to your **GitLab** account. * In the top-right corner of the screen, click on your **profile icon**. * From the dropdown menu, select **"Preferences"** to access your account settings. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXemfL102epMWT8llITWbQhS7GSrDkt6cRkiF6IDUrgTgdQroCSuYYtGQ4a62KUe_ir_6iP_-iZOzGxKyLg3MOB7BW4KVSQpu3c7n5i99DCus3lNqRbNldbHZZTWYBgIAQJ6hskMEw%3Fkey%3D3hJ1ramI-10wlNgIdI5NQFuy&width=768&dpr=3&quality=100&sign=231932b0&sv=2) **2\. Navigate to Access Tokens** * In the left sidebar, scroll down and find **"Access tokens"** under the **"Access"** section. * Click on **"Access tokens"** to open the token generation page. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdU8E_ZlES5KHJLx3jp8ATP9ZALqMXbEyFa14NdblRl2wrs2tAb73x0kV6LuoKSa0lI0JPvgDN2WYcvao6l2u1sJGwUgBEzaS5HZsurgs3uab9Lh_qTYgYaosFAVRZ3-_7PlaUtIw%3Fkey%3D3hJ1ramI-10wlNgIdI5NQFuy&width=768&dpr=3&quality=100&sign=91ee6043&sv=2) **3\. Enter Token Details** * **Name**: Enter a name for your token. It is recommended to use something descriptive, like **"Hivel"**, for easy identification. * **Description**: This is optional, but you can add a description to help identify the token's purpose. * **Expiration Date**: Set an expiration date for the token if desired, or leave it blank for **no expiration**. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXcEdDs0conc10Qj52nF6J9eS0kUtvCGHWhnH6VWtdMJpW9NtmXLUAqrLW1o-KG03bVOOYl41X4_Lmaj_daxQD4L9r0L-0DsIIDWxbyhLSVxnfZyhN7rfp-SqC2IKbgAdAu08TN17w%3Fkey%3D3hJ1ramI-10wlNgIdI5NQFuy&width=768&dpr=3&quality=100&sign=940be711&sv=2) **4\. Select Required Scopes** * To enable **Hivel** to interact with your GitLab instance, check the following required scopes: * **read\_api**: To read data from the GitLab API. * **read\_user**: To read user information. * **read\_repository**: To access repository data. **5\. Create the Token** * After entering the details and selecting the necessary scopes, click on the **"Create personal access token"** button. **6\. Save the Token** * Once the token is created, **copy the generated token** immediately and store it in a secure location. * **IMPORTANT**: This is the **only time** the token will be displayed, so make sure to copy it before leaving the page. Use the token to complete the next steps as shown on the Integration screen in Hivel. [PreviousApplication Setup Guide: User Sign-up and Integrationchevron-left](https://docs.hivel.ai/integrations/on-prem-setup/application-setup-guide-user-sign-up-and-integration) [NextJira On-Premchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/jira-on-prem) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # SonarQube On-Prem | Hivel Integrating SonarQube with Hivel enhances the quality and security of your codebase by enabling continuous code inspection and quality monitoring. SonarQube helps detect bugs, vulnerabilities, and code smells, ensuring that your software projects maintain high standards of code quality. By following the steps outlined below, you can seamlessly connect SonarQube to Hivel, allowing for efficient code quality management within your platform. #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/sonarqube-on-prem#h_01j3f1mcmbfjzaqwgecz0qnyxy) Step - 1: Whitelist Necessary IP Addresses For a secure and uninterrupted connection, make sure to whitelist the following IP addresses: * **Mandatory IPs**: * 107.23.139.76 * 3.219.89.23 * **Recommended, but Optional IPs**: * 45.119.114.218 * 183.82.116.218 #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/sonarqube-on-prem#h_01j05wwnfdzyph27b08y79h4sp) Step - 2: Generate an Access Token in SonarQube 1\. Log in to your SonarQube account. 2\. Click on the name icon located in the top right corner. 3\. Select "**My Account**" from the dropdown menu. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FqsiPxfaJ5nBD2p9ciXBc%252Fimage.png%3Falt%3Dmedia%26token%3D21858d36-722f-4efb-a690-38777760f6a7&width=768&dpr=3&quality=100&sign=2b8d6d67&sv=2) 4\. Navigate to the "**Security**" tab. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FLLgNSaSrjUfnKjuzVC6s%252Fimage%2520%2850%29.png%3Falt%3Dmedia%26token%3D75fbae5e-2b2e-4091-bef2-6022836857c7&width=768&dpr=3&quality=100&sign=466c297&sv=2) 5\. Go to Generate a token. 6\. Enter a token name, preferably "Hivel". 7\. Click on the "**Generate**" button. 8\. Copy the generated token and save it securely. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FLiR1AYc9cVS3GN9pgp0y%252Fimage%2520%2852%29.png%3Falt%3Dmedia%26token%3Dd2616e8f-dcbb-42bd-829c-facfc9c446e7&width=768&dpr=3&quality=100&sign=9f123a92&sv=2) 9\. Copy the URL from the address bar of your SonarQube server and save it. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FkZuNGgsuSxm132LPrZl6%252Fimage%2520%2853%29.png%3Falt%3Dmedia%26token%3Da6798198-154b-4711-9890-095828dddbfd&width=768&dpr=3&quality=100&sign=4baa71c6&sv=2) #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/sonarqube-on-prem#h_01j05wwnfd5tgn2061q6h8yasv) Step - 3: Connecting SonarQube to Hivel 1\. Log in to the Hivel Platform. 2\. Go to "**Settings**". 3\. Select "**Integrations**" from the settings menu. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FCiJ93Z09qbJC4O6WqtZt%252Fimage.png%3Falt%3Dmedia%26token%3Dcd06beb6-c9c7-44cf-a7b9-9ca60827ce25&width=768&dpr=3&quality=100&sign=62794edb&sv=2) 4\. Find the SonarQube card and click on "**Connect**". ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FxqC8hz6rkTAJJLnxpQPY%252Fimage%2520%2858%29.png%3Falt%3Dmedia%26token%3D3a8d50e3-fa4a-406c-a92e-5a73f08b00a8&width=768&dpr=3&quality=100&sign=ef3b64df&sv=2) 5\. **Fill in the required details:** * **SonarQube URL:** Enter the SonarQube server URL you copied earlier. * **Access Token:** Enter the access token you generated in SonarQube. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FpdKCJPJtp0CjgCTkEZw0%252Fimage%2520%2857%29.png%3Falt%3Dmedia%26token%3D122306cf-5403-4e7c-9152-fd1c83d52376&width=768&dpr=3&quality=100&sign=9a72e2b&sv=2) 6\. **Click on Submit.** ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FmInY4BsqJTXqYRKqU7UL%252Fimage.png%3Falt%3Dmedia%26token%3Db748cc6b-9b7e-4900-bbf7-9dce88afd754&width=768&dpr=3&quality=100&sign=4e85a164&sv=2) By following these steps, you should successfully connect your SonarQube instance to Hivel. If you encounter any issues or need further assistance, please reach out to the Hivel support team at [\[email protected\]envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#394a4c4949564b4d7951504f5c55175850) . [PreviousJira On-Premchevron-left](https://docs.hivel.ai/integrations/on-prem-setup/jira-on-prem) [NextCreating a Bitbucket App Passwordchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/creating-a-bitbucket-app-password) Last updated 1 month ago sun-brightdesktopmoon sun-brightdesktopmoon --- # Validation at a metric level for BitBucket | Hivel **Purpose:** To validate the accuracy of key engineering productivity metrics shown in Hivel by manually cross-checking with raw data from Bitbucket for a selected developer. * * * ### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#prerequisites) Prerequisites * Access to the Bitbucket repository and Bitbucket UI with permission to view pull requests, commits, and reviews. * Access to the Hivel platform with permissions to view the developer's metrics. * Basic familiarity with Bitbucket's interface (Pull Requests, Commits, and Activity tabs). * * * ### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#metrics-definitions) Metrics Definitions Metric Name Definition **Cycle Time** Time from first commit to PR merged. **Coding Time** Time from first commit until PR is opened. **Review Time** Time from PR opened until PR is reviewed. **PR > 400 LoC** Number of PRs with more than 400 lines of code changed. **PRs merged without review** PRs merged that have no recorded review state. **MTTR (Mean Time to Repair)** Average cycle time for production issue fixes identified by 'hotfix' label or title. **Deployment Frequency** How often code is released — number of PRs merged to main/master per time period. **Active Days** Average number of days with any activity per engineer. **Flashy Reviews** PRs that have a review time under 5 minutes. * * * ### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#step-by-step-validation-process-for-one-developer) Step-by-Step Validation Process for One Developer * * * #### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#identify-the-developer-and-time-period) Identify the Developer and Time Period * In Bitbucket, locate the developer by username or email. * Filter PRs and commits to only those authored by this developer within the validation time period. * **Ensure to select a shorter time period e.g. a week or 3 days to get a limited amount of data to cross-check with BitBucket.** * * * #### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#id-1.-validate-cycle-time) 1\. Validate Cycle Time **On Hivel:** Go to Pull Request screen and filter out the team, developer, and time frame for the list of merged PRs in that duration. Go to Cockpit to look at the average Cycle time for the same filters, once validated for each PR on BitBucket. (follow the same above steps to filter on Hivel for time related metrics) **On Bitbucket:** * For each PR by the developer: * Identify the timestamp of the **first commit** included in the PR. * Identify the timestamp when the PR was **merged**. * Calculate the difference (merge time - first commit time). * Calculate the average of these differences across all PRs in the period. * * * #### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#id-2.-validate-coding-time) 2\. Validate Coding Time **On Bitbucket:** * For each PR: * Find the time of the first commit in the PR. * Find the time when the PR was **opened**. * Calculate the difference (PR opened time - first commit time). * Calculate the average coding time. * * * #### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#id-3.-validate-review-time) 3\. Validate Review Time **On Bitbucket:** * For each PR: * Note the time when the PR was **opened**. * Find the time of the **first approval**. * Calculate the difference (first review time - PR opened time). * Average this across all PRs. * * * #### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#id-4.-validate-prs-greater-than-400-lines-of-code) 4\. Validate PRs > 400 Lines of Code **On Hivel:** Go to Pull Request screen and filter out the team, developer, time frame, and PRs > 400 LoC - for the list of large merged PRs in that duration. **On Bitbucket:** * Filter all PRs merged by the developer in that time period. * For each PR, check the number of lines changed. * BitBucket recommends running this command line to fetch the PR size * "git fetch origin pull/PR\_ID/head:pr-branch git diff --stat main...pr-branch" * Replace `PR_ID` and `main` with the appropriate PR number and base branch. * Count how many PRs exceed 400 lines changed. * * * #### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#id-5.-validate-prs-merged-without-review) 5\. Validate PRs Merged Without Review **On Hivel:** Go to Pull Request screen and filter out the team, developer, time frame, and click on Unreviewed PRs - for the list of PRs merged without review in that duration. **On Bitbucket:** * Filter out a small time period. 1. **List Merged PRs:** * Go to the repository's _Pull Requests_ page. * Set the filter to show only "Merged" PRs. 2. **Check Approval Status:** * Open each merged PR. * In the PR details, look for the "Reviewers" section. If there are no approvals listed, the PR was merged without approval. * * * #### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#id-6.-validate-mttr-mean-time-to-repair) 6\. Validate MTTR (Mean Time to Repair) **On Hivel:** Go to Pull Request screen and filter out the team, developer, time frame, and click on MTTR tile - for the list of CFR PRs and their respective MTTR. **On Bitbucket:** * Identify PRs labeled with “hotfix” or similar (e.g., title contains "hotfix", "bugfix", "urgent"). * Calculate cycle time for each hotfix PR (first commit to merge). * Average these times. * * * #### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#id-7.-validate-deployment-frequency) 7\. Validate Deployment Frequency **On Hivel:** Go to Pull Request screen and filter out the team, developer, time frame, and click on Deployment Frequency tile. **On Bitbucket:** * Go to the repository's **Pull Requests** page. * Filter by: * State: **Merged** * Author: The developer's username * Destination branch: master or main * The UI does **not** support filtering by date, so you must manually count PRs merged in your time window by checking their merge dates * Count the total number of PRs merged into the master or main branch during the selected time period. * Calculate deployment frequency as: * * * #### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#id-8.-validate-active-days) 8\. Validate Active Days **On Hivel:** Go to Dev360 screen and filter out on the time period and developer to get a summary of GIT activity done by the developer. **On Bitbucket:** * Identify all days where the developer had any activity: * Commits, Merge Commits, PR opened, PR reviewed, PR merged, PR declined. * **Repository Commits and PRs:** You can manually filter commits and pull requests by author in the repository view, then check the dates to see which actions occurred during the week. * **Local Git Logs:** By cloning the repository and using `git log` or `git shortlog` filtered by author and date, you can see a developer’s commit activity for the week. * * * #### [hashtag](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#id-9.-validate-flashy-reviews) 9\. Validate Flashy Reviews **On Bitbucket:** * For each PR, calculate review time (first review - PR opened). * Identify PRs with review time less than 5 minutes. * Count these PRs. [PreviousBitBucket Integrationchevron-left](https://docs.hivel.ai/integrations/scm/bitbucket/bitbucket-integration) [NextAzurechevron-right](https://docs.hivel.ai/integrations/scm/azure) Last updated 8 months ago * [Prerequisites](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#prerequisites) * [Metrics Definitions](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#metrics-definitions) * [Step-by-Step Validation Process for One Developer](https://docs.hivel.ai/integrations/scm/bitbucket/validation-at-a-metric-level-for-bitbucket#step-by-step-validation-process-for-one-developer) sun-brightdesktopmoon Copy Deployment Frequency = Total PRs merged / Time period (in days) sun-brightdesktopmoon --- # Release Notes - April 2025 | Hivel We’ve been busy behind the scenes, and now it’s time to unveil some game-changing features that will supercharge your month! ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-april-2025#github-copilot-adoption-metrics-assess-the-real-impact) **GitHub Copilot Adoption Metrics - Assess the Real Impact 🚀** Now, it’s easier than ever to measure the true impact of **GitHub Copilot** adoption on your team’s productivity! With the new metrics, you can track usage through **Suggestions vs. Lines of Code**, see the total suggestions made, acceptance rates, and even break it down by programming language. It’s like having a crystal ball for your team's coding future, except it’s backed by data! [_Read more about it here_](https://docs.hivel.ai/ai-adoption/copilot-adoption) [_Steps on how to integrate_arrow-up-right](https://docs.hivel.ai/github-copilot-integration) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FPaFMMnx5rc3H1egKUlir%252Fimage.png%3Falt%3Dmedia%26token%3D14322736-979b-4816-9ff4-059f20aa2877&width=768&dpr=3&quality=100&sign=1b0ace07&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F1mGhpwBdfirAAqQNS2sR%252FScreen%2520Cast%2520Apr%252029%25202025%2520%281%29.gif%3Falt%3Dmedia%26token%3D5b4489fc-1686-45b9-ad96-10e30f5028e4&width=768&dpr=3&quality=100&sign=b0c190a9&sv=2) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-april-2025#original-estimates-in-the-investment-screen) **Original Estimates in the Investment Screen** We’ve introduced a toggle feature that allows you to seamlessly switch between Story Points and Original Estimates in the Investment Screen. With the flag set to Original Estimates, you’ll see effort displayed in **Effort (Days)**, bringing you more clarity across the board, from bar graphs to hover details. The backend works its magic to convert effort data into days (8 hours = 1 day), so your insights are crystal clear. **Let us know** in case you are using the Original Estimates field on Jira, and we can enable it for you. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FVqn7NMBEKOs0Dvsv9eXa%252Fimage.png%3Falt%3Dmedia%26token%3D73d31697-3a9d-49f5-882d-48f9eb6cb945&width=768&dpr=3&quality=100&sign=736eb8b3&sv=2) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-april-2025#work-item-breakdown-at-an-org-level) **Work Item Breakdown - at an org level** In case you missed it, **issues are now work items in Jira**. Why you ask? Maybe someone had an "issue" with it. More about it on [_Jira's community_arrow-up-right](https://community.atlassian.com/forums/Jira-articles/Reimagining-work-in-Jira-to-better-represent-all-teams/ba-p/2854968) _._ With that in mind, **the Work Item Breakdown** dashboard lets you select multiple Jira projects, filter by work types, and group data over time (weekly, monthly, or quarterly). Whether you’re tracking work item volume changes or keeping an eye on the bug-to-feature ratio, it’s never been easier to monitor and adjust your pace. [_Check it out here_arrow-up-right](https://app.hivel.ai/dashboard/defect-density) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252Fsu9ASma45gv0C7Hsc9yZ%252Fimage.png%3Falt%3Dmedia%26token%3Dca44300a-7a5f-4d95-a4e7-0d0de582cd9f&width=768&dpr=3&quality=100&sign=5f99075b&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FzzPVQrYNURfdEfqEmFvu%252Fimage.png%3Falt%3Dmedia%26token%3D4367d1c4-fd94-417a-8615-42aea3ae51d6&width=768&dpr=3&quality=100&sign=3a1ce750&sv=2) ### [hashtag](https://docs.hivel.ai/release-notes/release-notes-april-2025#export-csv-at-a-sub-team-level) **Export CSV at a sub-team level 🗂️** You asked, we delivered! The CSV export in the Cockpit now includes both **parent and sub-teams**, giving you a full and accurate view of your team’s structure. Whether you're tracking high-level performance or zooming in on individual sub-teams, the export has you covered. The best part? It reflects your team hierarchy, so no more missing data. ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F1e5lSAlCDOIyklXQUBgI%252Fimage.png%3Falt%3Dmedia%26token%3D54111205-554d-4b81-adf8-5c711d0ee3b6&width=768&dpr=3&quality=100&sign=55e5c1dd&sv=2) `**Here’s to watching AI adoption grow, and to you finding the perfect balance between innovation and relaxation**`🍃✨ [PreviousRelease Notes - May + June 2025chevron-left](https://docs.hivel.ai/release-notes/release-notes-may-+-june-2025) [NextRelease Notes - March 2025chevron-right](https://docs.hivel.ai/release-notes/release-notes-march-2025) Last updated 10 months ago * [GitHub Copilot Adoption Metrics - Assess the Real Impact 🚀](https://docs.hivel.ai/release-notes/release-notes-april-2025#github-copilot-adoption-metrics-assess-the-real-impact) * [Original Estimates in the Investment Screen](https://docs.hivel.ai/release-notes/release-notes-april-2025#original-estimates-in-the-investment-screen) * [Work Item Breakdown - at an org level](https://docs.hivel.ai/release-notes/release-notes-april-2025#work-item-breakdown-at-an-org-level) * [Export CSV at a sub-team level 🗂️](https://docs.hivel.ai/release-notes/release-notes-april-2025#export-csv-at-a-sub-team-level) sun-brightdesktopmoon sun-brightdesktopmoon --- # On-Prem Installation Guide | Hivel ### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/on-prem-installation-guide#hivel-on-prem-installation-using-docker-compose) **Hivel On-Prem Installation Using Docker Compose** This guide outlines the installation and setup process for running Hivel On-Prem on a Linux-based machine using Docker Compose. The required Docker images are hosted in AWS ECR, and this document assumes you have the necessary access credentials. #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/on-prem-installation-guide#prerequisites) **Prerequisites** Before starting the installation process, ensure you have the following: * **Docker & Docker Compose**: Installed on the target machine. * **JAVA**: Installed on the target machine. * **AWS CLI**: Installed on the target machine. * **AWS ECR Access Credentials**: Provided separately. * **Linux Server**: With sufficient resources (CPU, RAM, Disk Space). * **Network Access**: To required dependencies such as databases or external services. * * * #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/on-prem-installation-guide#step-1-set-up-aws-ecr-authentication) **Step 1: Set Up AWS ECR Authentication** To authenticate and pull the Docker images from AWS ECR, follow these steps: 1. Run the following AWS CLI command to get the login credentials for your ECR: Copy aws ecr get-login-password --region | docker login --username AWS --password-stdin Replace `` with your AWS region (e.g., `us-east-1`), and `` with the URL for your ECR repository. 2. After running the command, you should see the following message: Copy Login Succeeded This confirms that authentication was successful. * * * #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/on-prem-installation-guide#step-2-docker-compose-set-up-configuration-files) **Step 2: Docker Compose Set Up Configuration Files** Now that authentication is complete, you'll need to download and extract the configuration files. **Download the Configuration Package** 1. Run the following AWS CLI command to download the configuration package: Replace `` with the actual name of your AWS S3 bucket. **Extract the Configuration Package** 1. Unzip the downloaded package using the following command: 2. Navigate to the extracted directory: * * * #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/on-prem-installation-guide#step-3-unified-setup-or-manual-configuration) **Step 3: Unified Setup or Manual Configuration** There are two methods to set up Hivel: **Recommended Method (Unified Setup)** For a smoother experience, you can use the **unified README file** located in the root directory of the extracted files. This file will automatically configure both the database and services. **Alternative Method (Manual Configuration)** If you prefer to configure the database and services separately, follow the instructions below: 1. Inside the extracted directory, navigate to the `**database**` folder: 2. Refer to the README file in this folder for detailed, step-by-step instructions on setting up the database. #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/on-prem-installation-guide#step-2-services-setup) **Step 2: Services Setup** Once the database setup is complete, proceed to set up the services. 1. Navigate to the `**hivel-service**` folder: 2. Follow the README file in this folder to configure the services. * * * #### [hashtag](https://docs.hivel.ai/integrations/on-prem-setup/on-prem-installation-guide#additional-notes) **Additional Notes** * **Security**: Ensure that `.env` files and any credentials are stored securely. * **Firewall**: Verify that firewall rules allow traffic on necessary ports. * **Disk Usage**: Monitor disk space to prevent failures. * **Integrations**: Details for integrating external services will be provided once the application is operational. For further assistance or if you encounter any issues, please reach out to us at [**\[email protected\]**envelope](https://docs.hivel.ai/cdn-cgi/l/email-protection#f88b8d8888978a8cb890918e9d94d69991) . [PreviousOn-Prem Setupchevron-left](https://docs.hivel.ai/integrations/on-prem-setup) [NextApplication Setup Guide: User Sign-up and Integrationchevron-right](https://docs.hivel.ai/integrations/on-prem-setup/application-setup-guide-user-sign-up-and-integration) Last updated 1 month ago sun-brightdesktopmoon Copy aws s3 cp s3:///hivel-on-prem.zip ./ --region ap-south-1 Copy unzip hivel-on-prem.zip Copy cd hivel-on-prem Copy cd database Copy cd ../hivel-service sun-brightdesktopmoon --- # How to create Github fine-grained token for Hivel Integration? | Hivel To integrate GitHub with Hivel using a fine-grained token, follow the steps below. This guide ensures a seamless setup, similar to the OAuth-based process but with specific token-based permissions. **Data Access by Hivel** * Hivel accesses the past 60-90 days of metadata and pull requests from active repositories during the initial sync. **Requirements** * Ensure to log in with an account possessing write permissions to relevant GitHub repositories. * Write permissions are mandatory for webhook publication, facilitating real-time data sync. **Best Practice** 1. Opt for a service account rather than an individual-linked account. 2. Service accounts are typically overseen by the company's admin. #### [hashtag](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-create-github-fine-grained-token-for-hivel-integration#steps-to-generate-a-fine-grained-token-on-github) **Steps to generate a Fine-Grained Token on GitHub** 1. **Log in to GitHub** with an account that has write permissions for the repositories you want to integrate. 2. Navigate to **Profile icon** **\>** **Settings > Developer Settings**. 3. Select **Personal access tokens** > **Fine-grained tokens**. 4. Click **Generate new token**. 5. Give the **token name**, preferably 'Hivel' and set an **Expiration** date as needed. 6. Grant the following permissions: 1. Repository permissions 1. Contents (read-only) 2. Metadata (read-only) 3. Pull Requests (read-only) 4. Webhooks (read and write) 2. Organization permissions 1. Members (read-only) 7. Click **Generate token** and **copy** the token immediately. Store it securely and share it with us. 8. Now go back to the homepage and follow the subsequent steps to allow access to fine-grained token: Navigate to **Profile icon** **\>** **Settings > Organizations**. 9. Select the organizations which need to be integrated. 10. Go to Repository settings and scroll to the end of the navigation menu. 11. At the bottom of the navigation menu, select **Personal Access Token > Settings**. 12. Select **Personal access tokens** **\>** **Fine-grained tokens**. 13. On this page, select the option to **Allow access via fine-grained personal access tokens**. That's it, all done! ### [hashtag](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-create-github-fine-grained-token-for-hivel-integration#screenshots-for-reference) Screenshots for reference: ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FfI5dK4CS38oY6D9FPDB1%252FScreenshot%25202025-01-10%2520at%252012.56.25%25E2%2580%25AFPM%2520%281%29.png%3Falt%3Dmedia%26token%3De29323de-26a1-4f95-b480-6a278ba386b6&width=768&dpr=3&quality=100&sign=bef2c65f&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FpMgxcrGkk5V35PwYudfD%252FScreenshot%25202025-01-10%2520at%252012.56.45%25E2%2580%25AFPM%2520%281%29.png%3Falt%3Dmedia%26token%3D5361a8e9-948f-4981-9d85-52a5de019fe4&width=768&dpr=3&quality=100&sign=2d4ec140&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FacUQ8I7OCCHwXsGigbJA%252FScreenshot%25202025-01-10%2520at%252012.57.32%25E2%2580%25AFPM%2520%281%29.png%3Falt%3Dmedia%26token%3D1c168e73-917b-43ff-8cd6-58d58c5ef1d1&width=768&dpr=3&quality=100&sign=edf82e66&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252FriiNbq8RTS19SoQRGOl7%252FScreenshot%25202025-01-10%2520at%252012.57.52%25E2%2580%25AFPM%2520%281%29.png%3Falt%3Dmedia%26token%3D96eb8937-00e5-4502-806c-aae88cb5f206&width=768&dpr=3&quality=100&sign=1168a671&sv=2) ![](https://docs.hivel.ai/~gitbook/image?url=https%3A%2F%2F3057781534-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F5KAIOUWph0JLSgQqbzyT%252Fuploads%252F6wzyueMlpz6GZQYMYUNh%252FScreenshot%25202025-01-10%2520at%25201.55.12%25E2%2580%25AFPM%2520%281%29%2520%281%29.png%3Falt%3Dmedia%26token%3D2cc5e200-0788-4eed-b403-9da934aa9a17&width=768&dpr=3&quality=100&sign=4891ca9&sv=2) [PreviousHow to integrate GitHub with Classic Token?chevron-left](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-integrate-github-with-classic-token) [NextHow to reauthorize Github with a classic token?chevron-right](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-reauthorize-github-with-a-classic-token) Last updated 1 year ago sun-brightdesktopmoon sun-brightdesktopmoon ---