- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2016 01:08 PM
I've found a lot of posts around making use of the group fields on the Configuration Item [cmdb_ci] table, and I'm also aware that you can create an infinite number of relationships between CIs and Groups.
However, I can't find a recommendation behind the standard group fields available on the base CI table. What would we use each of the three CMDB groups for?
- Assignment Group
- Approval Group
- Support Group
To be honest, I'm mostly confused about Assignment Group and Support Group. By name alone, I can guess the proper use for "Approval Group," but I can't see a difference between "Assignment" and "Support" (and I don't want to make things harder down-the-line because I chose incorrectly at the start).
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2016 01:19 PM
Not all the OOB columns are going to be meaningful to all (or even most... or even some).
In this case, the fields are doing *nothing* but (potentially) holding a value anyway... so I'd just say use them as you understand / imagine them.
If you don't need both, remove one from the forms. No biggie.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2016 01:28 PM
Assigned to is also important for Software Asset Management, as this is the value used for user based licensing to calculate compliance. This value synchronizes between the Asset and CI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2016 01:42 PM
That's good to know! I wonder if the dictionary-level dependency between CI.Assigned To and Ci.Company is actually meaningful, then.
Either way, if Assigned To and Assignment Group on the CI table aren't connected like they are on all of the [task] tables, then it's probably just misleading Pending more details about how CI.Assignment Group is really used, it continues to look like CI.Support Group is the best bet for tactical ownership (with CI.Approval Group used in approval workflows).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2016 12:51 AM
It's mainly personal implementation choice. There is no logic implemented OOTB.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2019 05:53 AM
Since this kind of question is part of the CIS - ITSM certification exam, I think there is definitely a differnce between both fields.
I agree anyway with your reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2016 01:19 PM
Not all the OOB columns are going to be meaningful to all (or even most... or even some).
In this case, the fields are doing *nothing* but (potentially) holding a value anyway... so I'd just say use them as you understand / imagine them.
If you don't need both, remove one from the forms. No biggie.