# Report Overspill topics per iteration/release **URL:** \ **Category:** Questions & Answers\ **Created:** [November 17, 2025, 5:06pm UTC](https://community.eazybi.com/t/report-overspill-topics-per-iteration-release/20487 "2025-11-17T17:06:05Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Cati](https://community.eazybi.com/letter_avatar_proxy/v4/letter/c/22d042/32.png) [@Cati](https://community.eazybi.com/u/Cati)\ **Post date:** [November 17, 2025, 5:06pm UTC](https://community.eazybi.com/t/report-overspill-topics-per-iteration-release/20487/1 "2025-11-17T17:06:05Z")
Hello, I need a little help for a report, as I don’t know how to proceed myself, so I thought I’d ask here in the hope that someone can help me. I am currently trying to create a report that shows all our overspill topics. These should be divided according to the iteration in which they were planned and then the iteration in which they were actually resolved. I imagine it as a bar chart, with the iterations on the x-axis (we have stored them separately as releases, but eazyBI does not consider them a timeline) and the number of issues on the y-axis. Therefore, my idea is to split the bars per iteration into the tickets that were planned for that iteration (not created, but really only those that were assigned to the iteration as a release) and then the overspill topics on top of them. I hope I was able to explain it understandably 😃 I would really appreciate any inspiration. Thanks in advance! Best regards Cati ---
**Author:** ![gerda.grantina](https://community.eazybi.com/user_avatar/community.eazybi.com/gerda.grantina/32/1994_2.png) [@gerda.grantina](https://community.eazybi.com/u/gerda.grantina)\ **Post date:** [November 21, 2025, 3:19pm UTC](https://community.eazybi.com/t/report-overspill-topics-per-iteration-release/20487/2 "2025-11-21T15:19:49Z")
Hi @Cati To help with your overspill report, please clarify: 1. What field do you use to track iterations (Fix Version or custom field)? 2. How do you identify which iteration an issue was originally planned for vs. actually completed in? Best regards, Gerda // [support@eazybi.com](mailto:support@eazybi.com) ---
**Author:** ![Cati](https://community.eazybi.com/letter_avatar_proxy/v4/letter/c/22d042/32.png) [@Cati](https://community.eazybi.com/u/Cati)\ **Post date:** [November 24, 2025, 4:23pm UTC](https://community.eazybi.com/t/report-overspill-topics-per-iteration-release/20487/3 "2025-11-24T16:23:37Z")
Hi, 1. we use the field Fix Version 2. we must not change the Fix Version after the issue is “In Progress”. If it is an overspill topic we change the end date, so that we have a realistic enddate but also the FixVersion the issue was originally planned for. ---
**Author:** ![gerda.grantina](https://community.eazybi.com/user_avatar/community.eazybi.com/gerda.grantina/32/1994_2.png) [@gerda.grantina](https://community.eazybi.com/u/gerda.grantina)\ **Post date:** [November 26, 2025, 8:31am UTC](https://community.eazybi.com/t/report-overspill-topics-per-iteration-release/20487/4 "2025-11-26T08:31:48Z")
Hi @Cati To help you with this question, there is still some clarification needed: - Would the issue with the changed end date automatically mean that it is an overspill issue? - How do you define the iteration in which they were planned and then the iteration in which they were actually resolved? Kindly, ---
**Author:** ![Cati](https://community.eazybi.com/letter_avatar_proxy/v4/letter/c/22d042/32.png) [@Cati](https://community.eazybi.com/u/Cati)\ **Post date:** [December 3, 2025, 1:30pm UTC](https://community.eazybi.com/t/report-overspill-topics-per-iteration-release/20487/5 "2025-12-03T13:30:27Z")
Hi @Gerda.Grantina, - No, a change in the end date does not automatically mean it is an overspill issue. Only if the new end date is outside the Fix Version specified in the ticket. - The iteration it is planned for is set as the FixVersion and recorded as a release with the dates indicating when it starts and ends. You have to determine the iteration in which it will be resolved yourself based on the end date. ---
**Author:** ![gerda.grantina](https://community.eazybi.com/user_avatar/community.eazybi.com/gerda.grantina/32/1994_2.png) [@gerda.grantina](https://community.eazybi.com/u/gerda.grantina)\ **Post date:** [February 20, 2026, 7:18am UTC](https://community.eazybi.com/t/report-overspill-topics-per-iteration-release/20487/6 "2026-02-20T07:18:38Z")
Hi @Cati , - Is the overspill issue identified when an issue’s **End date** is later than the **Fix version release date**? - Could you share a few concrete examples of how this should be calculated? Ideally, several issue examples that include: - Fix version and their release date - Issue End date It would be helpful to see cases where: - Some issues were planned for a version but released later than planned - Other issues were released within the planned version timeframe This would help clarify the expected calculation logic.