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

Idea and concept Cost Tracking for Issues #88

New Issue
Closed
opened 2025-10-03 20:16:38 +00:00 by tegwick · 0 comments
tegwick commented 2025-10-03 20:16:38 +00:00
Owner
Copy Link

I want to come up with an infrastructure for tracking cost and ascribing it to issues.

Here is the basic idea. Let's have a ledger of cost, like monthly costs for

  • hosteurope server instance to run on 10€/month
  • bubble.io plan 32€/month
  • coulomb.social domain 5€/month
  • claude code plan 20€/month
  • gemini plan for specification support 20€/month

Obviously one can also register one-time cost.

Cost shows up as soon as it is registered and is calculated as follows

  • relevance of a cost ticket is from its starting_from_date attribute
  • if cost started in the past (before current period of calculation) old cost increases LossCarriedForward

At the end of each calculation period cumulated cost will be devided by count of active (new and modified) issues and reduces the valuation of those issues.

We will not only track the resulting balance for the issue but keep record of transaction data.

Starting from this idea (epic) a gameplan is to be generated the elements to implement should be created as issues.

I want to come up with an infrastructure for tracking cost and ascribing it to issues. Here is the basic idea. Let's have a ledger of cost, like monthly costs for - hosteurope server instance to run on 10€/month - bubble.io plan 32€/month - coulomb.social domain 5€/month - claude code plan 20€/month - gemini plan for specification support 20€/month Obviously one can also register one-time cost. Cost shows up as soon as it is registered and is calculated as follows - relevance of a cost ticket is from its starting_from_date attribute - if cost started in the past (before current period of calculation) old cost increases LossCarriedForward At the end of each calculation period cumulated cost will be devided by count of active (new and modified) issues and reduces the valuation of those issues. We will not only track the resulting balance for the issue but keep record of transaction data. Starting from this idea (epic) a gameplan is to be generated the elements to implement should be created as issues.
tegwick added this to the Issue Cost Tracking and Estimation project 2025-10-03 20:16:38 +00:00
tegwick changed title from Idea and concept to Idea and concept Cost Tracking for Issues 2025-10-03 21:32:55 +00:00
tegwick moved this to Done in Issue Cost Tracking and Estimation on 2025-10-04 22:57:11 +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
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#88
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?