You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea behind this RFE is to have a way to notify the admin that may be some conflict in the profiles to be deployed.
It may be some done through some button in the UI to "Check Conflicts" or done automatically every time a new profile is added/modified.
One simple example: Two profiles with the exactly same priority, being applied to exactly the same users/groups/hosts/hostgroups which have different settings for Shotwell background. One sets the background to be white, the other sets the background to be black.
Current situation: As the desktop profiles are ordered alphabetically, one will take preference ... while the best option would be to make the admins aware of such scenario.
The text was updated successfully, but these errors were encountered:
A very good point. We're kind of queuing enhancements of this nature after we finish Chrome(ium) support, this is something we should definitively batch.
olivergs
changed the title
RFE: Create a way for the admins to know whether some conflict happens between the profiles that are going to be deployed
Create a way for the admins to know whether some conflict happens between the profiles that are going to be deployed
May 11, 2020
The idea behind this RFE is to have a way to notify the admin that may be some conflict in the profiles to be deployed.
It may be some done through some button in the UI to "Check Conflicts" or done automatically every time a new profile is added/modified.
One simple example: Two profiles with the exactly same priority, being applied to exactly the same users/groups/hosts/hostgroups which have different settings for Shotwell background. One sets the background to be white, the other sets the background to be black.
Current situation: As the desktop profiles are ordered alphabetically, one will take preference ... while the best option would be to make the admins aware of such scenario.
The text was updated successfully, but these errors were encountered: