feat(projects): per-project standard due date override (PMS-345)

David commented

2026-06-16 17:09:53 +02:00

Owner

Add a nullable projects.default_due_business_days column (0..=365, 0 disables) that lets a single project override the tenant-wide scheduling/default_due_business_days setting, so the standard due date for new tasks can be sourced from the project as well as from the tenant SLA settings. When a task is created without a due date, the project override wins (a value of 0 disables the default for that project); a NULL override inherits the tenant-wide setting, which itself falls back to no default. Surface the field on ProjectResponse and accept it on CreateProjectRequest/UpdateProjectRequest with the same 0..=365 range validation as the tenant setting (HTTP 422 on out-of-range), threading it through the project INSERT/SELECT/UPDATE queries.

#PMS-345

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

Add a nullable projects.default_due_business_days column (0..=365, 0 disables) that lets a single project override the tenant-wide scheduling/default_due_business_days setting, so the standard due date for new tasks can be sourced from the project as well as from the tenant SLA settings. When a task is created without a due date, the project override wins (a value of 0 disables the default for that project); a NULL override inherits the tenant-wide setting, which itself falls back to no default. Surface the field on ProjectResponse and accept it on CreateProjectRequest/UpdateProjectRequest with the same 0..=365 range validation as the tenant setting (HTTP 422 on out-of-range), threading it through the project INSERT/SELECT/UPDATE queries. #PMS-345 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>