kincses/service-finder
1
0
Fork 0
Code Issues 33 Pull Requests Packages Projects 2 Releases Wiki Activity

Implement Historical Data (occurrence_date fields) #152

New Issue
Open
opened 2026-03-26 09:14:29 +01:00 by kincses · 0 comments
kincses commented 2026-03-26 09:14:29 +01:00
Owner
Copy Link

Objective: Implement historical data support by adding and using fields for cost tracking and analytics.

Target Files:

  • Database: Add to relevant tables if missing
  • Backend models: Update SQLAlchemy models with date fields
  • API schemas: Update request/response schemas to include dates
  • Frontend: Update forms to capture occurrence dates
  • Analytics: Update queries to use date ranges

Acceptance Criteria:

  1. Cost records include field
  2. Historical trend analysis works with date filters
  3. Frontend forms capture and display occurrence dates
  4. Analytics service uses dates for time-based calculations
  5. Database queries efficiently filter by date ranges

Execution Steps:

  1. Audit database tables for missing date fields
  2. Create database migration if needed
  3. Update backend models and schemas
  4. Modify frontend forms to include date inputs
  5. Update analytics queries to use date ranges
  6. Test historical data entry and retrieval

Technical Details:

  • Estimated effort: 2 days
  • Dependencies: Task 2.3 (analytics service)
  • Priority: P1 (enables time-based analysis)
**Objective:** Implement historical data support by adding and using fields for cost tracking and analytics. **Target Files:** - Database: Add to relevant tables if missing - Backend models: Update SQLAlchemy models with date fields - API schemas: Update request/response schemas to include dates - Frontend: Update forms to capture occurrence dates - Analytics: Update queries to use date ranges **Acceptance Criteria:** 1. Cost records include field 2. Historical trend analysis works with date filters 3. Frontend forms capture and display occurrence dates 4. Analytics service uses dates for time-based calculations 5. Database queries efficiently filter by date ranges **Execution Steps:** 1. Audit database tables for missing date fields 2. Create database migration if needed 3. Update backend models and schemas 4. Modify frontend forms to include date inputs 5. Update analytics queries to use date ranges 6. Test historical data entry and retrieval **Technical Details:** - Estimated effort: 2 days - Dependencies: Task 2.3 (analytics service) - Priority: P1 (enables time-based analysis)
kincses added this to the Phase 2: Dashboard & Analytics Wiring milestone 2026-03-26 09:14:29 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Role: Admin
👑 Role: Admin
 Role: User
👤 Role: User
 Scope: API
🔌 Scope: API
 Scope: Backend
🏗️ Scope: Backend
 Scope: Core
⚙️ Scope: Core
 Scope: Database
Scope: Frontend
🖥️ Scope: Frontend
 Scope: Robot
Status: Blocked
Status: Done
Status: In Progress
Status: To Do
Type: Bug
🐞 Type: Bug
 Type: Database
💾 Type: Database
 Type: Feature
✨ Type: Feature
 Type: Model
🧠 Type: Model
 Type: Refactor
Type: Refactor
Type: Script
📜 Type: Script
No Label Scope: Backend Scope: Database Scope: Frontend Status: To Do Type: Feature
Milestone
No items
No Milestone Phase 2: Dashboard & Analytics Wiring
Projects
Clear projects
No project
Assignees
Clear assignees
kincses
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kincses/service-finder#152
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?