Fix the renaming of collections
The following behaviour should be fixed
- Create 'Collection A'
- Create 'Collection B'
- Go to the properties of Collection A. Under Membership Rules, go to Add Rule and select 'Include Collections'. Choose 'Collection B'.
- Rename 'Collection B' to 'Collection C'.
- Note that under the Membership Rules, Collection C is still referenced using it's old name.
When a collection is renamed, this change should also be reflected under the 'Membership Rules' of other collections.
I understand this was fixed in 1802. https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1802
"•If a collection is a member of another collection and it is renamed, then the new name is updated under membership rules. "
L U commented
Business impact - inconvenient to have to look up collection ID globally to find out what the included/excluded collection is meant to be.
It would help if fixing this bug, at least, could be given high priority.
It would be nice if we could open sub-collection properties from the membership rule list, a bit like you can drill down into nested AD groups.