Report Overspill topics per iteration/release

Questions & Answers
1

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 :smiley:
I would really appreciate any inspiration.
Thanks in advance!
Best regards
Cati

2

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

3

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.

4

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,

5

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.