This is definitely needed!
Let us know if there are specific cases where you’d like to be able to look at costs by the tags when they were applied vs. the current state of tags viewed retroactively. Understanding your needs will help ensure we cover the specifics for you.
An error occurred while saving the commentMichael Waddell commented
In order to match up resource costs against our internal project-based budgeting, we need a way to associate resources flexibly and in a way that can be changed retrospectively as needed. So far, tags is the best approach we've found, but it's not quite what we need.
Our ideal solution would be something like the following. Every resource gets a "billing project" tag. This tag could default to blank when a new resource is created, or it could be initialized to match the "resource group name". When this tag is changed, you are asked to specify if the change applies only to the current billing cycle (the default) or if it applies retroactively (and if so, how many months backwards from the current billing cycle it applies to). These changes should immediately be visible in the Cost Management graph/export UI.
We’ll definitely add this.