"Iteration Length" report with defaults
We found an odd situation when running the default "Iteration Length" report in Insight. We are reporting on RTC data, and some of the iterations only have a Start Date defined and not an End Date. This may be an iteration of Backlog items or something like that -- regardless, it's an allowable situation in RTC.
However, the reports with this situation turn out awful. Insight sets the default "End Date" of the Iteration to December 31, 1969. This means when you run the Iteration Length report, the iterations with no end date show up as being -15,000+ days long. This totally skews the report because other iterations with actual start and end dates are so miniscule in comparison that they barely register on the report.
Is it intentional that Insight defaults the start and/or end date like this? I see that the report is set up to filter out Iterations where Start Date is null or End Date is null, but in this case it's not null... it's just set to an odd default. Is this a DB2-specific behavior?
However, the reports with this situation turn out awful. Insight sets the default "End Date" of the Iteration to December 31, 1969. This means when you run the Iteration Length report, the iterations with no end date show up as being -15,000+ days long. This totally skews the report because other iterations with actual start and end dates are so miniscule in comparison that they barely register on the report.
Is it intentional that Insight defaults the start and/or end date like this? I see that the report is set up to filter out Iterations where Start Date is null or End Date is null, but in this case it's not null... it's just set to an odd default. Is this a DB2-specific behavior?
One answer
Insight didn't set default value for "Start Date" or "End Date", and Insight extracted data from RTC datawarehouse. It is caused that the RTC assigned default value "December 31, 1969" for iteration end date if not defined end date, mean this field is blank in RTC.
In order to show correct report, you need to customize the report, and modify filter expression, something like is not null AND > '1969-12-31'.
In order to show correct report, you need to customize the report, and modify filter expression, something like is not null AND > '1969-12-31'.
We found an odd situation when running the default "Iteration Length" report in Insight. We are reporting on RTC data, and some of the iterations only have a Start Date defined and not an End Date. This may be an iteration of Backlog items or something like that -- regardless, it's an allowable situation in RTC.
However, the reports with this situation turn out awful. Insight sets the default "End Date" of the Iteration to December 31, 1969. This means when you run the Iteration Length report, the iterations with no end date show up as being -15,000+ days long. This totally skews the report because other iterations with actual start and end dates are so miniscule in comparison that they barely register on the report.
Is it intentional that Insight defaults the start and/or end date like this? I see that the report is set up to filter out Iterations where Start Date is null or End Date is null, but in this case it's not null... it's just set to an odd default. Is this a DB2-specific behavior?