ticket Table (262)

This table contains the tickets (requests) of the system. Its purpose should be evident.

Fields

NameDescriptionTypeNull
idThe primary key (auto-incremented)PK
connect_idIf a ticket is connected to another ticket, this field is set to the id of the 'master' ticket.FK ticket
titleThe title of the ticket.String(255)
created_atWhen the ticket was created.DateTime
last_changedThe last time the ticket was modified.DateTime
activateWhen the ticket should be activated, if it is postponed.DateTime
closed_atWhen the ticket was closed.DateTime
created_byThe id of the user who created the ticket. 1 (system user) if the ticket was created externallyFK ejuser
authorA string representing the author of the ticket (same as author of first message).String(255)
owned_byThe id of the user who owns the ticket. 1 (system user) if the ticket is unassigned.FK ejuser
categoryThe id of the category a ticket is in.FK ej_category
orig_categoryThe id of the category the ticket was posted to.FK ej_category
slevelThe securitylevel of the ticket.Enum TicketSecurityLevel
statusThe status of the ticket. I.e. active/closed/postponed/deletedEnum TicketBaseStatus
ticket_statusUser defined ticket statusFK ticket_status
cust_idThe reference to the customer. NULL or -1 if ticket is not connected to customer.FK person
priorityThe reference to the ticket_priority table.FK ticket_priority
orig_priorityThe reference to the initial priority for the ticket.FK ticket_priority
alert_levelThe alert level for the ticket. Matches the level value of the ticket_alert table.Short
alert_timeoutThe datetime for when the ticket should jump to the next alert_level.DateTime
alert_stopIf the esclatation was stopped, this fields indicates how many seconds left before the next escalation level. -1 if escalation is running.Int
read_by_ownerThe datetime for when the ticket last was read by the owner.DateTime
first_read_by_ownerThe datetime for when the ticket first was read by the current owner.DateTime
first_read_by_userThe datetime for when the ticket first was read by a user.DateTime
read_by_customerThe datetime for when the ticket was read by the customer.DateTime
filter_idThe reference to the mailbox from which the ticket was created. NULL or -1 if the ticket was not created by a mailbox.FK mail_in_filter
display_filterThe name of the mailbox from which the ticket was created. Only for displaypurposesString(255)
replied_atThe datetime for when the ticket was replied to. I.e. the first external message added to the ticket.DateTime
time_to_replyThe time (minutes) between when the ticket was created and when it was replied to. Calculated based on priority's timeframe.Int
time_to_closeThe time (minutes) between when the ticket was created and when it was closed. Calculated based on priority's timeframe.Int
real_time_to_replySame as time_to_reply, but not calculated based on priority.Int
real_time_to_closeSame as time_to_close, but not calculated based on priority.Int
read_statusWhether the owner has read the ticket or not (red, yellow, green).Enum TicketReadStatus
has_attachmentBoolean indicating if this ticket has one or more attachments.Bool
deadlineDeadline for ticket.DateTime
filter_addressAddress of receiving filter (mail box)String(255)
dbi_agent_idIntegration agent (eJournal)FK dbi_agent
dbi_keyThe primary key for the integrated entry in the external datasource.String(255)
dbi_last_syncronizedLast external synchronization.DateTime
dbi_last_modifiedWhen the entry was last modified.DateTime
originWhat is the origin of this ticketEnum TicketOrigin
time_spent_internallyThe total time (seconds) within the priority’s office hours the ticket has been in an open status (configurable), not including current stateInt
time_spent_externallyThe total time (seconds) within the priority’s office hours the ticket has been in a external waiting status (configurable), not including current stateInt
time_spent_queueThe total time (seconds) within the priority’s office hours the ticket has been in a queue status, not including current stateInt
real_time_spent_internallyThe total time (seconds) within 24x7 the ticket has been in an open status (configurable), not including current stateInt
real_time_spent_externallyThe total time (seconds) within 24x7 the ticket has been in a external waiting status (configurable), not including current stateInt
real_time_spent_queueThe total time (seconds) within 24x7 hours the ticket has been in a queue status, not including current stateInt
time_spent_calculatedWhen the time_spent value was last calculated.DateTime
num_repliesThe number of replies (messages) to the customer for this request.Int
num_messagesThe total number of messages for this request.Int
from_addressThe from-address used when this ticket got created, e.g. by emailString(4000)
tagsArray of references to the Tags recordsFKArray
contact_idThe company of the person in the cust_id field, if that person belongs to a companyFK contact
languageThe language of the first external messageString(10)
sentimentThe sentiment index of the last external messageInt
sentimentConfidenceThe sentiment confidence of the last external messageInt
form_submission_idIf this ticket was created from a form submission, this field will point to that recordFK form_submission
created_by_workflow_idThe workflow this request/ticket was created byFK workflow
suggestedCategory_idSuggestion for categorization, based on the text of the message (AI)FK ej_category
origHumanCategory_idWill contain the category id selected by the user, when having the choice of using the suggested category or manually selecting a categoryFK ej_category
sale_idReference to sale tableFK sale
project_idReference to project tableFK project
time_spentThe total time (minutes). Aggregated time spent from ticket's messages. Read-only for external use.Int
ticket_typeTickettype of the ticketFK ticket_type

