Content
View differences
Updated by Jens Ulferts over 3 years ago
* Introduce date\_alert to Notification::REASONS
* add 3 columns to the `notification_settings` table for start & due date as well as for overdue
* add default on the database layer
* Adds start\_date, due\_date and overdue notification setting into existing notification settings.
* start\_date set to 24 (hours)
* due\_date set to 24 (hours)
* overdue set to null
* if this is done via defaults on the database layer, default should be set for all properties of the table and the value setting in `Users::SetAttributesServices` should be replaced by that.
* validate values for the columns are positive integer values
* Add 3 properties for startDate, dueDate and overdue
* Setting can either be nil or an ISO8601 duration
* internally hours (integer) are stored
* Transformation has to happen when rendering but also when parsing
* Adapt API documentation
* add 3 columns to the `notification_settings` table for start & due date as well as for overdue
* add default on the database layer
* Adds start\_date, due\_date and overdue notification setting into existing notification settings.
* start\_date set to 24 (hours)
* due\_date set to 24 (hours)
* overdue set to null
* if this is done via defaults on the database layer, default should be set for all properties of the table and the value setting in `Users::SetAttributesServices` should be replaced by that.
* validate values for the columns are positive integer values
* Add 3 properties for startDate, dueDate and overdue
* Setting can either be nil or an ISO8601 duration
* internally hours (integer) are stored
* Transformation has to happen when rendering but also when parsing
* Adapt API documentation