coulomb/markitect-main
2
0
Fork 0
Code Issues 60 Pull Requests Actions Projects 12 Releases 1 Wiki Activity

Implement Cost Tracking Database Schema #110

New Issue
Closed
opened 2025-10-03 22:37:15 +00:00 by tegwick · 0 comments
tegwick commented 2025-10-03 22:37:15 +00:00
Owner
Copy Link

Priority: HIGH | Effort: 2 days | Dependencies: None

User Story

As a system administrator, I want a robust database schema for financial data so that all cost tracking information is properly structured and maintains data integrity.

Description

Create the foundational database schema for the cost tracking system, including tables for cost items, periods, transactions, and allocations with proper relationships and constraints.

Technical Implementation

  • New Files: markitect/finance/init.py, markitect/finance/models.py, markitect/finance/migrations/001_create_cost_tables.sql, tests/test_finance_models.py
  • Modified Files: Database schema files, Migration system

Acceptance Criteria

  • Complete database schema with all required tables
  • Proper foreign key relationships and constraints
  • Database migration scripts for schema creation
  • SQLAlchemy models with validation
  • Decimal precision for financial calculations
  • Audit trail capabilities (created_at, updated_at)
  • Database indexes for performance
  • Unit tests for model relationships and validation

Related Issues

Foundation for Issue #88 (Cost Tracking for Issues)

**Priority**: HIGH | **Effort**: 2 days | **Dependencies**: None ## User Story As a system administrator, I want a robust database schema for financial data so that all cost tracking information is properly structured and maintains data integrity. ## Description Create the foundational database schema for the cost tracking system, including tables for cost items, periods, transactions, and allocations with proper relationships and constraints. ## Technical Implementation - **New Files**: markitect/finance/__init__.py, markitect/finance/models.py, markitect/finance/migrations/001_create_cost_tables.sql, tests/test_finance_models.py - **Modified Files**: Database schema files, Migration system ## Acceptance Criteria - [ ] Complete database schema with all required tables - [ ] Proper foreign key relationships and constraints - [ ] Database migration scripts for schema creation - [ ] SQLAlchemy models with validation - [ ] Decimal precision for financial calculations - [ ] Audit trail capabilities (created_at, updated_at) - [ ] Database indexes for performance - [ ] Unit tests for model relationships and validation ## Related Issues Foundation for Issue #88 (Cost Tracking for Issues)
tegwick added the priority:hightype:feature labels 2025-10-03 22:37:15 +00:00
tegwick added this to the Issue Cost Tracking and Estimation project 2025-10-03 22:38:41 +00:00
tegwick moved this to Done in Issue Cost Tracking and Estimation on 2025-10-04 21:41:46 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
priority:critical
Critical priority issue
 priority:high
High priority issue
 priority:low
Low priority issue
 priority:medium
Medium priority issue
 status:active
Issues currently being worked on
 status:blocked
Issues blocked by dependencies
 status:done
Completed issues
 status:review
Issues under review
 status:todo
Issues ready to be worked on
 type:bug
Bug report
 type:documentation
Documentation update
 type:enhancement
Enhancement to existing feature
 type:feature
New feature request
 wish
Feature wishlist item - idea to be discussed and refined
 wish/archived
Archived or rejected wishlist item
 wish/discussion
Wishlist item currently being discussed and refined
 wish/draft
Wishlist item with initial draft specification
 wish/ready
Wishlist item ready to become a regular issue
No Label priority:high type:feature
Milestone
No items
No Milestone
Projects
Clear projects
No project Issue Cost Tracking and Estimation
Assignees
Clear assignees
bubble-reader tegwick
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coulomb/markitect-main#110
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?