It would be nice to let the saved SQL report define default date values, relative to the time the report is being run, for any "date" fields. Often such date fields require entering a date eg. 6 months past or similar, and having the default value in would make it much less likely for the user to choose the wrong date.
Created attachment 77643 [details] [review] Bug 21200: Allow default values for saved SQL report "date" parameters Let the saved SQL report define default date values, relative to the time the report is being run, for any "date" fields. Often such date fields require entering a date eg. 6 months past or similar, and having the default value in would make it much less likely for the user to choose the wrong date. The default value is put after the "date" text, separated by a pipe. Format for the default date value is either "now", or "<value> <unit>", where value is a positive or negative integer value, and unit is one of "hour", "day", "week", "month", "year". Not putting in the default value would behave the same as before, leaving the date input field empty. For example: SELECT count(*) FROM items WHERE DATE(dateaccessioned) BETWEEN <<Start|date|-6 month>> AND <<End|date|now>> Would default to the last 6 months.
Failing this due to tests, and because bug 21215 will make coding this easier.