- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2018 10:07 AM
I'm not sure I understand the question. But for tasks, you have an assignment group. That is the group that is responsible for resolving the task. Then on e.g. CI's you can have a field Support group. That is just to know who does the support on this CI. In other words, if there is an incident on this CI, put this group as assignment group. This is one of the reason customers have functionality that when you fills in a CI on an incident, it takes the value of that CI's Support group and put that in the assignment group on the incident (task).
This is my thoughts and I hope this made it a bit clearer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2018 10:26 AM
Sorry -- let me try to help clarify...
We implemented the CMDB first, and the consulting company we used populated the Support Group field on the CI records, and left the assignment group field blank.
When Change Requests are opened, we are taking the value from the CI table, Support Group and populating the RFC with that group name in the field labeled Assignment Group. The field on the Change Record Form is labeled "Assignment Group", but the workflow is written to populate the field with the data for the CI in the Support Group field.
Some of the other modules - Incident, Change, etc use the terminology of Assignment Group.
On the back side, they are all in the same group table... and I think our team is getting hung up on the terminology difference...
What data should be in the Assignment Group Field and which data should be in the Support Group field.
Both fields reference back to the exact same place - the sys_user_group table.
I found one community article that said "pick one -- assignment group or support group, whichever makes the most sense to your company".
I think our team is trying to make them 2 separate things, and are hung up on the names of the fields.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2018 10:39 AM
I agree that it's really confusing. I actually never looked and saw the Assignment group field on the CIs.
I've been looking around trying to see any other information about it, but most people seems as confused as you.
But I would reason like this:
Support Group: This is the group that supports the CI, which means that if there is e.g. an incident this is the group that should be put in Assignement group field on the incident.
Assignment Group: This is mainly just the group that the CI is assigned to. meaning that not all CIs is assigned to a specific user (Assigned to field), but has a group that it's assigned to.
I would also say that in the majority of the cases, the group in these field would be the same thou and not sure if it's worth the effort to keep them up to date for this.
The above is still just my personal thoughts and ideas.
//Göran
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2021 05:15 PM
A support group is the default group responsible for providing initial support while an assignment group can be any group (including support) to achieve desired results.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2021 04:20 AM
Use support group for incident handling related to this CI.
And assignment group (now labeled change group) for handling changes related to this CI.
Ref.: