Current Deferral Limit settings for policies are a fixed date/time. For ongoing policies this is a pain because, once the date passes, you either lose a deferral period entirely, or you have to extend the deferral date indefinitely, which means the policy may never be applied. I would like to be able to set a deferral limit of %n number of days since first deferral or %n number of times from first deferral, allowing a set grace period before policy enforcement regardless of specific calendar dates.
The problem posted in this Feature Request is about how we have some very important policies, such as software updates, that really need to be run on macOS devices in a timely fashion. However, our end users do important work so we want them to control when they're interrupted by computer reboots. Because the current implementation has a deferral date deadline, whenever users are offsite because of holidays or leave events, they come back to work and cannot be immediately productive because policies need to run based on the expired deferral date. This leads to end user irritation and ruins the Apple seamless experience. This can also lead to data loss and work productivity impacts. Please let me know if I have misunderstood anything from the comments.
A solution idea presented here is to make the deferral for a certain number of days after each time a Policy is triggered, so that this deferral is specific to a user/device instead of specific to the Policy. Thank you to everyone who is sharing workaround ideas in the comments!
Right now we are investigating how enhancements surrounding this end user experience may correlate to our current Jamf Pro initiatives. We don't have any features specifically planned for upcoming releases, but we are leaving this as Under Review because we are continuing to ideate on how we can help solve this problem. If we discover this does not map with any of our roadmap initiatives for Jamf Pro, we'll reevaluate the status at that time.