Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Data Manager - Priority
Assets Data Manager for Jira Service Management Cloud is currently rolling out in Open Beta and will be available to all Premium + Enterprise sites by end of October 2024.
Priority is an important concept in Assets Data Manager. It occurs in the following locations in the feature:
Data Source Priority
Data Source Priority is the relative priority of a Data Source.
When data sources are reconciled during importing to create Data Manager objects, the data from a high-priority source is selected over the data from a lower-priority source.
Because human error is the cause of most errors in data, data sources that function without human intervention will be prioritized above source data that must be created or maintained manually.
Each data source can be categorized into one of four Data Source Priority Groups that help to determine the priority assigned to that data source.
Data Source Priority Groups
A Data source Priority Group is a broad category that is used to assess the “trustworthiness” of data sources. There are four suggested groups:
Dynamic (Priority 1): Data is accurate, timely, and reliable. It is constantly updated through discovery. An example would be SCCM or BigFix.
Supplementary Dynamic (Priority 2): Data on these sources is updated regularly and used to supplement information from dynamic sources. Data sources categorized in this group include Active Directory, Anti-virus, and inventory sources for mid-range devices.
Secondary Source (Priority 3): Data from these sources are updated dynamically, at times via agents. It is used to augment the existing data in Data Manager, and these sources include virtual devices, Configuration Management Databases (CMDB), and inventory sources such as those from Flexera.
Manual (Priority 4): Data is entered manually on a spreadsheet, such as fixed and lease asset registers.
The Data Source Priority is combined with the Attribute Priority to create the Preferred Value.
Attribute Priority
Attribute priority is the relative priority of an Attribute from a particular Data Source.
As a best practice, Attribute Priority is only used when known issues from a source require an exception to the existing Data Source Priorities.
For example, if there are known issues with a highly-ranked data source that provides poor information for an Operating System, we can add an Attribute Priority and direct the system to use an alternate priority order for this field alone. The Attribute Priority is combined with the Data Source Priority to create the Preferred Value.
Preferred Value
The Preferred Value is a single value from a specific data source and attribute that represents the most trustworthy data available.
The preferred value is calculated using the Attribute Priority, followed by the Data Source Priority.
When an object is created during importing, the preferred values become for each attribute become the attributes of that new object.
Attribute Display Priority
The Attribute Display Priority feature is a feature of the Attribute screen within the Settings section of Data Manager. It allows you to move the visible attributes up and down in the list.
The Attribute Display Priority is not related to - and does not affect - the Attribute Priority that helps to define which information is preferred when an Import is run.
Priority (Attribute Flag)
A Priority attribute flag is an Attribute with an flag attached that identifies that this attribute has been assigned a priority in the Attribute Priority screen.
This flag is only visible in the Attributes screen.
Was this helpful?
Still need help?
The Atlassian Community is here for you.