Used for fairly simple issues or tasks that need to be accomplished and recorded but require no research or analysis. These are generally items that are well known and documented, occur frequently or can be considered routine.

Used for non-recurring issues or tasks that occur but only require brief research or analysis.

Used for issues that are complex or difficult, have previously occurred, or are related to previously open or resolved tickets and typically require data collection and involved analysis to solve and report on.

Used to manage a project, or a large body of work which requires mapped out task planning, collaboration from multiple organization members, and task delegation; specifically useful when some tasks may be dependent on the completion of others.

In addition to the general Ticket Information, projects are composed of project settings, a group of assigned resources, project tasks, tasks, and milestone tasks, that can all be scheduled, and marked as complete. Project Tasks can be organized in a hierarchy and marked as dependent on the completion of other project tasks.

Used to provide users visibility and control over the changes occurring within their organization. After submission, Change Management Requests are delivered to a list of approving users, which must approve or deny the requested change before additional action is taken.

Non-approving users included on this ticket type also receive relevant information via ticket email notification, and are updated when the approval status of the Change Management Request changes.