# Why is count of PRs reviewed or merged is different across screens?

In Hivel, the **PRs Reviewed** and **PRs Merged** metrics track PRs that were only opened by a specific author

* **PRs Reviewed:** Pull requests opened by the filtered author that have been reviewed by anyone, regardless of who performed the review.
* **PRs Merged:** Pull requests opened by the filtered author that have been merged, no matter who completed the merge.

These metrics apply across all screens in Hivel where you can view PR metrics, giving a clear picture of the activity on PRs initiated by the specified author.

#### Additional Filtering in the Pull Requests Screen

In the [<mark style="color:purple;">**Pull Request**</mark> <mark style="color:purple;"></mark><mark style="color:purple;">screen</mark>](/using-hivel/pull-request.md), you have additional filtering options. Here, you can also filter to see:

* PRs that were **reviewed by** the filtered author.
* PRs that were **closed by** the filtered author.

<figure><img src="/files/I15CaHdadj1lm30472A5" alt="" width="111"><figcaption></figcaption></figure>


---

# 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/why-is-count-of-prs-reviewed-or-merged-is-different-across-screens.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.