Difference between revisions of "Auto-Assignment"
From SDU
m |
m |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | __NOTOC__ | ||
| + | [[Category:Configuration]] | ||
| + | {{Global Header}} | ||
| + | {{Global Announcement}} | ||
| + | |||
| + | == Overview == | ||
Auto-assignment is the functionality that is intended to automatically set the ticket Assignee based on various factors, such as End User Location, Workshift, and Analyst availability to name a few. The process flow below helps to understand the thought process behind the auto-assignment process. | Auto-assignment is the functionality that is intended to automatically set the ticket Assignee based on various factors, such as End User Location, Workshift, and Analyst availability to name a few. The process flow below helps to understand the thought process behind the auto-assignment process. | ||
[[Image:Auto-assignment.png]] | [[Image:Auto-assignment.png]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 03:25, 27 July 2008
To make corrections or additions to this article, select the edit tab above.
To discuss or ask questions about this article, select the discussion tab above.
To discuss or ask questions about this article, select the discussion tab above.
Overview
Auto-assignment is the functionality that is intended to automatically set the ticket Assignee based on various factors, such as End User Location, Workshift, and Analyst availability to name a few. The process flow below helps to understand the thought process behind the auto-assignment process.
