List of Indexed Attributes¶
Below is a comprehensive list of all object attributes indexed by Elasticsearch. In other words, if you wish to find a ticket, article, or user via the Zammad search box, Elasticsearch can match on any (or all) of the fields below.
Table of content
Note
These fields may vary if you created custom fields (objects) in the admin interface.
Hint
Below you can find some hints:
(SLA): Attributes marked as SLA attribute are only set if the ticket is affected by SLA calculation. Please note that some attributes may not be set if specific conditions are not met.
Also note that some attributes may be reset to
null
if no longer applicable.note
attribute: Note attributes usually are empty if not specified via console or API.Timestamps: All timestamps provided by Zammad are UTC by default. This also applies to times provided by Elasticsearch
Ticket¶
Tip
The following index contains below mentioned information:
*_ticket
Field |
Sample Value |
Description |
---|---|---|
article |
#{Article Array} |
Array with all articles belonging to the ticket
Please see Article for more details
|
article_count |
|
Number of articles within the ticket |
checklist |
Contains these attributes:
|
Items array contains the text of the items |
close_at |
|
First close time, set once |
close_diff_in_min |
|
Depends on |
close_escalation_at |
|
Time stamp when the ticket would escalate in case solution time is violated. (SLA) |
close_in_min |
|
Value in minutes for how long the ticket was open based on business hours. (SLA) |
create_article_sender |
Contains these attributes:
|
Sender of the article (System, Agent, Customer) |
create_article_sender_id |
|
ID of the user that created the article |
create_article_type |
Contains these attributes:
|
Information of first article type and nature |
create_article_type_id |
|
Type ID of first article |
created_at |
|
Time stamp of ticket creation |
created_by |
#{user object} |
Complete Payload of user that created the ticket
Please see User for more
|
created_by_id |
|
User ID that created the ticket |
customer |
#{user object} |
Complete payload of the customer that created the ticket
Please see User for more
|
customer_id |
|
Customers User ID |
escalation_at |
|
Time stamp of the next applicable escalation. One of the following attributes:
(SLA) |
first_response_at |
|
Time stamp of the first communication type reaction to the customer (SLA) |
first_response_diff_in_min |
|
Depends on |
first_response_in_min |
|
Value in minutes for how long the first response took based on the business hours. (SLA) |
group |
#{group object} |
Complete payload of the current tickets group
Please see Group for more
|
group_id |
|
ID of the current group |
id |
|
ID of the Ticket |
last_close_at |
|
Last close time, set on each closing of ticket |
last_contact_agent_at |
|
Time stamp of last communication type contact of any agent |
last_contact_at |
|
Time stamp of last communication type contact
Depends on
last_contact_agent_at , last_contact_customer_at
and “Ticket Last Contact Behavior” setting |
last_contact_customer_at |
|
Time stamp of last communication type contact of customer |
mention_user_ids |
|
Array with mentioned or subscribed users IDs |
note |
|
Note of ticket, only set via console or API |
number |
|
Ticket number |
organization |
|
Complete Payload of user that owns the ticket
Please see Organization for more
|
organization_id |
|
ID of the customers organization |
owner |
|
Complete Payload of user that owns the ticket
Please see User for more
|
owner_id |
|
User ID of the ticket owner |
pending_time |
|
Depends on pending states, time stamp for pending time |
preferences |
|
May not be available in your system, contains information for internal system functions |
priority |
#{priority object} |
Complete Payload of priority of ticket
Please see Ticket Priority for more
|
priority_id |
|
Priority ID of the ticket |
state |
#{state object} |
Complete Payload of current ticket state
Please see Ticket State for more
|
state_id |
|
ID of current ticket state |
tags |
|
Array with all attached tags |
time_unit |
|
Accounted time units for ticket (total) |
title |
|
Title / Subject of Ticket |
type |
|
Ticket type (deprecated) |
update_diff_in_min |
|
Depends on |
update_escalation_at |
|
Time stamp when the ticket would escalate in case update time is violated. (SLA) |
update_in_min |
|
Value in minutes for how long the last ticket update took based on the business hours and update time. (SLA) |
updated_at |
|
Last ticket update |
updated_by |
#{user object} |
Complete Payload of the user that updated the ticket
Please see User for more
|
updated_by_id |
|
User ID that updated the ticket |
Ticket Priority¶
Tip
The following index contains below mentioned information:
*_ticket_priority
Field |
Sample Value |
Description |
---|---|---|
active |
|
Defines if the priority is active (available) |
created_at |
|
Creation date of priority |
created_by_id |
|
User that created priority |
default_create |
|
Defines if priority is default priority upon ticket creation |
id |
|
ID of priority |
name |
|
Priority name |
note |
|
Note for priority that has been set via console or API |
ui_color |
|
CSS class for tickets of priority |
ui_icon |
|
CSS class for ticket icons of priority |
updated_at |
|
Date of last change |
updated_by_id |
|
User ID of user last updating the priority |
Ticket State¶
Tip
The following index contains below mentioned information:
*_ticket_state
Field |
Sample Value |
Description |
---|---|---|
active |
|
Defines if state is active (available) |
created_at |
|
Creation date |
created_by_id |
|
User ID that created state |
default_create |
|
Defines if the state is the default state upon ticket creation |
default_follow_up |
|
Defines if the state is the default follow up state on ticket follow ups |
id |
|
State ID |
ignore_escalation |
|
Defines if SLA calculation is generally ignored for this state |
name |
|
State name |
next_state |
|
Contains all follow up state information if applicable, may not be available depending on the state type |
next_state_id |
|
State ID of follow up state |
note |
|
Note that has been set via console or API |
state_type |
Contains these attributes:
|
Contains all available information of the states type |
state_type_id |
|
ID of the state type |
updated_at |
|
Last update of state |
updated_by_id |
|
User ID that updated state last |
Article¶
Tip
The following index contains below mentioned information:
*_ticket
Note
Articles are part of the ticket index. To reduce complexity we decided to provide it in its own table. 🙏
Field |
Sample Value |
Description |
---|---|---|
body |
|
Article body in plain text |
cc |
|
EMail-Addresses set as CC (String) |
content_type |
|
Content type of article |
created_at |
|
Time stamp of article creation |
created_by_id |
|
User ID that created the article |
from |
|
From field of article creator |
id |
|
Internal article ID |
in_reply_to |
|
In-Reply-To Header from emails if applicable |
internal |
|
Defines if article is internal |
message_id |
|
Message ID of Email if applicable |
origin_by_id |
|
User ID or original creator if created on behalf another user |
preferences |
|
Internal preferences, may be empty, mainly for delivery states |
reply_to |
|
Contains reply to header if applicable |
sender_id |
|
ID of sender type (Customer, System, Agent) |
subject |
|
Article subject |
ticket_id |
|
Ticket ID the article belongs to |
to |
|
EMail address from TO-Header |
type_id |
|
ID of articles Type (phone, email, web, …) |
updated_at |
|
Last update |
updated_by_id |
|
User that updated article |
User¶
Tip
The following index contains below mentioned information:
*_user
Field |
Sample Value |
Description |
---|---|---|
active |
|
Defines if user is active |
address |
|
Address string |
city |
|
City string |
country |
|
Country string |
created_at |
|
Creation date of user |
created_by_id |
|
User ID that created the user |
department |
|
Department string |
|
EMail Address of user, if applicable |
|
fax |
|
Fax number |
firstname |
|
Users first name |
id |
|
Internal User ID |
last_login |
|
Updated upon every user login |
lastname |
|
Users last name |
login |
|
Login name, always set and unique, can differ from |
mobile |
|
Mobile phone number |
note |
|
Note being available via web, console and API |
organization |
#{organization object} |
Complete Payload of the organization the user is member of
Please see Organization for more
|
organization_id |
|
ID of organization the user is member of |
out_of_office |
|
Defines if user has activated out of office function |
out_of_office_end_at |
|
Ending date out of office |
out_of_office_replacement_id |
|
User ID that replaces this user during out of office period |
out_of_office_start_at |
|
Begin date out of office |
permissions |
|
Array with all permissions of the user |
phone |
|
Phone number of user |
preferences |
|
Depends on user and situation, may contain |
role_ids |
|
Contains array with role IDs assigned to the user |
street |
|
Street |
updated_at |
|
Time stamp of last update |
updated_by_id |
|
User ID that updated this entry |
verified |
|
Defines if the user has verified the account |
vip |
|
Defines if user has VIP state |
web |
|
Web URL of User |
zip |
|
ZIP code |
Organization¶
Tip
The following index contains below mentioned information:
*_organization
Field |
Sample Value |
Description |
---|---|---|
active |
|
Defines if organization is active |
created_at |
2021-03-22T12:47:54.807Z |
Creation date |
created_by |
#{user object} |
Complete Payload of the user that created the organization
Please see User for more
|
created_by_id |
|
User ID that created the organization |
domain |
|
Organizations domain |
domain_assignment |
|
Domain assignment depends on |
id |
|
Organization ID |
members |
#{array of user objects} |
Array with complete Payload of the users being member of the
organization
Please see User for more
|
name |
|
Organization name |
note |
|
Note being available via web, console and API |
shared |
|
Defines if the organization is a sharing one |
updated_at |
|
Last update time |
updated_by |
#{user object} |
Complete Payload of the user that updated the organization
Please see User for more
|
updated_by_id |
|
User ID that updated the organization |
vip |
|
Defines if the organization has VIP state |
Group¶
Tip
The following index contains below mentioned information:
*_group
Field |
Sample Value |
Description |
---|---|---|
active |
|
Defines if group is active (available) |
assignment_timeout |
|
Time in minutes an agent can be inactive until the owner ship is removed |
created_at |
|
Time stamp of group creation |
created_by_id |
|
User ID that created the group |
email_address |
Contains these attributes:
|
Contains all available information of the groups email address |
email_address_id |
|
ID of email address |
follow_up_assignment |
|
Defines if owners are still assigned after follow ups |
follow_up_possible |
|
Defines if following up on a closed ticket is possible |
id |
|
Group ID |
name |
|
Group name |
note |
|
Notes for the group available via web, console and API |
signature |
Contains these attributes:
|
Contains all available information of the groups signature |
signature_id |
|
Signature ID |
updated_at |
|
Time stamp of last group update |
updated_by_id |
|
User ID that updated group |
CTI Log¶
Tip
The following index contains below mentioned information:
*_cti_log
Field |
Sample Value |
Description |
---|---|---|
call_id |
|
Unique Call ID |
comment |
|
Optional comment |
created_at |
|
Creation date of Call |
direction |
|
Call direction |
done |
|
Defines if call displays as “to do” within UI |
duration_talking_time |
|
Call duration in seconds |
duration_waiting_time |
|
Duration in seconds the caller was waiting for answer |
end_at |
|
Time stamp of call end |
from |
|
Calling number |
from_comment |
|
Display name of calling number if applicable |
from_pretty |
|
Pretty version of |
id |
|
Internal ID of entry |
initialized_at |
2021-03-25T08:47:56.753Z |
Time stamp of call initialization, usually matches |
preferences |
|
Contains internal information if required |
queue |
|
Queue the call was answered in |
start_at |
|
Time stamp the call was answered |
state |
|
Last state of call |
to |
|
Dialed number |
to_comment |
|
Display name of called number if applicable |
to_pretty |
|
Pretty version of |
updated_at |
|
Last update of entry |
Chat Session¶
Tip
The following index contains below mentioned information:
*_chat_session
Field |
Sample Value |
Description |
---|---|---|
chat |
Contains these attributes:
|
Contains various preferences of the chat topic in charge |
chat_id |
|
ID of Chat topic |
created_at |
|
Time stamp of chat creation |
created_by_id |
|
User that created the chat, place holder, currently always |
id |
|
ID of Chat Session |
messages |
|
Array with all messages of chat |
name |
|
Name agent set for chat user, if applicable |
preferences |
Contains these attributes:
|
Various internal Meta data of the session_id |
session_id |
|
Unique Session ID |
state |
|
Current state of chat session |
tags |
|
Tags applied to Chat Session by agent, if applicable |
updated_at |
|
Last update |
updated_by_id |
|
User ID that last updated session, may be |
user |
#{user object} |
Complete Payload of the chat agent
Please see User for more
|
user_id |
|
User ID of chat agent |