| |
Results |
|
Report calculations not working with Date fields
|
Report calculations not working with Date fields
|
|
|
|
Bad numeric format for negative value - calculation field in Report definition
|
Bad numeric format for negative value - calculation field in Report definition
|
|
|
|
Summary reports are incorrect for calculation fields when use precision and locale that has comma separator
|
Summary reports are incorrect for calculation fields when use precision and locale that has comma separator
|
|
|
|
Summary report with Include Items setting checked and a calculation crashes IIS
|
A summary report with both the Include Items setting checked on the Additional Options tab and a calculation crashes IIS when the report is run and the user gets logged out.
|
|
|
|
Calendar calculations not working correctly, including Time in State and Average Time to State reports and Escalation Notifications (Regression of DEF246157)
|
Calendar calculations not working correctly, including Time in State and Average Time to State reports and Escalation Notifications (Regression of DEF246157)
|
|
|
|
Calculation of time on a listing report does not export to Excel correctly
|
A time calculation on a listing report such as "Now - Last Modified Date" to display the amount of time since the item was last modified does not export to Excel correctly.
|
|
|
|
Deleted calculation columns still displaying within listing reports
|
Removing calculation columns from report definition listings in composer does not remove the columns from displaying in the user workspace.
|
|
|
|
Summary report in the User Workspace with an elapsed time calculation contains an incorrect result
|
Have some items with time spaced between the time it's submitted against times they are transitioned or closed. In the User Workspace, create a summary report with AVG calculations between the time fields (see attached Word document). Run the report without "Include Items" checked in the Additional Options tab. See that the elapsed times show correctly.
|
|
|
|
Reported Defect: DEF127361: Trend Report months are calculated wrong depending on start month
|
On a trend report with monthly calculations , depending on which date is chosen for the report to begin the resulting report will deliver variable results per month. For example, October may show as anything from 29 to 31 days long, and then all following months will be shifted by the same amount.
|
|
|
|
You may get an incorrect result when calculate with date fields on reports
|
If you are calculating datefields in a report and the result causes an overflow, instead of a message, you get an error or a bizarre value (the details vary with the values). This will be fixed in a future release. As an example, if you have two date fields and set them both to the same value, then a calculation of "datefield1 - datefield2" should display as 0; instead an error is thrown.
|
|
|
