Jamf Pro has a powerful feature called 'extension attributes' which can be attached to computers or mobile devices. They function basically as custom fields and can contain various data types. This is great to have as a reporting option, and their status is returned by the expanded inventory collection and stored in the MongoDB. Therefore, we can build reports from their values.
Today, the reporting UI has extension attributes listed as a criteria UI, but actually viewing results and reporting on them doesn't appear to be working properly.
This should probably be done after all of the other reporting bug fixes.
Tasks:
Ensure the mappings from the device JSON returned by the Jamf Pro API matches the scout device field mappings in the /common directory.
Make sure that extension attribute values are saved properly when creating reports.
Figure out why the report results aren't returning the proper results based on the extension attribute status.
Fix any issues with reporting on extension attributes.
PR Ready When:
We are able to generate accurate reports based on extension attribute status
We are able to update reports based on extension attribute status
Jamf Pro has a powerful feature called 'extension attributes' which can be attached to computers or mobile devices. They function basically as custom fields and can contain various data types. This is great to have as a reporting option, and their status is returned by the expanded inventory collection and stored in the MongoDB. Therefore, we can build reports from their values.
Today, the reporting UI has extension attributes listed as a criteria UI, but actually viewing results and reporting on them doesn't appear to be working properly.
This should probably be done after all of the other reporting bug fixes.
Tasks:
/commondirectory.PR Ready When: