feat: complete issue fixes and implement remaining features
## Critical Issues (CRIT-001~003) - All Fixed
- JWT secret key validation with pydantic field_validator
- Login audit logging for success/failure attempts
- Frontend API path prefix removal
## High Priority Issues (HIGH-001~008) - All Fixed
- Project soft delete using is_active flag
- Redis session token bytes handling
- Rate limiting with slowapi (5 req/min for login)
- Attachment API permission checks
- Kanban view with drag-and-drop
- Workload heatmap UI (WorkloadPage, WorkloadHeatmap)
- TaskDetailModal integrating Comments/Attachments
- UserSelect component for task assignment
## Medium Priority Issues (MED-001~012) - All Fixed
- MED-001~005: DB commits, N+1 queries, datetime, error format, blocker flag
- MED-006: Project health dashboard (HealthService, ProjectHealthPage)
- MED-007: Capacity update API (PUT /api/users/{id}/capacity)
- MED-008: Schedule triggers (cron parsing, deadline reminders)
- MED-009: Watermark feature (image/PDF watermarking)
- MED-010~012: useEffect deps, DOM operations, PDF export
## New Files
- backend/app/api/health/ - Project health API
- backend/app/services/health_service.py
- backend/app/services/trigger_scheduler.py
- backend/app/services/watermark_service.py
- backend/app/core/rate_limiter.py
- frontend/src/pages/ProjectHealthPage.tsx
- frontend/src/components/ProjectHealthCard.tsx
- frontend/src/components/KanbanBoard.tsx
- frontend/src/components/WorkloadHeatmap.tsx
## Tests
- 113 new tests passing (health: 32, users: 14, triggers: 35, watermark: 32)
## OpenSpec Archives
- add-project-health-dashboard
- add-capacity-update-api
- add-schedule-triggers
- add-watermark-feature
- add-rate-limiting
- enhance-frontend-ux
- add-resource-management-ui
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,23 @@
|
||||
# Change: Add Resource Management UI
|
||||
|
||||
## Why
|
||||
HIGH-006: The Resource Management module backend API exists but there is no frontend UI. Managers cannot visualize team workload distribution, making capacity planning difficult.
|
||||
|
||||
Issues addressed:
|
||||
- HIGH-006: 資源管理模組前端 UI 未開發
|
||||
|
||||
## What Changes
|
||||
- Create WorkloadPage.tsx with workload heatmap visualization
|
||||
- Create WorkloadHeatmap.tsx component for color-coded user load display
|
||||
- Create WorkloadUserDetail.tsx component for detailed task breakdown
|
||||
- Add /workload route to App.tsx router
|
||||
- Add navigation link in Dashboard or sidebar
|
||||
|
||||
## Impact
|
||||
- Affected specs: resource-management
|
||||
- Affected code:
|
||||
- `frontend/src/pages/WorkloadPage.tsx` - new page
|
||||
- `frontend/src/components/WorkloadHeatmap.tsx` - new component
|
||||
- `frontend/src/components/WorkloadUserDetail.tsx` - new component
|
||||
- `frontend/src/services/workload.ts` - new API service
|
||||
- `frontend/src/App.tsx` - add route
|
||||
@@ -0,0 +1,26 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Workload Heatmap UI
|
||||
The system SHALL provide a visual workload heatmap interface for managers.
|
||||
|
||||
#### Scenario: View workload heatmap
|
||||
- **GIVEN** user is logged in as manager or admin
|
||||
- **WHEN** user navigates to /workload page
|
||||
- **THEN** system displays a heatmap showing all accessible users' workload
|
||||
- **AND** each user cell is color-coded by load level (green/yellow/red)
|
||||
|
||||
#### Scenario: Navigate between weeks
|
||||
- **GIVEN** user is viewing the workload page
|
||||
- **WHEN** user clicks previous/next week buttons
|
||||
- **THEN** the heatmap updates to show that week's workload data
|
||||
|
||||
#### Scenario: View user workload details
|
||||
- **GIVEN** user is viewing the workload heatmap
|
||||
- **WHEN** user clicks on a specific user's cell
|
||||
- **THEN** a modal/drawer opens showing that user's task breakdown
|
||||
- **AND** tasks show title, project, time estimate, and due date
|
||||
|
||||
#### Scenario: Filter by department
|
||||
- **GIVEN** user is a system admin
|
||||
- **WHEN** user selects a department from the filter
|
||||
- **THEN** the heatmap shows only users from that department
|
||||
@@ -0,0 +1,29 @@
|
||||
# Tasks: Add Resource Management UI
|
||||
|
||||
## 1. API Service
|
||||
- [x] 1.1 Create workload.ts service with API calls for heatmap, user detail, and my workload
|
||||
|
||||
## 2. Components
|
||||
- [x] 2.1 Create WorkloadHeatmap.tsx component
|
||||
- Display users in a grid/table
|
||||
- Color-coded load levels (green=normal, yellow=warning, red=overloaded)
|
||||
- Show allocated/capacity hours and percentage
|
||||
- [x] 2.2 Create WorkloadUserDetail.tsx component
|
||||
- Show user's task list for the selected week
|
||||
- Display task title, project, time estimate, due date
|
||||
|
||||
## 3. Page
|
||||
- [x] 3.1 Create WorkloadPage.tsx
|
||||
- Week selector (navigate between weeks)
|
||||
- Department filter (for admins) - Note: Basic implementation, can be enhanced
|
||||
- Integrate WorkloadHeatmap component
|
||||
- Click user to show WorkloadUserDetail in modal/drawer
|
||||
|
||||
## 4. Integration
|
||||
- [x] 4.1 Add /workload route to App.tsx
|
||||
- [x] 4.2 Add navigation link in Layout sidebar
|
||||
|
||||
## 5. Testing
|
||||
- [x] 5.1 Verify heatmap loads correctly
|
||||
- [x] 5.2 Verify user detail modal shows tasks
|
||||
- [x] 5.3 Verify week navigation works
|
||||
Reference in New Issue
Block a user