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

Implement Issue Activity Tracking #113

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

Priority: MEDIUM | Effort: 2 days | Dependencies: Database Schema

User Story

As a system, I want to automatically track issue activities so that I can identify which issues are active during each cost allocation period.

Description

Build an activity tracking system that monitors issue creation, modification, and other activities to determine which issues should receive cost allocations.

Technical Implementation

  • New Files: markitect/finance/activity_tracker.py, tests/test_activity_tracker.py
  • Modified Files: Existing issue management hooks

Acceptance Criteria

  • ActivityTracker class with event capture
  • Integration with existing issue management system
  • Activity type classification (created, modified, commented)
  • Period-based activity queries
  • Historical activity data migration
  • Activity deduplication logic
  • Performance optimization for large datasets
  • Tests with mock issue activities

Related Issues

Data source for Issue #88 (Cost Tracking for Issues)

**Priority**: MEDIUM | **Effort**: 2 days | **Dependencies**: Database Schema ## User Story As a system, I want to automatically track issue activities so that I can identify which issues are active during each cost allocation period. ## Description Build an activity tracking system that monitors issue creation, modification, and other activities to determine which issues should receive cost allocations. ## Technical Implementation - **New Files**: markitect/finance/activity_tracker.py, tests/test_activity_tracker.py - **Modified Files**: Existing issue management hooks ## Acceptance Criteria - [ ] ActivityTracker class with event capture - [ ] Integration with existing issue management system - [ ] Activity type classification (created, modified, commented) - [ ] Period-based activity queries - [ ] Historical activity data migration - [ ] Activity deduplication logic - [ ] Performance optimization for large datasets - [ ] Tests with mock issue activities ## Related Issues Data source for Issue #88 (Cost Tracking for Issues)
tegwick added the priority:mediumtype:feature labels 2025-10-03 22:37:18 +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:13 +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#113
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?