Idea ID: 2737421

Trend reports using an arbitrary date field

Status : Delivered
over 6 years ago

While submit date works for many cases, it doesn't work in all scenarios where other date fields like close date or a user created field might fit better. Reports like tasks completed in a specific month would become possible. An arbitrary data field would remove all restrictions from the functionality.

Parents
  • As discussed on ichange, I think this is very hard to implement via advanced reporting. The problem is that the results of advanced reporting cannot be used in trend reports. Create an advanced report whose result is displaying a trend in a distribution report is very hard (and quite inconvenient, since the modifying the date range or the grouping (week/ day) would imply modifying the xml on the server side). So IMO, it is inaccurate to consider this addressed. If you consider there is enough demand to address it, you could either enable trend reports on auxiliary tables (therefore being able to use the result of an advanced report to trend on), or make the user able to choose the date field in the trend report.
Comment
  • As discussed on ichange, I think this is very hard to implement via advanced reporting. The problem is that the results of advanced reporting cannot be used in trend reports. Create an advanced report whose result is displaying a trend in a distribution report is very hard (and quite inconvenient, since the modifying the date range or the grouping (week/ day) would imply modifying the xml on the server side). So IMO, it is inaccurate to consider this addressed. If you consider there is enough demand to address it, you could either enable trend reports on auxiliary tables (therefore being able to use the result of an advanced report to trend on), or make the user able to choose the date field in the trend report.
Children
No Data