# How to validate the data on Hivel?

Data validation is essential to ensure the accuracy and reliability of information synchronized between Hivel and your integrated tools. This guide walks you through the validation process for  SCMs and Project Management tools.

### Validating SCM data

1. Log into your Hivel account
2. Navigate to the [<mark style="color:purple;">**Activity screen**</mark>](https://app.hivel.ai/dashboard/activity), where you'll find detailed developer activity breakdowns

#### Validating individual activities

1. Select any commit or PR open bubble in the visualization<br>

   <figure><img src="/files/dMY81tnPGKvWfUi1Nc5Q" alt="" width="186"><figcaption></figcaption></figure>
2. Review the filtered list in the right pane showing the specific entry<br>

   <figure><img src="/files/xV5Jw1sbnEPVGIniqreR" alt="" width="286"><figcaption></figcaption></figure>
3. Click on the entry to access the corresponding item in your SCM
4. Verify that the activity date in Hivel matches the date recorded in your SCM

#### Validating activity patterns

1. Select a time period containing both active and inactive days for a specific developer.<br>

   <figure><img src="/files/ShSaezB71O28VL6HL7B3" alt="" width="563"><figcaption></figcaption></figure>
2. Compare the activity pattern in Hivel with the SCM records
3. Verify that active and inactive periods align between both systems<br>

   <figure><img src="/files/CJTCLlimeNpdmpayshZS" alt="" width="375"><figcaption></figcaption></figure>

### Validating project management data

1. Access the [<mark style="color:purple;">**Investment**</mark>](https://app.hivel.ai/dashboard/investment-profile) screen in Hivel
2. Select an active board and sprint for validation

**Method 1: Individual ticket validation**

1. Locate specific tickets in the sprint details table<br>

   <figure><img src="/files/oS8rk2ZxuBctRCDoobH8" alt="" width="133"><figcaption></figcaption></figure>
2. Click on the ticket name to open it in your project management tool<br>

   <figure><img src="/files/aK4RTzvnVkLAFqMv6rhi" alt="" width="180"><figcaption></figcaption></figure>
3. Compare the ticket details between both systems<br>

   <figure><img src="/files/3q5b7CovO5FetXx13n98" alt=""><figcaption></figcaption></figure>

**Method 2: Sprint overview validation**

1. Check the total ticket count displayed in the table's right corner<br>

   <figure><img src="/files/F4pIBUORpgyECOFc0vlI" alt="" width="117"><figcaption></figcaption></figure>
2. Compare this number with the ticket count in your project management tool by applying the appropriate sprint filter.
   1. Ensure that for completed sprints, you only consider the issues resolved within the sprint. For example, In Jira if the sprint start date is 2nd Dec and end date is 9th Jan, add this to the JQL: `resolved >= "2024-12-02" AND resolved <= "2025-01-10"`<br>

      <figure><img src="/files/tQeQp0UG6HjgwwldnGs9" alt="" width="563"><figcaption></figcaption></figure>

      1. **Why is this necessary?** We only count tickets completed within their original sprint to avoid double-counting tickets that spill over into subsequent sprints.<br>
3. Verify that both systems show the same number of tickets for the sprint<br>

   <figure><img src="/files/F2ONdSRfauPv8D61OeYv" alt="" width="95"><figcaption></figcaption></figure>

This validation process helps ensure that Hivel accurately reflects your development and project management activities, maintaining data integrity across all integrated tools.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hivel.ai/faqs/metrics-and-data-faqs/how-to-validate-the-data-on-hivel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.