Retain Report Settings When Archiving Between Instances

Feature Request: Retain Report Settings When Archiving Between Instances

Summary:
Enable users to archive a cost volume from one instance (e.g., development) and restore it into another instance (e.g., production) while preserving all associated report settings and options. This ensures that configured reporting behavior seamlessly carries over across environments without manual reconfiguration.

Problem Statement:
Currently, when organizations develop cost volumes and associated report settings in a development environment, those settings are not reliably retained when the cost volume is moved into a production system. This forces users to manually recreate report options and configurations, which is time-consuming, error-prone, and discourages proper use of a dev→prod workflow.

Proposed Solution:
Support archiving of cost volumes in a way that includes all related report configurations (filters, layout, calculation options, display settings, etc.).
When restoring an archived cost volume into a different instance, automatically apply the archived report settings so that the cost volume behaves identically to the source environment.
Provide validation and mapping for environment-specific values (e.g., references, instance-specific resources) and surface clear warnings or prompts when certain settings cannot be applied.
Offer an option to preview which report settings will be transferred and which require user intervention before completing the restore.

Benefits:
Reduces manual rework when promoting cost volumes from development to production.
Improves consistency and data integrity by ensuring reports behave the same across environments.
Encourages best practices with separate dev and prod instances by making promotion low-friction.
Decreases the risk of configuration errors that could impact analysis, compliance, or customer deliverables.
Saves time for power users and administrators responsible for maintaining standardized reporting setups.