Skip to content
Snippets Groups Projects
Commit 0d229710 authored by Jared Hancock's avatar Jared Hancock
Browse files

New names for initial deps and topics

This will hopefully remove some of the confusion from the repeated
names in the various initial data
parent c6b12155
No related branches found
No related tags found
No related merge requests found
...@@ -228,6 +228,10 @@ class Topic { ...@@ -228,6 +228,10 @@ class Topic {
$errors['priority_id']='You must select a priority'; $errors['priority_id']='You must select a priority';
if($errors) return false; if($errors) return false;
foreach (array('sla_id','form_id','page_id','pid') as $f)
if (!isset($vars[$f]))
$vars[$f] = 0;
$sql=' updated=NOW() ' $sql=' updated=NOW() '
.',topic='.db_input($vars['topic']) .',topic='.db_input($vars['topic'])
......
...@@ -8,25 +8,25 @@ ...@@ -8,25 +8,25 @@
# #
# NOTE: The department listed first by ID# will be the default department # NOTE: The department listed first by ID# will be the default department
# #
# NOTE: ------------------------------------
# The very first group listed in this document will be the primary
# department of the initial staff member -- the administrator.
--- ---
- id: 1 - id: 1
name: Support name: Support
signature: | signature: |
Support Dept Support Department
ispublic: 1 ispublic: 1
sla_id: 0
tpl_id: 0
# The email_id and autoresonse_emaiL_id are reuired, but will be set to
# the default email later in the install process
email_id: 0
autoresp_email_id: 0
- id: 2 - id: 2
name: Billing name: Sales
signature: | signature: |
Billing Dept Sales and Customer Retention
ispublic: 1 ispublic: 1
sla_id: 1 sla_id: 1
tpl_id: 0
email_id: 0 - id: 3
autoresp_email_id: 0 name: Maintenance
signature: |
Maintenance Department
ispublic: 0
...@@ -28,11 +28,15 @@ ...@@ -28,11 +28,15 @@
# depts: (list<Department<id>>) id's of the departments to which the group # depts: (list<Department<id>>) id's of the departments to which the group
# should initially have access # should initially have access
# #
# NOTE: ------------------------------------
# The very first group listed in this document will be the primary group of
# the initial staff member -- the administrator.
--- ---
- isactive: 1 - isactive: 1
name: Admins name: Overseers
notes: | notes: |
System overlords System overlords. These folks (initially) have full control to all the
departments they have access to.
can_create_tickets: 1 can_create_tickets: 1
can_edit_tickets: 1 can_edit_tickets: 1
can_delete_tickets: 1 can_delete_tickets: 1
......
...@@ -21,19 +21,34 @@ ...@@ -21,19 +21,34 @@
- isactive: 1 - isactive: 1
ispublic: 1 ispublic: 1
dept_id: 1 dept_id: 1
sla_id: 1
priority_id: 2 priority_id: 2
form_id: 0 topic: General Inquiry
topic: Support
notes: | notes: |
Tickets that primarily concern the support deparment Questions about products or services
- isactive: 1 - isactive: 1
ispublic: 1 ispublic: 1
dept_id: 1 dept_id: 1
sla_id: 0 priority_id: 1
topic: Feedback
notes: |
Tickets that primarily concern the sales and billing departments
- id: 10
isactive: 1
ispublic: 1
dept_id: 1
priority_id: 2 priority_id: 2
form_id: 0 topic: Report a Problem
topic: Billing notes: |
Product, service, or equipment related issues
- pid: 10
isactive: 1
ispublic: 1
dept_id: 1
sla_id: 1
priority_id: 3
topic: Access Issue
notes: | notes: |
Tickets that primarily concern the sales and billing deparments Report an inability access a physical or virtual asset
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment