Date offsets incorrectly applied when batch reports
Description
When running batch reports immediately, rather than scheduling them for some time in the future, a date offset of one day before today is automatically applied. Absolute dates are ignored. This breaks the ability to run availability reports for end dates in the past and will break running jasper reports with date parameters in the same way. Bug has probably been there since the report-api code was introduced.
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Donald Desloge February 8, 2011 at 12:42 PM
Now that the feature-reporting-api-parameters branch has been merged this issue should be resolved.
Donald Desloge February 7, 2011 at 4:31 PM
Now that we have merged your work with the report parameter api is this still a bug. I've tried created a couple of reports with different end dates and this seems to work. If this is the case I'll go ahead and resolve this issue as fixed.
When running batch reports immediately, rather than scheduling them for some time in the future, a date offset of one day before today is automatically applied. Absolute dates are ignored. This breaks the ability to run availability reports for end dates in the past and will break running jasper reports with date parameters in the same way. Bug has probably been there since the report-api code was introduced.