Version tracking in Jira Assets

[Joshua Robinson]

Working in Jira Assets we've created a CMDB structure where CIs roll up into several prod environments.  So, we have Terraform baselined at 1.0 across all prod environments. A ticket is then entered to update Terraform. The CI is selected, previous version is 1.0, new version is 2.0. Deployment takes longer due to schedule impacts so Terraform is currently at 2.0 in prod A & B. However, 1.0 in prod C. Ticket is closed as that's the way it's going to stay for a period of time. Ticket goes to baseline, and it updates the Terraform object to 2.0 in prod A & B. Prod C is dropped from the baseline. 

Question is: how do we track the different versions across the different environments so that they're mutually exclusive within the same CI record? Or, do we have to create a "Terraform" CI for each environment? 

[Vitalii Rybka]

Hi @Joshua Robinson,

While Marc's approach works, you actually have several options beyond creating separate CIs:

Option 1: Environment-Version Attributes Add custom attributes like "Prod_A_Version", "Prod_B_Version", "Prod_C_Version" to your Terraform CI. This tracks version drift in one object.

Option 2: Deployment Relationship Model (Recommended)

• Keep your base Terraform CI
• Create "Deployment" objects that link CI → Environment with version info
• Structure: Terraform CI → deployed to → Environment A (v2.0), Environment B (v2.0), Environment C (v1.0)

Option 3: Environment-Specific CIs Marc's suggestion - clean separation but can lead to object proliferation.

Why Option 2 is best:

• Maintains single source of truth for the CI
• Tracks deployment history and current state
• Handles your exact version drift scenario
• Follows CMDB best practices

The key insight: model the deployment relationship rather than cramming everything into the CI attributes.

This gives you proper audit trails and handles cases where environments lag behind or need rollbacks.

Need help setting up the object schema for this approach? Happy to walk through it!

DM me if you want more detailed guidance on the relationship modeling!

[Marc - Devoteam]

Hi @Joshua Robinson 

Welcome to the community.

Yes you would have to create a CI for each environment.

[Joshua Robinson]

Thank you for the welcome and the confirmation.