Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-16342

Enhancing the Analysis function of Assets Data Manager to filter only updated records and attributes

XMLWordPrintable

    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem

      Currently, to check for updated records and their sources, you can navigate to the Analysis page(Data Manager > Analysis), select the relevant object(the object will be a hyperlink and clickable) to view the object list, and then drill down into a specific object and click on the All Data Sources tab. The bold values indicate the preferred record, allowing you to see which value was selected from which data source. Additionally, you can use the advanced search on the list page to filter objects, such as finding all "Ownership" records from a specific data source. To track changes for a specific attribute, modify the attribute settings and enable it for snapshots. Once enabled, each import via the cleanse and import client will include that attribute in the snapshot. You can then view changes in the object's history section or analyze trends over time using timeline charts in the dashboard.

      However, the following things are not possible:

      • Filter only only those records that have been updated/ changed, when reconciling between two sources.
      • Specific attribute that has been updated (for example, Ownership change, or object last accessed changed etc)

      Suggested Solution

      Introduce a better way to check only the updated records and attributes at a glance.

      Why This Is Important

      Use Case

      If there are 1000 records in AD, we have to run/cleanse/import all 1000 records each time. Out of those 1000 records, 5 devices have been upgraded to Windows 11 (Attribute: Windows OS → changed from Windows 10 to Windows 11), we are interested only in those changed records. Checking records individually or tracking a specific attribute, while useful, isn't practical when you have numerous records and data.

      Workaround

      None at this point

              Unassigned Unassigned
              cf3a9e2a2246 Diptajeet Datta
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: