# Why do some Jira issues show as spillover in Hivel even though they were completed in Jira?

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.

{% hint style="info" %}
To configure the issues to have resolutions and resolution dates set while closing, please refer to this [<mark style="color:purple;">documentation</mark>](https://confluence.atlassian.com/jirakb/jira-issues-need-a-resolution-826873869.html) from Atlassian on the same.
{% endhint %}


---

# 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/pr-issues-and-workflow-faqs/why-do-some-jira-issues-show-as-spillover-in-hivel-even-though-they-were-completed-in-jira.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.