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.
If the resolution date is on of before the sprint end date, then they are considered as completed.
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.
To configure the issues to have resolutions and resolution dates set while closing, please refer to this documentation from Atlassian on the same.
PreviousWhy cannot I see cycle time against developers even though they have commits?NextWhy is pickup time not included in cycle time?
Last updated