It would really help us out if we could roll out new versions of Intune aplications through deployment rings. For example we don't know if a new browser will cause issues with legacy sites. But if we were able to first deploy to an alpha (wait 0 days), and insiders (7 days) group first. We could catch issues and kill the deployment to production (say in 14 days) before issues arrise.
This request is already possible in the Publisher today, kindly see this article for more detail: https://patchmypc.com/custom-options-available-for-third-party-updates-and-applications#ManageAssignments if you have any questions on how to get this setup or how it works, shoot us an email! We can get on a call if need.
@Basiel, as mentioned in your recent ticket, your comments do not relate to the original request of this uservoice and it is a different use case - please create a new idea which better aligns with your idea.
So, when a new package is created it should only
movedelete the assingments when the x days are passed on the current assignment.On new packages it should set all the ring assignments like previous. It should not remove the current assignments until that specific ring is activated on the new package. Otherwise you end up with some rings which do not have that package assigned.
You can use different security groups in the assignments which are activated n + x days (n = day 0). This creates the deployment rings you are asking for.
The problem I see with this is that all assignments are removed from the current package and put on the new one.. ignoring/resetting the timings. If you have f.e. adobe reader which goes to PRD in n + 12 days -and- adobe releases a new package every 10 days the deployment will never hit PRD.
So, when a new package is created it should only move the assingments when the x days are passed on the current assignment.