Archived proposals:
- add-trigger-conditions-weekly-subscription: Trigger conditions and weekly subscription
- update-api-consistency: WebSocket auth, optimistic locking, workload defaults
All implementations were already complete in previous commits (f5f870d).
Updated tasks.md with implementation summary.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
23 lines
1.3 KiB
Markdown
23 lines
1.3 KiB
Markdown
## 1. Backend
|
|
- [x] 1.1 Extend trigger schemas/validation to accept composite conditions and new operators/fields
|
|
- [x] 1.2 Implement composite condition evaluation (AND-only) with operator semantics and custom field/formula support
|
|
- [x] 1.3 Extend notify target resolution for group targets, dedup recipients, and exclude triggerer
|
|
- [x] 1.4 Evaluate triggers on due_date/start_date/custom_field updates
|
|
- [x] 1.5 Add weekly report subscription API (get/update) and enforce manual subscription
|
|
- [x] 1.6 Include project members (and owner) in weekly report project scope
|
|
|
|
## 2. Frontend
|
|
- [x] 2.1 Update trigger API types for composite conditions and group targets
|
|
- [x] 2.2 Update TriggerForm/TriggerList to build AND-only rule lists with date range + custom field inputs
|
|
- [x] 2.3 Add MySettings weekly report subscription toggle (with API integration)
|
|
- [x] 2.4 Add i18n strings for new trigger/weekly report UI
|
|
|
|
## 3. Tests
|
|
- [x] 3.1 Backend tests for composite conditions (status+priority, due_date range)
|
|
- [x] 3.2 Backend tests for custom field (formula) conditions
|
|
- [x] 3.3 Backend tests for group notification targeting (department/role/project_members) with dedup/exclude
|
|
- [x] 3.4 Backend tests for weekly report subscription and project-member scope
|
|
|
|
## 4. Validation
|
|
- [x] 4.1 Run targeted pytest in conda and report results
|