You have a duplicate listed above but the below FR predates the one you posted.
https://www.jamf.com/jamf-nation/feature-requests/6831/add-showrecoverykey-to-require-filevault-2-in-security-privacy-payload
Good catch. I voted it up. And also made a comment in that FR so that the one I posted gets marked as a duplicate.
https://www.jamf.com/jamf-nation/feature-requests/7753/ability-to-skip-true-tone-setup-assistant-on-macbook-pro-2018
11/6/18 EDIT: Although not marked as implemented as of this edit, apparently it made it into Jamf Pro 10.8. Striking this one off the list.
I may have missed it, but does this list have "InstallApplication" and "InstallEnterpriseApplication"?
EDIT:
Here's the latter: https://www.jamf.com/jamf-nation/feature-requests/7699/add-support-for-installenterpriseapplication-in-10-13-6-and-later
Support for the former might be nice for environments that cannot upgrade to 10.13.6, but I doubt we'll see it.
An open framework for constructing payloads and commands similar to the FR below would solve most, if not all of these issues.
Break Up Multi-MDM-Payload GUI Payloads
@milesleacy While that FR has my vote, it's not really going to solve the fact that Jamf hasn't implemented and/or supported these MDM payloads/commands. Jamf already provides the ability for people to upload their own custom profiles. Your FR would make that easier, but that's not really the point though (of this list anyways). Jamf should have these MDM features already built into Jamf. How they see fit to best do that, I'll leave up to them. And there's also the fact that some of these MDM features require just a bit more support than just filling in a payload domain, key and value.
All that to say, I'd like to keep this list specific to MDM features that aren't implemented by Jamf. Not MDM improvements that Jamf could make of which there are a ton.
@bpavlov , I agree. Jamf needs to be quicker with deploying their “easy button” of GUI checkboxes, etc. Thats a perennial problem. We’re still waiting for all 10.13 MDM functions to be natively supported here on the eve of 10.14. Given that timeline is a proven bugbear, I’m looking for an alternative.
Providing an open framework to enter commands, payloads, settings, and values semi-manually would provide those of us who provide zero-day support for Apple operating systems within our organizations with the ability to use any and every command, payload, and setting as soon as Apple release them into the wild.
We can write profiles by hand, manually sign them and upload them to Jamf, but that is not scalable or delegable to junior staff. As for commands, AFAIK, Jamf does not provide any provision for hand-writing and uploading an MDM command.
I understand this list/discussion is about GUI support in the Jamf web app, however I’m proposing something flexible and a bit more manual vs nothing at all.
