Hivel
Hivel
Hivel
  • 👋Welcome to Hivel
  • 🚀Using Hivel
    • ⭐Cockpit Pro
      • ⬇️How to download reports
      • 🤝Meetings Breakdown
    • 🏃‍♀️Activity
    • ⛑️Work Item Breakdown
    • ➕Hivel Quadrant
    • 💰Investment
      • Issue Age
      • How to set up Products & Allocation tabs in the Investment Screen?
      • How to add Custom fields for Product and Allocation Label in Jira
    • 💎Performance Appraisal
    • 🎯Pull Request
      • Comments Categorization
      • Review Cycles
      • How to exclude outlier commits and PRs?
    • 🐞Quality (SonarQube)
    • ♨️Coding Hotspots
    • ⚽Goals
    • 👩‍🏫Process
    • 🖥️Coding
      • Understanding Rework, New Work, and Maintenance
    • 👨‍🎓Dev360
    • 🔔Slack Alerts and Notifications
  • Copilot Adoption
  • 📊Metrics & Definitions
    • 🚅Speed
      • Deployment Frequency
      • Coding Time
      • Review Time
      • Merge Time
      • Cycle Time
      • Pickup time
    • 💯Quality
      • Change Failure Rate
      • Maintenance
      • Rework
      • Mean Time to Restore (MTTR)
      • PRs merged without review
      • PR Reviewed
      • Flashy Reviews
      • PRs > 400 LoC
    • 📈Throughput
      • New Work%
      • How are Active Days calculated
      • PRs Open, PRs Ready to Review or Merge
  • 🔗Integrations
    • List of all integrations
    • GitHub
      • How do I Signup using GitHub?
      • How to integrate additional Github accounts?
      • How to create Github fine-grained token for Hivel Integration?
      • How to reauthorize Github with a service account?
      • GitHub-Alternate SignUp Method Instructions
      • How to re-initiate GitHub integration with Hivel
    • Gitlab
      • Gitlab Server
      • Gitlab Cloud
      • How to ensure Gitlab token has access to required groups/repositories
    • BitBucket
      • BitBucket Integration
    • Jira
      • How to integrate Jira Cloud with Hivel
      • How to Re-authorize Jira in Hivel?
        • Page
      • How to Integrate Jira with OAuth 2.0
      • How to Re-authorize Jira with OAuth 2.0
      • How to integrate Jira Server with Hivel
    • Azure DevOps
    • Google Calendar
      • How to integrate Google Calendar in Hivel
    • Microsoft Outlook
    • Slack
    • SonarQube
    • Okta
    • Jenkins
    • Jenkins Freestyle Integration with Ansible and Hivel Webhook
  • On-Prem Setup
    • On-Prem Installation Guide
    • Jira On-Prem
    • Gitlab On-Prem
    • SonarQube On-Prem
    • Application Setup Guide: User Sign-up and Integration
    • Creating a Bitbucket App Password
    • On-Prem Outlook Integration
  • Github Copilot Integration
  • ⚒️Setup
    • Sign Up
      • How to sign up to Hivel?
    • Users
      • How to invite more users to use Hivel?
      • How to add or update an user's email id?
      • How to merge users?
      • How to update the name of a user?
      • Can I see the data of a user or repo that I don’t have access to on my SCM tool?
      • How to archive users?
    • Teams
      • How to create teams?
      • How to delete a team?
      • How to modify a team?
      • How to create sub-teams?
    • Role-Based Access Control (RBAC)
    • ⚙️Configurations Explained
      • 🌴Branch Configurations
      • 🐞Hotfix Configurations
        • Track hotfixes via patch version pattern
      • Other Configurations
  • ⏭️Upcoming Features and Enhancements
  • Release Notes
    • Release Notes
      • Release Notes - October 2024
      • Release Notes - November 2024
      • Release Notes - December 2024
      • Release Notes - January 2025
      • Release Notes - February 2025
      • Release Notes - March 2025
      • Release Notes - April 2025
  • 🔐API Documentation
    • 🏁Tracking Releases and Incidents with Hivel
    • Deployment API
    • Create Incident API
  • 🌟Insights and Best Practices
    • Developer's Guide to Hivel
    • 🎖️Best Practices for Software Development Efficiency
    • 🧹Jira Best Practices
    • Tips and tricks to improve performance
      • How to improve Speed
        • What to do if my Cycle Time is high?
        • What to do if my Coding Time is high?
        • What to do if my Review Time is high?
        • What to do if my Merge Time is high?
      • 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?
        • How to address and prevent unreviewed PRs
        • Strategies to Reduce Mean Time to Restore (MTTR)
        • Best Practices for Team Ownership in Code Review
        • How to identify root cases of high change failure rates?
        • Building a feedback loop for continuous code improvement
      • How to improve planning and throughput
        • Leveraging data for more effective sprint planning
        • What metrics can I use to prevent developer burnout?
      • How to track, manage, and reduce technical debt?
      • What are the impacts of context switching on developer productivity and how to reduce it?
      • How to build a data-driven culture of Engineering?
      • How to balance speed and quality?
  • FAQs
    • Why can't I remove a user from a team?
    • How to change a team owner?
    • How do we account for weekends in the metrics?
    • Are draft PRs considered for calculation of coding/cycle time?
    • Why do some metrics like PRs reviewed or merged have more than 100%?
    • How to mark leaves & absences?
    • Where can I see average PR sizes?
    • How do I link Pull Requests to Issues
    • Why is count of PRs reviewed or merged is different across screens?
    • Why is data of some members are not visible?
    • Why is there an abnormal spike in Cycle Time?
    • Why some of the repositories are not imported or synced?
    • How to get a report of monthwise developer activity metrics?
    • How can I see the progress against my goals?
    • How to see all the metrics by sprints or releases?
    • Why are commits done today are not reflecting immediately
    • Why Product and Allocation's previous data is not reflecting?
    • Why cannot I see cycle time against developers even though they have commits?
    • Why do some Jira issues show as spillover in Hivel even though they were completed in Jira?
    • Why is pickup time not included in cycle time?
    • How can I add a template in dashboards for my org to follow?
    • Can I get a detailed report of all the activity done by developer per day?
    • How do I exclude a PR from rework/maintenance/new work calculation?
    • Why don't I see delivery accuracy for Kanban boards?
    • Why do I see "NA" in the percentage change of a metric?
    • Why do I see "No existing user found" message while login
    • 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?
    • How to validate the data on Hivel?
    • How to measure impact of Copilots using Hivel?
Powered by GitBook
On this page
  • Sections:
  • Filters:

Was this helpful?

  1. Using Hivel

Investment

View the effort breakdown across issue types and investment across epics to ensure they are aligned to business objectives.

PreviousHivel QuadrantNextIssue Age

Last updated 1 month ago

Was this helpful?

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:

| | |

Sections:

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

  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.

  1. Sprint-level drilldown: Click on a particular sprint to view detailed fields of each Jira issue within that sprint.

  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.

All the sections in Investment follow a similar above behaviour of filtering on issuetype, sprints and arriving at the drilldown.

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.

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.

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.

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.

The pie charts offer a combined view of values from selected sprints, providing an easy overview of sprint performance across multiple sprints.

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 on how to set up this functionality, please refer to .

For more information or assistance, please contact our support team at .

🚀
💰
this article
support@hivel.ai
Issue
Epic
Product and Allocation
Delivery
Products section
Allocation section