...
In Jira, Automation can be used to automatically assign the newly created assets to other objects, such as services or applications, based on the values of the assigned Tags. This ensures seamless integration of cloud resources into the broader IT management framework, reducing manual effort and increasing operational efficiency.
Historical Data
To provide flexible options for managing historical asset data in Jira Assets, allowing organizations to retain valuable information while accurately tracking the status of Azure resources.
By default, the app retains all asset data in Jira Assets, even after the resources are removed from Azure. However, this may not always align with your specific needs. There are three main options for configuring how historical data is managed:
Keeping All Historical Data (Default Setting):
In this option, once an Azure resource is synchronized into Jira Assets, it remains there permanently, even if the resource is deleted from Azure. The removal of data from Jira must be done manually.
Tracking Deletion Using Status and Other Fields:
This is often the most useful option for common scenarios. Like the default setting, all data is retained in Jira Assets. However, when a resource is deleted from Azure, its status in Jira Assets is updated to "Inactive" (or another custom value).
The setup is flexible: any field can be updated to reflect specific changes. For instance, you can create a "Deleted On" field and update it with the timestamp when the resource was removed from Azure.
This allows you to retain deleted data and their references to tickets, services, etc., while ensuring that you can filter out resources that no longer exist in Azure.
...
TBD
...
How to Set Up Historical Data Tracking
Step 1: Create Custom Fields for Status Tracking
On your object types in Jira Assets, create fields to hold the status information. You can name and configure these fields with different values. For example, you might use a field called "Status" with two options: Active and Inactive.
Step 2: Configure the Import Definition
Go to the Import Definition and select Edit Mapping. Locate your object type, click the three dots (…), and choose Edit Object Type Mapping.
Step 3: Set the Updater for Missing Objects
In the object type mapping, select the Updater for Missing Objects option. Choose the field you created for status (e.g., "Status") and set the target value (e.g., "Inactive").
You can also configure the Threshold Number, which determines how many times the object must be missing before the update is triggered. Set it to "0" for an immediate update when a resource is missing.
...
Automatic Removal of Deleted Data:
If you prefer that only the current state of Azure resources is kept in Jira Assets, you can use the Remove for Missing Objects option. With this setting, assets will be automatically deleted from Jira if they no longer exist in Azure. However, keep in mind that this will also remove references to these assets from tickets, services, and other related objects.
Handling Deleted Objects Across Multiple Subscriptions in the same Root Object
If you are importing from multiple Azure subscriptions and using a shared root object in Jira Assets, you may encounter issues with the status approach. The "missing object" check only applies to individual imports, which could lead to the inactivation or removal of asset objects that still exist in other subscriptions.
Solution:
To avoid this issue, consider one of the following options:
Use Separate Root Objects: Create distinct root objects for each subscription to keep them separate in Jira Assets.
Single Import for Multiple Subscriptions: If you want to manage multiple subscriptions under one root object, consider using a single import that aggregates data from all your subscriptions. (Note: This feature is under development and will be released in a future update.)
Billing Data
TBD