ticket table relationship diagram

Communication channel leading to ticket being created

| Origin | Comment | |---|---| | 0 | We just have no idea. Maybe it was too long ago | | 1 | Email | | 2 | SMS | | 3 | Telefacsimile | | 4 | Phone call to human operator | | 5 | Facebook wall | | 6 | Tweet tweet | | 7 | Internal, by human operator | | 8 | Direct by customer through Customer Centre web pages | | 9 | Auto-generated from e-marketing link | | 10 | Automatic processes in Service |

Status of a ticket / request

This is the internal value. The user-defined ticket status is saved to ticket.ticket_status

| Status | Comment | |---|---| | 0 | Unknown / uninitialized | | 1 | Request is currently active | | 2 | Request has been closed | | 3 | Request has been postponed | | 4 | Deleted | | 5 | Request has been merged with another request. See connect_id |

Indexes

FieldsTypesDescription
idPKClustered, Unique
connect_idFKIndex
created_atDateTimeIndex
created_byFKIndex
owned_byFKIndex
categoryFKIndex
orig_categoryFKIndex
statusEnumIndex
ticket_statusFKIndex
cust_idFKIndex
priorityFKIndex
orig_priorityFKIndex
alert_timeoutDateTimeIndex
filter_idFKIndex
read_statusEnumIndex
dbi_agent_idFKIndex
dbi_keyString(255)Index
dbi_last_syncronizedDateTimeIndex
dbi_last_modifiedDateTimeIndex
tagsFKArrayFull text
created_by_workflow_idFKIndex
ticket_typeFKIndex

Relationships

TableDescription
chat_sessionThis table contains chat sessions.
contactCompanies and Organizations.
dbi_agentDBI agent settings
ej_categoryThis table contains categories, in which tickets are categorized. The categories are organized in a hierarchial manner.
ej_messageThis table contains the messages listed under tickets.
ejuserThis table contains entries for the users of the system.
form_submissionA form submission
hotlistThe table is used by the hotlist to store the relationship between tickets and users
mail_in_filterThis table contains entries for the mailboxes the eJournal system is fetching mail from (POP3 or IMAP).
notifyThis table contains the pop-up messages displayed for users for various events, such as 'new ticket', etc.
outboxOutgoing emails with sending status and other info
personPersons
projectProjects
s_shipment_addrAddresses that are ready to be sent in a shipment.
saleSales For every Sale record edited through the SuperOffice GUI, a copy of the current version of the record will be saved in the SaleHist table. This also applies to editing done through the SaleModel COM interface, but not to editing done through the OLE DB Provider or other channels.
TagsMDO List of tags for Service entities
ticketThis table contains the tickets (requests) of the system. Its purpose should be evident.
ticket_customersThis table allows several customers to be connected to several tickets (many-to-many)
ticket_logThis table contains log entries for the tickets.
ticket_log_actionThis table contains actions for the tickets.
ticket_log_changeThis table contains log entries for the tickets.
ticket_priorityThis table contains the ticket priorities.
ticket_statusThis table user defined ticket status values.
ticket_status_historyThis table contains the history of a tickets statuses. Each time a ticket changes status a copy of the previous status of the record will be saved
ticket_typeA ticket (request) type
workflowSuperOffice specific info about a workflow

Replication Flags

  • None

Security Flags

  • Sentry controls access to items in this table using user’s Role and data rights matrix.