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

Implement Cost Allocation Engine #114

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

Priority: MEDIUM | Effort: 4 days | Dependencies: Database Schema, Cost Management, Period Management, Activity Tracking

User Story

As a financial system, I want to automatically allocate costs to active issues so that each issue reflects its fair share of operational expenses.

Description

Create the core allocation engine that distributes costs across active issues using the defined algorithm, handles edge cases, and maintains audit trails.

Technical Implementation

  • New Files: markitect/finance/allocation_engine.py, markitect/finance/transaction_manager.py, tests/test_allocation_engine.py

Acceptance Criteria

  • AllocationEngine class with cost distribution logic
  • Equal distribution algorithm implementation
  • Loss carried forward handling
  • Transaction audit trail creation
  • Edge case handling (no active issues, partial periods)
  • Allocation reversal capabilities
  • Performance optimization for large allocations
  • Comprehensive tests for all allocation scenarios

Related Issues

Core functionality for Issue #88 (Cost Tracking for Issues)

**Priority**: MEDIUM | **Effort**: 4 days | **Dependencies**: Database Schema, Cost Management, Period Management, Activity Tracking ## User Story As a financial system, I want to automatically allocate costs to active issues so that each issue reflects its fair share of operational expenses. ## Description Create the core allocation engine that distributes costs across active issues using the defined algorithm, handles edge cases, and maintains audit trails. ## Technical Implementation - **New Files**: markitect/finance/allocation_engine.py, markitect/finance/transaction_manager.py, tests/test_allocation_engine.py ## Acceptance Criteria - [ ] AllocationEngine class with cost distribution logic - [ ] Equal distribution algorithm implementation - [ ] Loss carried forward handling - [ ] Transaction audit trail creation - [ ] Edge case handling (no active issues, partial periods) - [ ] Allocation reversal capabilities - [ ] Performance optimization for large allocations - [ ] Comprehensive tests for all allocation scenarios ## Related Issues Core functionality for Issue #88 (Cost Tracking for Issues)
tegwick added the priority:mediumtype:feature labels 2025-10-03 22:37:19 +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 22:57:15 +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:medium 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#114
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?