Skip to content
This repository was archived by the owner on Sep 3, 2025. It is now read-only.

Conversation

@metroid-samus
Copy link
Contributor

Prerequisite for implementing parallel cost model execution for cases, allowing both the new cost model and classic cost model to run simultaneously and maintain separate cost records.

In this PR, we:

  • replace the cost_type default column with a cost_model_type column:
    • model_type=new is the response cost type associated with the new cost model
    • model_type=classic is the response cost type associated with the classic cost model
    • model_type=None is a cost type that is not associated with response time. This would cover manually-added costs accumulated over the course of the incident.
  • Update scheduler code to create a case response cost type and case response costs if none exist.
  • Update the UI to indicate which cost types are tied to response costs.
Screenshot 2025-03-05 at 2 38 02 PM Screenshot 2025-03-05 at 2 38 13 PM

@metroid-samus metroid-samus added the enhancement New feature or request label Mar 5, 2025
@metroid-samus metroid-samus self-assigned this Mar 5, 2025
@metroid-samus metroid-samus changed the title Migrate from using default cost type to assigning cost type by cost model. Migrate from using default case cost type to assigning cost type by cost model. Mar 6, 2025
@metroid-samus metroid-samus requested a review from mvilanova March 6, 2025 23:02
…o-cost-model-based-cost-type

Signed-off-by: Avery <averyl@netflix.com>
@metroid-samus metroid-samus merged commit d993d4f into main Mar 10, 2025
9 checks passed
@metroid-samus metroid-samus deleted the enhancement/migrate-from-default-cost-type-to-cost-model-based-cost-type branch March 10, 2025 21:20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants