Linux websever 5.15.0-153-generic #163-Ubuntu SMP Thu Aug 7 16:37:18 UTC 2025 x86_64
Apache/2.4.52 (Ubuntu)
: 192.168.3.70 | : 192.168.1.99
Cant Read [ /etc/named.conf ]
8.1.2-1ubuntu2.23
urlab
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
var /
www /
html /
IT-Ticket /
[ HOME SHELL ]
Name
Size
Permission
Action
osTicket-v1.18.2
[ DIR ]
drwxr-xr-x
auth-ldap.phar
268.47
KB
-rwxr-xr-x
auth-password-policy.phar
9.02
KB
-rwxr-xr-x
en_GB.phar
400.96
KB
-rwxr-xr-x
hi.phar
212.79
KB
-rwxr-xr-x
Delete
Unzip
Zip
${this.title}
Close
Code Editor : hi.phar
<?php __HALT_COMPILER(); ?> 9 f config.yamlY Y Е�]� department.yaml� � �D�� email_template_group.yaml� � � �� event.yaml� � �%҅� file.yamlH6 H6 ;ݿ� filter.yamlV V ��h� form.yaml, , �2д group.yaml� � {b7G� help_topic.yaml� � �_ � list.yaml� � A'� organization.yaml@ @ zL� priority.yaml� � k��� queue_column.yamlI I �-�� queue_sort.yamlr r ��2ɴ queue.yamlG2 G2 �\ɡ� role.yaml_ _ 3��� schedule.yamli i ��� sequence.yaml ���� sla.yaml� � 1�|ش team.yaml� � *)]�� ticket_status.yaml| | H�~�� # help/tips/dashboard.audit_logs.yaml �"� " help/tips/dashboard.dashboard.yaml }�� # help/tips/dashboard.my_profile.yaml Hд ( help/tips/dashboard.staff_directory.yaml� � g���� $ help/tips/dashboard.system_logs.yaml� � "�U�� help/tips/emails.banlist.yaml" " �f#� help/tips/emails.diagnostic.yaml� � �_%'� help/tips/emails.email.yaml ��@�� help/tips/emails.template.yamlq q ���� help/tips/forms.yaml� � ���� help/tips/install.yaml 4�� , help/tips/knowledgebase.canned_response.yaml^ ^ P>�� % help/tips/knowledgebase.category.yaml� � �w� help/tips/knowledgebase.faq.yamlE E ��{� help/tips/manage.api_keys.yaml � �� ! help/tips/manage.custom_list.yaml� � u��'� help/tips/manage.filter.yaml� � \mWU� help/tips/manage.helptopic.yaml� � �u� help/tips/manage.pages.yaml� � ���Ҵ help/tips/manage.schedule.yamlD D ��9m� help/tips/manage.sla.yaml j]�(� help/tips/org.yaml� � �1d� help/tips/settings.agents.yamly y 3�-U� help/tips/settings.alerts.yamlo o 5N��� % help/tips/settings.autoresponder.yaml� � �z� � help/tips/settings.email.yaml� � ���ش help/tips/settings.kb.yaml ��2� help/tips/settings.pages.yaml� � �Cjִ help/tips/settings.system.yaml�$ �$ ��Ҵ help/tips/settings.tasks.yaml� � ���� help/tips/settings.ticket.yaml~ ~ ��T� help/tips/settings.users.yaml] ] �|��� help/tips/staff.agent.yamlG G w��� help/tips/staff.agents.yaml� � :�dL� help/tips/staff.department.yaml� � �2 j� help/tips/staff.departments.yaml� � ��ִ help/tips/staff.groups.yaml 좁´ " help/tips/staff.staff_members.yaml� � 5ޞ� help/tips/staff.team.yamlr r CJ� help/tips/staff.yaml' ' �.�� help/tips/tasks.queue.yaml� � ���w� help/tips/tickets.queue.yamlc c �l�� templates/premade.yaml� � d3Jδ # templates/email/assigned.alert.yaml� � ���� " templates/email/message.alert.yaml� � �존 % templates/email/message.autoresp.yaml� � ��k�� templates/email/note.alert.yaml� � e�o� ( templates/email/task.activity.alert.yaml^ ^ ;�GW� ) templates/email/task.activity.notice.yaml� � m:1� templates/email/task.alert.yaml� � �!��� * templates/email/task.assignment.alert.yaml� � ň͓� ' templates/email/task.overdue.alert.yaml� � �À� ( templates/email/task.transfer.alert.yaml� � ��� + templates/email/ticket.activity.notice.yaml� � e� �� ! templates/email/ticket.alert.yaml� � �� % templates/email/ticket.autoreply.yaml� � �f�� $ templates/email/ticket.autoresp.yaml� � G�� " templates/email/ticket.notice.yaml� � �클 # templates/email/ticket.overdue.yamlF F ��g� % templates/email/ticket.overlimit.yamlk k O�/�� ! templates/email/ticket.reply.yaml� � V-�� # templates/email/transfer.alert.yaml6 6 Ԛ踴 templates/page/access-link.yaml T�1�� ! templates/page/banner-client.yaml� � ��W� templates/page/banner-staff.yamlz z )I߂� " templates/page/email2fa-staff.yaml� � ��լ� templates/page/landing.yamlA A ��#,� templates/page/offline.yamlK K ���� " templates/page/pwreset-client.yaml� � ?���� ! templates/page/pwreset-staff.yaml6 6 a�TU� ' templates/page/registration-client.yamlV V /^*� ( templates/page/registration-confirm.yaml ���A� & templates/page/registration-staff.yaml� � �Q�� ' templates/page/registration-thanks.yamlD D �8[�� templates/page/thank-you.yaml& & O�vִ templates/ticket/installed.yaml� � υ�� templates/ticket/upgraded.yaml0 0 ��^j� js/jquery.ui.datepicker.jsR R �!�ɴ LC_MESSAGES/messages.mo.php� � a��x� js/osticket-strings.js� � �$�R� MANIFEST.php �sD� #Default configuration. The format is key: value and the data will be #inserted into the %config table at install time --- core: time_format: 'H:mm' date_format: 'dd/MM/yyyy' datetime_format: 'dd/MM/yyyy H:mm' daydatetime_format: 'EEEE, MMMM dd yyyy H:mm' default_priority_id: 2 enable_daylight_saving: 0 reply_separator: '- इस रेखा से ऊपर जवाब दें -' #Do not translate below here isonline: 1 staff_ip_binding: 0 staff_max_logins: 4 staff_login_timeout: 2 staff_session_timeout: 30 passwd_reset_period: 0 client_max_logins: 4 client_login_timeout: 2 client_session_timeout: 30 max_page_size: 25 max_open_tickets: 0 autolock_minutes: 3 default_smtp_id: 0 use_email_priority: 0 enable_kb: 0 enable_premade: 1 enable_captcha: 0 enable_auto_cron: 0 enable_mail_polling: 0 send_sys_errors: 1 send_sql_errors: 1 send_login_errors: 1 save_email_headers: 1 strip_quoted_reply: 1 ticket_autoresponder: 0 message_autoresponder: 0 ticket_notice_active: 1 ticket_alert_active: 1 ticket_alert_admin: 1 ticket_alert_dept_manager: 1 ticket_alert_dept_members: 0 message_alert_active: 1 message_alert_laststaff: 1 message_alert_assigned: 1 message_alert_dept_manager: 0 note_alert_active: 0 note_alert_laststaff: 1 note_alert_assigned: 1 note_alert_dept_manager: 0 transfer_alert_active: 0 transfer_alert_assigned: 0 transfer_alert_dept_manager: 1 transfer_alert_dept_members: 0 overdue_alert_active: 1 overdue_alert_assigned: 1 overdue_alert_dept_manager: 1 overdue_alert_dept_members: 0 assigned_alert_active: 1 assigned_alert_staff: 1 assigned_alert_team_lead: 0 assigned_alert_team_members: 0 auto_claim_tickets: 1 auto_refer_closed: 1 collaborator_ticket_visibility: 1 require_topic_to_close: 0 show_related_tickets: 1 show_assigned_tickets: 1 show_answered_tickets: 0 hide_staff_name: 0 disable_agent_collabs: 0 overlimit_notice_active: 0 email_attachments: 1 ticket_number_format: '######' ticket_sequence_id: 0 queue_bucket_counts: 0 allow_external_images: 0 task_number_format: '#' task_sequence_id: 2 log_level: 2 log_graceperiod: 12 client_registration: 'public' default_ticket_queue: 1 embedded_domain_whitelist: 'youtube.com, dailymotion.com, vimeo.com, player.vimeo.com, web.microsoftstream.com' - #Departments defined initially for the system #Fields: #id - (int:optional) id number in the database #flags - (bitmask: 0x0004 Active 0x0008 Archived) #name - (string) Short name of the department #signature - (string) Descriptive name of the 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 name: समर्थन signature: | सहायता विभाग ispublic: 1 flags: 0x0004 group_membership: 1 - id: 2 name: बिक्री signature: | बिक्री और ग्राहक संबंध ispublic: 1 flags: 0x0004 sla_id: 1 group_membership: 1 - id: 3 name: अनुरक्षण signature: | अनुरक्षण विभाग ispublic: 0 flags: 0x0004 group_membership: 0 - #Default email template group for the system #NOTE: The language field is defined for the email tempate group model, but #is not considered by the installer. Whatever language the install #loads data for, the same language will be used to load the email #templates #Fields: #isactive - (bool:0|1) true or false if the templates should be initially #usable #name - (string) descriptive name for the template group #notes - Administrative notes (viewable internally only) --- id: 1 isactive: 1 name: osTicket डिफ़ॉल्ट टेम्पलेट (एचटीएमएल) notes: | डिफ़ॉल्ट osTicket टेम्पलेट्स - #event.yaml #Events initially inserted into the system. --- id: 1 name: created description: - id: 2 name: closed description: - id: 3 name: reopened description: - id: 4 name: assigned description: - id: 5 name: released description: - id: 6 name: transferred description: - id: 7 name: referred description: - id: 8 name: overdue description: - id: 9 name: edited description: - id: 10 name: viewed description: - id: 11 name: error description: - id: 12 name: collab description: - id: 13 name: resent description: - id: 14 name: deleted description: - id: 15 name: merged description: - id: 16 name: unlinked description: - id: 17 name: linked description: - id: 18 name: login description: - id: 19 name: logout description: - id: 20 name: message description: - id: 21 name: note description: - #files.yaml #Files initially inserted into the system. Canned responses have their own #method for attachments; however, this file will make it easier to add #things like inline images. #NOTE: If the files aren't attached to something by the installer, they #bill be cleaned up shortly after installation (by the autocron). --- key: b56944cb4722cc5cda9d1e23a3ea7fbc name: powered-by-osticket.png type: image/png encoding: base64 data: | iVBORw0KGgoAAAANSUhEUgAAANoAAAAoCAYAAACYR+TJAAAKQ2lDQ1BJQ0MgcHJvZmlsZQAAeNqd U3dYk/cWPt/3ZQ9WQtjwsZdsgQAiI6wIyBBZohCSAGGEEBJAxYWIClYUFRGcSFXEgtUKSJ2I4qAo uGdBiohai1VcOO4f3Ke1fXrv7e371/u855zn/M55zw+AERImkeaiagA5UoU8Otgfj09IxMm9gAIV SOAEIBDmy8JnBcUAAPADeXh+dLA//AGvbwACAHDVLiQSx+H/g7pQJlcAIJEA4CIS5wsBkFIAyC5U yBQAyBgAsFOzZAoAlAAAbHl8QiIAqg0A7PRJPgUA2KmT3BcA2KIcqQgAjQEAmShHJAJAuwBgVYFS LALAwgCgrEAiLgTArgGAWbYyRwKAvQUAdo5YkA9AYACAmUIszAAgOAIAQx4TzQMgTAOgMNK/4Klf cIW4SAEAwMuVzZdL0jMUuJXQGnfy8ODiIeLCbLFCYRcpEGYJ5CKcl5sjE0jnA0zODAAAGvnRwf44 P5Dn5uTh5mbnbO/0xaL+a/BvIj4h8d/+vIwCBAAQTs/v2l/l5dYDcMcBsHW/a6lbANpWAGjf+V0z 2wmgWgrQevmLeTj8QB6eoVDIPB0cCgsL7SViob0w44s+/zPhb+CLfvb8QB7+23rwAHGaQJmtwKOD /XFhbnauUo7nywRCMW735yP+x4V//Y4p0eI0sVwsFYrxWIm4UCJNx3m5UpFEIcmV4hLpfzLxH5b9 CZN3DQCshk/ATrYHtctswH7uAQKLDljSdgBAfvMtjBoLkQAQZzQyefcAAJO/+Y9AKwEAzZek4wAA vOgYXKiUF0zGCAAARKCBKrBBBwzBFKzADpzBHbzAFwJhBkRADCTAPBBCBuSAHAqhGJZBGVTAOtgE tbADGqARmuEQtMExOA3n4BJcgetwFwZgGJ7CGLyGCQRByAgTYSE6iBFijtgizggXmY4EImFINJKA pCDpiBRRIsXIcqQCqUJqkV1II/ItchQ5jVxA+pDbyCAyivyKvEcxlIGyUQPUAnVAuagfGorGoHPR dDQPXYCWomvRGrQePYC2oqfRS+h1dAB9io5jgNExDmaM2WFcjIdFYIlYGibHFmPlWDVWjzVjHVg3 dhUbwJ5h7wgkAouAE+wIXoQQwmyCkJBHWExYQ6gl7CO0EroIVwmDhDHCJyKTqE+0JXoS+cR4Yjqx kFhGrCbuIR4hniVeJw4TX5NIJA7JkuROCiElkDJJC0lrSNtILaRTpD7SEGmcTCbrkG3J3uQIsoCs IJeRt5APkE+S+8nD5LcUOsWI4kwJoiRSpJQSSjVlP+UEpZ8yQpmgqlHNqZ7UCKqIOp9aSW2gdlAv U4epEzR1miXNmxZDy6Qto9XQmmlnafdoL+l0ugndgx5Fl9CX0mvoB+nn6YP0dwwNhg2Dx0hiKBlr GXsZpxi3GS+ZTKYF05eZyFQw1zIbmWeYD5hvVVgq9ip8FZHKEpU6lVaVfpXnqlRVc1U/1XmqC1Sr VQ+rXlZ9pkZVs1DjqQnUFqvVqR1Vu6k2rs5Sd1KPUM9RX6O+X/2C+mMNsoaFRqCGSKNUY7fGGY0h FsYyZfFYQtZyVgPrLGuYTWJbsvnsTHYF+xt2L3tMU0NzqmasZpFmneZxzQEOxrHg8DnZnErOIc4N znstAy0/LbHWaq1mrX6tN9p62r7aYu1y7Rbt69rvdXCdQJ0snfU6bTr3dQm6NrpRuoW623XP6j7T Y+t56Qn1yvUO6d3RR/Vt9KP1F+rv1u/RHzcwNAg2kBlsMThj8MyQY+hrmGm40fCE4agRy2i6kcRo o9FJoye4Ju6HZ+M1eBc+ZqxvHGKsNN5l3Gs8YWJpMtukxKTF5L4pzZRrmma60bTTdMzMyCzcrNis yeyOOdWca55hvtm82/yNhaVFnMVKizaLx5balnzLBZZNlvesmFY+VnlW9VbXrEnWXOss623WV2xQ G1ebDJs6m8u2qK2brcR2m23fFOIUjynSKfVTbtox7PzsCuya7AbtOfZh9iX2bfbPHcwcEh3WO3Q7 fHJ0dcx2bHC866ThNMOpxKnD6VdnG2ehc53zNRemS5DLEpd2lxdTbaeKp26fesuV5RruutK10/Wj m7ub3K3ZbdTdzD3Ffav7TS6bG8ldwz3vQfTw91jicczjnaebp8LzkOcvXnZeWV77vR5Ps5wmntYw bcjbxFvgvct7YDo+PWX6zukDPsY+Ap96n4e+pr4i3z2+I37Wfpl+B/ye+zv6y/2P+L/hefIW8U4F YAHBAeUBvYEagbMDawMfBJkEpQc1BY0FuwYvDD4VQgwJDVkfcpNvwBfyG/ljM9xnLJrRFcoInRVa G/owzCZMHtYRjobPCN8Qfm+m+UzpzLYIiOBHbIi4H2kZmRf5fRQpKjKqLupRtFN0cXT3LNas5Fn7 Z72O8Y+pjLk722q2cnZnrGpsUmxj7Ju4gLiquIF4h/hF8ZcSdBMkCe2J5MTYxD2J43MC52yaM5zk mlSWdGOu5dyiuRfm6c7Lnnc8WTVZkHw4hZgSl7I/5YMgQlAvGE/lp25NHRPyhJuFT0W+oo2iUbG3 uEo8kuadVpX2ON07fUP6aIZPRnXGMwlPUit5kRmSuSPzTVZE1t6sz9lx2S05lJyUnKNSDWmWtCvX MLcot09mKyuTDeR55m3KG5OHyvfkI/lz89sVbIVM0aO0Uq5QDhZML6greFsYW3i4SL1IWtQz32b+ 6vkjC4IWfL2QsFC4sLPYuHhZ8eAiv0W7FiOLUxd3LjFdUrpkeGnw0n3LaMuylv1Q4lhSVfJqedzy jlKD0qWlQyuCVzSVqZTJy26u9Fq5YxVhlWRV72qX1VtWfyoXlV+scKyorviwRrjm4ldOX9V89Xlt 2treSrfK7etI66Trbqz3Wb+vSr1qQdXQhvANrRvxjeUbX21K3nShemr1js20zcrNAzVhNe1bzLas 2/KhNqP2ep1/XctW/a2rt77ZJtrWv913e/MOgx0VO97vlOy8tSt4V2u9RX31btLugt2PGmIbur/m ft24R3dPxZ6Pe6V7B/ZF7+tqdG9s3K+/v7IJbVI2jR5IOnDlm4Bv2pvtmne1cFoqDsJB5cEn36Z8 e+NQ6KHOw9zDzd+Zf7f1COtIeSvSOr91rC2jbaA9ob3v6IyjnR1eHUe+t/9+7zHjY3XHNY9XnqCd KD3x+eSCk+OnZKeenU4/PdSZ3Hn3TPyZa11RXb1nQ8+ePxd07ky3X/fJ897nj13wvHD0Ivdi2yW3 S609rj1HfnD94UivW2/rZffL7Vc8rnT0Tes70e/Tf/pqwNVz1/jXLl2feb3vxuwbt24m3Ry4Jbr1 +Hb27Rd3Cu5M3F16j3iv/L7a/eoH+g/qf7T+sWXAbeD4YMBgz8NZD+8OCYee/pT/04fh0kfMR9Uj RiONj50fHxsNGr3yZM6T4aeypxPPyn5W/3nrc6vn3/3i+0vPWPzY8Av5i8+/rnmp83Lvq6mvOscj xx+8znk98ab8rc7bfe+477rfx70fmSj8QP5Q89H6Y8en0E/3Pud8/vwv94Tz+4A5JREAAAAZdEVY dFNvZnR3YXJlAEFkb2JlIEltYWdlUmVhZHlxyWU8AAADKGlUWHRYTUw6Y29tLmFkb2JlLnhtcAAA AAAAPD94cGFja2V0IGJlZ2luPSLvu78iIGlkPSJXNU0wTXBDZWhpSHpyZVN6TlRjemtjOWQiPz4g PHg6eG1wbWV0YSB4bWxuczp4PSJhZG9iZTpuczptZXRhLyIgeDp4bXB0az0iQWRvYmUgWE1QIENv cmUgNS42LWMwMTQgNzkuMTU2Nzk3LCAyMDE0LzA4LzIwLTA5OjUzOjAyICAgICAgICAiPiA8cmRm OlJERiB4bWxuczpyZGY9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkvMDIvMjItcmRmLXN5bnRheC1u cyMiPiA8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0iIiB4bWxuczp4bXA9Imh0dHA6Ly9ucy5h ZG9iZS5jb20veGFwLzEuMC8iIHhtbG5zOnhtcE1NPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8x LjAvbW0vIiB4bWxuczpzdFJlZj0iaHR0cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL3NUeXBlL1Jl c291cmNlUmVmIyIgeG1wOkNyZWF0b3JUb29sPSJBZG9iZSBQaG90b3Nob3AgQ0MgMjAxNCAoTWFj aW50b3NoKSIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDo2RTJDOTVERUE2NzMxMUU0QkRDRERG OTFGQUY5NERBNSIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDo2RTJDOTVERkE2NzMxMUU0QkRD RERGOTFGQUY5NERBNSI+IDx4bXBNTTpEZXJpdmVkRnJvbSBzdFJlZjppbnN0YW5jZUlEPSJ4bXAu aWlkOkNGQTc0RTRGQTY3MTExRTRCRENEREY5MUZBRjk0REE1IiBzdFJlZjpkb2N1bWVudElEPSJ4 bXAuZGlkOkNGQTc0RTUwQTY3MTExRTRCRENEREY5MUZBRjk0REE1Ii8+IDwvcmRmOkRlc2NyaXB0 aW9uPiA8L3JkZjpSREY+IDwveDp4bXBtZXRhPiA8P3hwYWNrZXQgZW5kPSJyIj8+i/72ygAAFwtJ REFUeNrsXQmcU9XVPy97MslkZoBhcRiQXTY30M+tKCqoLQr287O2LvUr1taFuiButUoVwa32U4tS tNU6VkRUpCwFZdEyqGyCoKyC7IsCM8zCTJKX992b/G9z5k6SyQxQccz5/Q4kk5f37rv3/M/5n3Pv uzGGDx9OWTk2pNp00tju71Oxfy9RxP1da35LoZOF7hd6m9DtjT6DJTTfpNI1Hrr6rTyy2SyyGc1j bG1Z887KEZILhJ4n9MdCr2j0t6NC80xauN5NP5sSpLAAXXMBmRRH1j6+1+ISWig0V6hdaA0i0r4m RjQFmV2N/rY/SktEJBv6Rj5ZAmQtfVGKWlmgZeW7Ka2Enip0gNDThLYX6gXgJLuJCA0JPSh0ldDp QmcJPZDBue34X4K0otGUUQBtxlYX7SuzU492YYpEm1fHZ4H2/ZCOQq8U+r9Cu2X4nd5CrxK6TOhI oQvSHJsjdBgD87tCxwn9bUZXkhAVADt0yCBfjtnsQJbN0Zq/eITeLnQhDL9bE84hI+BcoffjfMnk V4iSHDr3A9gNR7OgSbO3OemJ0hwqyo02y4HIAq35SmuhU4X+QehxR8BOHgGNvAA5naSbRULvTRO5 fi00P+2ZnRbVfuOgSYt91Ca3eeVlWerY/OUEoW8K7XWEz3sucru9QmsBuNZpHHY/ipf6H0xHG7cd tNGUtR5qF8gCLSvfHZFR5pWjADIlPuR8mcrvKF7NHJuS3wrqWOiPxnKz5lTSz1LH5i2SKvb/lq4t 49FSocuFVrG/y0JJyzpHylTMI/7JNWn+Gg9FIgYZRvMdlGxEO+ZcX+Rwvv1zaspk8ZGT9UJ/InSH 0A5Cfyn0MuR338Tvz4q792CU5q300KSVXpq20U1uQSGN5jysWcs+hryeEaWS7aeQGfYKq2t09U3m Sncl+bucPC7/D93Cw0K/BFVcR/FCST8R56aTXQDMb8bQ9OVeB/30pQK6ZUaQJi73kddhkcdhNe+x zZr3sSPSo28+FKSQPUxeq9H+XUaOntrfSoVOBACDR7n544W+Voca+qIhcSMhGcUOltvpwDYXPVjq pzmbXFQVMsjvsqh7qwiZAmPR5o2zLNCOKXphCGuzbLT6QDH1z98Se52hBIReo/1NRpShFF9i1eYo N/05oaMSrRGRKydKq9Z7aPGXbuqQH6EFW1z0aGkOtfNHYzQxJycesU3r+zG2jrPPPjtr4ceQTJu/ jN7c3Yv6t9gk3HzGfvAsipfdlZQBeN8gtmwQ2uIoNFcu0xpBatWICMJyneLjc3LJFFedtclNCwXQ DFeUct0ierVonqs+shHtO5mnWZTnqooXRSyPMN6MXL5cMe9i7x8SugSv5SLhJ4S+kcF4y/zqddBM WczIo3g53ym0EvleWwCbUPRYVucMgg5OWOGlzbudVCgiWY+2iXWL31eQZYF2DIrdiFJV2EM1NUHy 2EOZ0EdZNj+Rvf9A6KvaMWuEVlN8gjmdyEnuB1jK6KPEKpByRMoigPZMoYOEzo4BPSpAGDTpqz1O yndaFGoZiRU5viVwyfbKJWHt8X6P0HlCD2WBlpWY+O21tKKiDZXs7EvDO39IVOtv6CuDKb4eUclf EcW4dKHU6xSJGWNJ7FWeyLFCIpRW2qrIVmc+TMp2FFemU+Ixm3zyWLu27nDRsMl5tO2gnVp4o3JS rR3FJ7cjoLAp/QvFV5pIqlsg1I32ygi6sQndKCPyPUIHMor7Q6HbskDLSkwsEUgcJMvdtSjxGxSf B04pMpqpsCcXD7+b5JiuGrXULyrP8CdyWp9LRNz7Vh6dKCjf1WcJjB2yxZsQe4DGUJNdYVnHILlq 34o9QrOdCiI0fm6AVm53Uve2kViORvFV/3JRcxXOkEpk5NwEGnq+9DcUfyLgeaE3ZaljVo6KFLiq 6f293ejk4A7qJZRC/lRgywOFU/JP0DtdTk55sVgZ3no34rYecxy00X3zAvTkh35qL6jfrA1uqg4b tLfSRsN619DICyqIDsRmltuJ5rSMNSnX3EWe6KFFS3z01moPFbc0FcgI+RwBNA1JLvLClpR4ts3b xC6MasA2G4ioR0qOR1/3htOYkQVaejFgHE5441CK4zw4pgZe/sgkGDaTdtQEaFVZEfUK7I1HtuTz anLerC9e70SOpYukYd1TmqPbmkltwrdMnJUbGvteIGadnVrLAoZBMza6Y2sPDwig5XssGjmgUtyx QFe1USWgsFrkZPO31xjjV232hm+elidyS4odx0r2ivZVMMM3Wd6nRH4mFyqvB9jy0f+VhzF+/+mF Jj1QSDoJ78dlgdawyIF+AbmPfNRkNMWfOubSh+LrCtvjmHuO1MWjAlTHuStosizzi4jWOXd3qs16 5PxYAK+/BP3S5QYth0uAzE4vUtvwzc/MzA3dMy1IhYFoK59hFQtweW12K9LKZ8mnpTe38kUj87Y6 6eqSAiq58oAE2xLqWjt4+QbXzoF3Fckqia9Lcag4V+BRgMwFgMi2PATwe1ieJp3So5R4UFRSzztQ xJEg/COcl5uasiXCtyftGchIL7xkgZaiJkHxeakO+D+ZlRegsuVMasiHCzbhkD0isjkcoXQ5Gl+o uzJJHiTb9QDpS+0s2i0i2WgBshee+Wcu3f52sLA437zJYYs9qNmeXU1WKhdELXqyYzA6f/J6N3nf yaNHz68oL3k9v3zSp15budO6tmNh5BZxgT7RulFqi9DHKb5iRJev2Wt5g59KQOP91mOY5aRLlreh oKNsZX8WaA1LhNHFAymo40F4bhn9dh+NRjgNk0q2nUJ3dyolR2xezZbMiyr5RPtMVtz+hqoglylR 03jA5jHXThBU8Tdv5p3RLt98zmWnU6JW7D5ehNHI/OgHQi+RGo7SvccHzXFTRd72xT47Ld7uFDQx +nSv9qERpmlExeeTjThVlH0nH9EZIvRPQs8Qep2WI/GczcXed6L4lgt2ODu5hOwfSbpGPsg6GNS5 EBGzEuOwgOJPEDRE5eWzcpeC1gbhjMZT3W3yLqb4FEYhJaY45IqbSayCeSL6upOGp4vhhGXbKhxI 4E5Fw2ajAnQ1xedLFiPBrkySmwxC4ufFRRfBMxHj2TZQCJWgy/0kihFWNzID9uM7HtzoHlAiGTH6 w5PIuaD54PLEDKEV2rkeg9QFXHkTqNUg5CgWqnL/IqpXsj4TnZWDqt16FvpT8X0bixTqfD9Bn8g2 TqP4igx5zotwDjlIq5IAoq2KHsQ2wjEMizYfyqdQ1B4HWn1pzSIPp42yUjcGxRIlkgbeT97oxI37 7dGLH2tDVSFqL0A2MeCyegnKJ/OJW4R+peV316P6N1YAcV+uK/Z96phvXmUYNCIUNraJjr3CqA/0 c4T+Hbb0IcXXXHLiymueSk4CrVTylyRAk1H3Tqq/rlPJ+aCl6ebMJBt5WihfFvU663vpwOQTB1cB LJSkDbcBL4MQuXW5BBpz1g54hufRsHFo6A/YF+aC56vQLp/efQmeiosc7GcovmJbGtZz8Ew34/xS RqHkK68lH6Eowd9Hwzgi8DQSpHKB6inaNVbCGBaCNkmP2RlG9Q067yAGWFI+ObHaUTtHKdq0Eu/v pvgTwF6W00zIsFLGI4vM0y5jfxsF4C/CoPXANS9k1El6Zjm5LOeb5gh9T2crPns4vgayvnhx7yrq 7sBruYJe31pgNaLKcrl1wNx1Hvq6yqAWvugdIpJJkM1FW3UHVItctQrRcYzI32blui3pDM+14s26 L0k0JTi0ezDGNyJXK2ugH6sBvFSFjEdhX+lkEwJDOrb2qAYy2cbhuN92AN1Z7PO1yC27o997wLb6 MMefTuw2Vv3xwuD7ITH9mnmIFwGaAgBAgUxGmXnoQB869jp45hA6rC8rRZ/DrnUuXgcQZj0wCAmy VxjIViJihRCmS9AZNawzR6DthGh0Hgy4I8ArwfUZPj8L9+DHvT2C9pgwjn0wns4ZdKDJvNcQtHUN /laItso5rCmMZnTRvH47vJ5XnzlYdMh0xoojKQo2RXj9OXKi8+E4uLwf619LgMwfpWcXBOgOkZcV 5kT7ipzsBqyavysJyLi8ChuQ7OFarfT+dZrvLUDfR/DdTMryqaLdTRrIwmAf0vFeTvENgl5GEAil yKsJx93I3s9gICMUuM5iTOVGRNp+lHjWjkA3n4TTHwU6ydv+IWzyMRnAbBqXlSf+OUBwKYtiA+EB BlBiTuZVUK7zcazirPcBBAvx/nSA6DgYnZIilieqDVwmIcKqBbK34yZPR0fXgmLeC24dZmBdC8ow EufoBk49HG0/kRLPa/XC69sZWO9GJD8XFLWxMgYU/GJQChWxBsHYlXC2MJgZ63v1EkVBGW9ov4x8 rupk+Vke67dFLMdxalFlmDDX7VRg0stLfDRiZi4V5ETJZov1h4zab7Ponk7URPh/w4Gq0v09bCx1 2YExuVyjpI2VdhTfVYuLvO5QsJp3wEKuR1/7KTEXpwC7A06fb6mwBIGhlqUQQ9jnEsR/xucm0oH7 2OeXgc08AVBxfv82qq6ynWNtWpiewOZiPsYJlFwEo1WG8QSjAv+CJyAY+Hn4PiHctka+5Ee0LAcF zUfkCLLKTU8WyWYgD8oBdVHn7AvA1eD9bniqqYiKqkjwGXJMFzzcNIo/Zi/lF6BxUqaD6hJKyr8H jcmkEiVlBSKjicgyjh1zIRzWp4whqByvJ/N+y+twDSNKZREP5bkrUj11ncv6bQOjXkq+ghFVknyo sspG729wk0O89gv6KGhfbxZJM5nMXQ5wdUI0+yuucS6i1kMYlwKNtklb2UlNm2dUEW0oi/wERvKH RpxnLyLqWJa3rkH/8F2ZrwAzI7CoKUnONQfjrXLYAazAY9Oofcqq40fa+4VAqQNAURu+fAC6wkUB KIhOkZ7ld5TYzKUVDP51RM5LAJb+aNQq5FmqQ6URLoMx2+BVclg0PJ55osXMkDuyyPlfQr9Ah0Qx cH4WbXjeVsverwPou2cItDVaZfIreNDj4Ei2Aswnw1ANROm+rJ/rgGx3rZ/6BPZQBxnNzGT5eOw+ XWj3FvytQouwm9UPR7y+1EevrfBSt8KIfMjSYP2c6Y9R7IET6gJ28BGi29OgwA9Cv4ZDLEXutohS T/hnKgO19y828vs5oHCqOCEDxK2M5hPslK+gcSJCWgw0NXgdSDLFogctRzqgmUk4MyWpvtUk8YJ8 mYsbYVkZ2xkAFQE8Hty0pFq9GchXs5vYDzAb7Caq0ebPYVRuzeBVudjDotNadJqdEhOmZXAIqhrY 1GkOI0W/mYxGqDbOBv3pDCrbB+1cC+fzbxe+rSZIJwmQPdBjNrltIhDEtjaoVxDpxhzcSlYUUVMP cSrqsqhip5OmLPNRm6CpnmS2sXvONNLwe3KysRwIynUhxrIf6NcQRqFuo6Yt6LWSzBeWN2Gu7Uyt uJGD6jdpQON7UJ5M6ZauJSSQwgYoHdD0J3H7sGO2gAIUwxt3YJ6UYED5DIg1GAgJtAsQZfbAsNTj GpeyyPI5wBVm1aOhmpdWJfUIrq+ik51NKJbDq/pxzmHw+upzB77fF/dRgOiod17LDJN30gocUlow x7KLRc1P4HRuYMWHxeiXuGVZBj3ebS4V+feSJwYyX6r9Q05gxq6KKCGWa8f7TdDEjfsdNHWdm7ol Hrw0KbGPSKZbHPjQLxGqOxkbAfX9EH1cjP44mxUq5Fj8jNQGPU13aA0adArRE1wnItwKxoTsWn4b TTO1E4EtOdk42lI4iaQfDmeGX0B1V05/wOY0urLqk5rPuZs1YjXL81ReUgxjUw8QVgJop2LgPmIA Ixjkj9g1OqEs+3fMY1SnqFBtYZ3XD/mi+rwnpiD+D0UJZTDDWBXUjkJJi0Z4XHkdvpXAVez1Iq04 oXKOH+P1W/yERd5yOiF/CwUdNYhkSUGWx2jtJ1o0V3SwtoG2r2fONBPphrL2duQ8x1H9XYgt9P9c FAcG4thBKBI1FWARbQ4srwnnmozCiZJWqBr6WGSv0Sqm51BijvU8phdCJSv7I2MuViqg6RHtFFCO GZSYLFbVmXkoOowAsEYjInxGdTeGmcGqbCsAKL+WtO/FgPRi8xSfsoLMYHjal1BS/RI31Z0VDyop +S5eVSjoXI7OnIr3OwGGtuiEq1DQmQCDeQMFlx4awBsCmerH8ej8AByIassb7DiZp/0axwTQHx/z k97deQHZZIVR5mWpn64eDFrzCcZFT8C3/dtowgZ1KYjQ0O61tGi7M7YhDptbU1XEJ6jhX4wZiHH8 G6L1xygu/ZRSTw6vQtFiHPK6V5sY0bZo76/Ui0cNyE4Uq9bAKZ7O7ukOfFamFUb8aP/BJkRd7vTq RTQTIGuPEnl/Nmh34vUXoD3f4MQ/RKm9J5uzuZV1/GIt4VRzEPuYR5WylHmteYisB2A4l6IM3x3H PIUKYStWwg1o9zIJ8x8ReJqrMdfRlk1BvIF5lyls3mskuPyzrBwdSJHDeZk3/Bz9dA2ilWrLSPQB LzYt00rAdSY8fSKiUcSVbkB7s2rwSxq1LmARLU6xQgYF2obpmtOraH+1TS9elYKdXN+AERUxdlMC wy9HSlCUIb02DyOivaM5thEZOkNi/bEL9vCA5hgeRMSNUt1fzDmN+IZDDYv+U1VdU0U0O7zyGNBC H6pvryKiKPkH+PdQeCknjOUDzLVwyrIPA9QJ3p3TnHsBiFAS7zQFCf7lMCwXQDoV0UyVjX+BXGoT 1V/w+WcY+TA4gjDuYwaLIiHc6yx4Nzeu8RoKFJ3wnWT7In6BaOCD55Pnuhn53n5QlTlJuP0sRlPn 1DtrbUBGMj8KJfs1enw6+rg1aNBE7dtD2HRHwlRFVJPlfS3+y3F6HOd7CqX7aUnusxBRvzMM/iPm zGR0/i3GIdkcRFdEDNIjdyNlJhywmhrxwFFORPt3gZUMgN2Uau1xsqLUe3CkoxgGHgdrmwinoxYr 3I97GA9nWgvHq3LQpWwMq8Ei/GyObSRs23AkSRI/gDG7YDzJ+Ms6JJPqB+xCaeZilkKTnWNdms7d gGs4cY2wdo1DlGSSV5MV6HhV3g8nuR95nr/AoRisoPBRkukOLgeIPW8EGYWBM7WBVoWYICWW/nxG 9dc9ilbKByutnhgki0UnXjkbT/U3S+0Bz0z1HIPovbJaG4UOGeTIq7NJzjR4+IdhsM/CQZXhPs7E Z53Qj7ezs74AYF8LYxwHOhrBmA1GtChE5J1+GEAz0bczKbG+Uzq43yBfPwjwtYCTXKhNKei07hk4 1n54LwPG78HGRiHVUG7pf3AvB9i95QLYJQxoW3Ddi1hlcyzavsSRogppZZBM0xGYH8lEDveBSktL co/WdZRBmClKwHciAvZktLH+8qV4XrYYzOJXyPsKcA/TEMnmJLnGAET3KKIti10GnV0UotM6hmhr uZ3naYT8ZDP+vxWqj/Er8O472N9Vbv40CkvJtlAoA1DHaP3r1wo7XgYeu8aylCwHXXyeAYRYvsur sQVUdwlWnsbedgAEvBB1C6q/j+C+nmJTKMEU1dmWWj89DGcYYHiS2tGhNcBNWTkakoNcU4FsM6hl OlkJauZCbql2oUo1l3MDBvt60n+dU9DGLifU0iWbamjMnIAAWj1f8Bqi86WY9mgBYG8GZVua4rrL KfEj8TKnaQew7AOdn03JN9eZjmJWGPf1FauETkB08lP9Xxldiuv9CP93ZhVIdc2ZSGWm438LbdDp /9tIawYgWrVE27347icomJ2DirkfTlQeuxXnfF875yK061ZKTI3JlGm+8fLLL/dCaIygkRuzuDji IqnGL+Ehd8L7f5rswOvKRjXl/HZUIStRwa0vQZNGTw/SmNIc6hA0m0OfGnAwakOVCkrMJza4o1Ga ftQLN3ZEMy/YQjWoqtVA21ogcMnjy/5fgAEAs+CvmHNdSv0AAAAASUVORK5CYII= - #Default ticket filters installed for the system #NOTE: The SYSTEM BAN LIST is critically important and should _never_ be #removed from this file. The name 'SYSTEM BAN LIST' is also important #and should not be translated -- it is not displayed on the interface #Fields: #isactive - (bool:0|1) true or false if the filter is initially enabled #execorder - (int) order the filters should be executed in (lowest first) #name - (string) Descriptive name for the filter #notes - (string) Administrative notes (viewable internally only) #rules - (list<FilterRule>) List of rules for the filter #Fields for FilterRule: #isactive - (bool:0|1) true if the rule should be considered #what - (enum<email|>) field to check #how - (enum<equals|contains|dncontain>) how to check for <val> #val - (string) search value #Fields for FilterAction #type - type of filter action --- isactive: 1 execorder: 99 match_all_rules: 0 email_id: 0 target: Email #notrans name: SYSTEM BAN LIST #notrans notes: | ईमेल पर प्रतिबंध लगाने के लिए आंतरिक सूची । दूर नहीं करते rules: - isactive: 1 w: email #notrans h: equal #notrans v: test@example.com #notrans actions: - sort: 1 type: reject #notrans - #Default (dynamic) form configuration. This data is used as the initial, #minimal data for dynamic forms that ships with the system. #Fields: #id: Used only if associated with a help topic #title: Bold section title of the form #instructions: Title deck, detailed instructions on entering form data #notes: Notes for the form, shown under the fields #flags: #0x0001 If the form can be removed from the system #fields: List of fields for the form #type: Field type (short name) (eg. 'text', 'memo', 'phone', ...) #label: Field label shown to the user #name: Name used with the data internally. This is especially #useful for page and email templates, where %{ ticket.<name> } #will be used to retrieve the data from the field. #hint: Help text shown with the field #flags: Bit mask for settings & options ## From class DynamicFormField #const FLAG_MASK_CHANGE = 0x0010; # Type cannot change #const FLAG_MASK_DELETE = 0x0020; # Cannot be deleted #const FLAG_MASK_EDIT = 0x0040; # Data cannot be edited #const FLAG_MASK_DISABLE = 0x0080; # Field cannot be disabled #const FLAG_MASK_REQUIRE = 0x10000; # Requirement cannot be changed #const FLAG_MASK_VIEW = 0x20000; # View settings cannot be changed #const FLAG_MASK_NAME = 0x40000; # Name cannot be changed #configuration: Field-specific configuration #size: (text) width of the field #length: (text) maximum size of the data in the field #cols: (memo) width of the textarea #rows: (memo) height of the textarea --- id: 1 type: U #notrans title: संपर्क जानकारी flags: 0 fields: - type: text #notrans name: email #notrans label: ईमेल पता sort: 1 flags: 489395 configuration: size: 40 length: 64 validator: email #notrans - type: text #notrans name: name #notrans label: Full Name sort: 2 flags: 489395 configuration: size: 40 length: 64 - type: phone #notrans name: phone #notrans label: Phone Number sort: 3 flags: 13057 - type: memo #notrans name: notes label: आंतरिक टिप्पणियां sort: 4 flags: 12289 configuration: rows: 4 cols: 40 - id: 2 type: T #notrans title: टिकट विवरण instructions: अपनी समस्या का वर्णन करें notes: | This form will be attached to every ticket, regardless of its source. You can add any fields to this form and they will be available to all tickets, and will be searchable with advanced search and filterable. flags: 0 fields: - id: 20 type: text #notrans name: subject #notrans label: समस्या का सारांश sort: 1 flags: 489265 configuration: size: 40 length: 50 - id: 21 type: thread #notrans name: message #notrans label: समस्या का विवरण hint: Details on the reason(s) for opening the ticket. sort: 2 flags: 480547 - id: 22 type: priority #notrans name: priority #notrans label: Priority Level flags: 274609 sort: 3 - type: C #notrans title: कंपनी की जानकारी instructions: ईमेल टेम्पलेट्स में उपलब्ध विवरण flags: 0 fields: - type: text #notrans name: name #notrans label: कंपनी का नाम sort: 1 flags: 291249 configuration: size: 40 length: 64 - type: text #notrans name: website #notrans label: वेबसाइट sort: 2 flags: 274705 configuration: size: 40 length: 64 - type: phone #notrans name: phone #notrans label: Phone Number sort: 3 flags: 274705 configuration: ext: false - type: memo #notrans name: address label: पता sort: 4 flags: 12545 configuration: rows: 2 cols: 40 html: false length: 100 - type: O #notrans title: संगठन का विवरण instructions: उपयोगकर्ता संगठन पर विवरण flags: 0 fields: - type: text #notrans name: name #notrans label: नाम sort: 1 flags: 489395 configuration: size: 40 length: 64 - type: memo name: address label: पता sort: 2 flags: 13057 configuration: rows: 2 cols: 40 length: 100 html: false - type: phone name: phone label: Phone sort: 3 flags: 13057 - type: text name: website label: वेबसाइट sort: 4 flags: 13057 configuration: size: 40 length: 0 - type: memo #notrans name: notes label: आंतरिक टिप्पणियां sort: 5 flags: 12289 configuration: rows: 4 cols: 40 - type: A #notrans title: Task Details instructions: Please Describe The Issue notes: | This form is used to create a task. flags: 0 fields: - type: text #notrans name: title #notrans flags: 487601 sort: 1 label: Title configuration: size: 40 length: 50 - type: thread #notrans name: description #notrans flags: 413939 sort: 2 label: Description hint: Details on the reason(s) for creating the task. - #Default groups defined for the system #Fields: #id - Primary id for the group #role_id - (int) default role for the group #flags - (bit mask) group flags #name - (string) descriptive name for the group #notes - (string) administrative notes (viewable internally only) #depts: (list<Department<id>>) id's of the departments to which the group #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. --- id: 1 role_id: 1 flags: 1 name: Lion Tamers notes: | प्रणाली अधिपतियों। इन लोगों (शुरू) का सभी विभागों पर उपयोग करने का पूर्ण नियंत्रण है। depts: - 1 - 2 - 3 - id: 2 role_id: 2 flags: 1 name: इंद्रजीत notes: | संचालक depts: - 1 - 2 - 3 - id: 3 role_id: 2 flags: 1 name: नए प्रशिक्षकों notes: | सदस्य कर्मचारी depts: - 1 - 2 - 3 - #Default help topics installed for the system #Fields: #id - (int:optional) id number in the database #topic - (string) descriptive name of the help topic #flags - (bitmask: Active | Disabled | Archived) #ispublic - (bool:0|1) true or false if end users should be able to see the #help topic. In other words, true or false if the help topic is _not_ #for internal use only #noautoresp - (bool:1) true to disable the auto-responder for tickets #assigned to this help topic. NOTE that this field must be completely #omitted to ENABLE the auto-response by default #dept_id - (int) id number of the department with which this help topic is #associated #sla_id - (int:optional) id number of the sla with which this help topic is #associated #notes - (string) administrative notes (internally viewable only) --- topic_id: 1 flags: 0x02 ispublic: 1 priority_id: 2 forms: - 2 topic: सामान्य पूछताछ notes: | उत्पादों या सेवाओं के बारे में प्रश्न - topic_id: 2 flags: 0x02 ispublic: 1 priority_id: 1 forms: - 2 topic: प्रतिक्रिया notes: | Tickets that primarily concern the sales and billing departments - topic_id: 10 flags: 0x02 ispublic: 1 dept_id: 3 priority_id: 2 forms: - 2 topic: समस्या के बारे में बताएं notes: | उत्पाद, सेवा, या उपकरण से संबंधित मुद्दों - topic_pid: 10 flags: 0x02 ispublic: 1 sla_id: 1 priority_id: 3 forms: - 2 topic: Access Issue notes: | Report an inability access a physical or virtual asset - #Custom (dynamic) lists. This data is used as the initial, #minimal data for dynamic list that ships with the system. #Fields: #id: Primary id (not recommended) #name: Name of the list #name_plural: Name in plural (optional) #sort_mode: Sorting order (Alpha, -Alpha, SortCol) #masks: Edit masks to indicate various statuses of the list #(e.g if editable or deletable..etc) #notes: Notes for the list #items: List of items for the list #id: Primary id #value: Value (name) of the list item #extra: Abbreviated version of the value #status: If enabled (1 - enabled, 0 - disabled) #sort: Sort order (optional) #properties: Item-specific config based on Ticket Flags form fields #(key): (value) #properties: List properties form (see form.yaml for details) #Ticket statuses --- type: ticket-status #notrans name: Ticket Status name_plural: टिकट की स्थितियां sort_mode: SortCol #notrans masks: 13 notes: | टिकट की स्थितियां properties: title: Ticket Status Properties instructions: Properties that can be set on a ticket status. flags: 0 fields: - type: state #notrans name: state #notrans label: State sort: 1 flags: 487665 configuration: prompt: State of a ticket - type: memo #notrans name: description #notrans label: Description sort: 3 flags: 471073 configuration: rows: 2 cols: 40 html: false length: 100 configuration: handler: TicketStatusList - #Initial organizations defined for the system. #Fields: #name - Descriptive name for the organization #fields - custom fields --- name: osTicket fields: 0: | 1120 5th Street Alexandria, LA 71301 phone: (318) 290-3674 website: https://osticket.com notes: > हम न केवल सॉफ्टवेयर का विकास करते हैं, हम भी osTicket के लिए समर्थन का प्रबंधन करने के लिए इसका इस्तेमाल करते हैं। हमें लागू मदद से आप जल्दी और osTicket की सुविधाओं और कार्यक्षमता की पूरी क्षमता का लाभ उठाने दें। पेशेवर समर्थन के लिए हमसे संपर्क करें या दस्तावेज और समुदाय के समर्थन के लिए हमारी वेबसाइट पर जाएँ। #Default system data for ticket priorities --- low: priority_id: 1 priority_desc: अल्पतर priority_color: "#DDFFDD" priority_urgency: 4 normal: priority_id: 2 priority_desc: साधारण priority_color: "#FFFFF0A" priority_urgency: 3 high: priority_id: 3 priority_desc: उच्च priority_color: "FEE7E7" priority_urgency: 2 emergency: priority_id: 4 priority_desc: आपात priority_color: "FEE7E7" priority_urgency: 1 - #Columns are not necessary and a default list is used if no columns are #specified. #Fields: #id: #flags: (unused) #name: Display name of the column #primary: Data source for the field #secondary: Backup data source / default text #filter: What the field should link to #'link:ticket': Ticket #'link:user': User #'link:org': Organization #'link:ticketP': Ticket with hover preview #truncate: #'wrap': Fold words on multiple lines #annotations: #c: Annotation class name #p: Placement #'a': After column text #'b': Before column text #'<': Float to start (left) #'>': Float to end (right) #conditions: #crit: Criteria for the condiditon, in the form of [field, method, value] #prop: Array of CSS properties to apply to the field #'font-weight': #'font-style': #... #extra: (future use and for plugins) --- id: 1 name: "Ticket #" primary: "number" filter: "link:ticketP" truncate: "wrap" annotations: '[{"c":"TicketSourceDecoration","p":"b"}]' conditions: '[{"crit":["isanswered","nset",null],"prop":{"font-weight":"bold"}}]' - id: 2 name: "Date Created" primary: "created" secondary: null filter: "date:full" truncate: "wrap" annotations: "[]" conditions: "[]" - id: 3 name: "विषय" primary: "cdata__subject" filter: "link:ticket" truncate: "ellipsis" annotations: '[{"c":"TicketThreadCount","p":">"},{"c":"ThreadAttachmentCount","p":"a"},{"c":"OverdueFlagDecoration","p":"<"},{"c":"LockDecoration","p":"<"}]' conditions: '[{"crit":["isanswered","nset",null],"prop":{"font-weight":"bold"}}]' - id: 4 name: "User Name" primary: "user__name" truncate: "wrap" annotations: '[{"c":"ThreadCollaboratorCount","p":">"}]' conditions: "[]" - id: 5 name: "प्राथमिकता" primary: "cdata__priority" truncate: "wrap" annotations: "[]" conditions: "[]" - id: 6 name: "Status" primary: "status__id" truncate: "wrap" annotations: "[]" conditions: "[]" - id: 7 name: "Close Date" primary: "closed" filter: "date:full" truncate: "wrap" annotations: "[]" conditions: "[]" - id: 8 name: "Assignee" primary: "assignee" truncate: "wrap" annotations: "[]" conditions: "[]" - id: 9 name: "Due Date" primary: "duedate" secondary: "est_duedate" filter: "date:human" truncate: "wrap" annotations: "[]" conditions: "[]" - id: 10 name: "Last Updated" primary: "lastupdate" filter: "date:full" truncate: "wrap" annotations: "[]" conditions: "[]" - id: 11 name: "विभाग" primary: "dept_id" truncate: "wrap" annotations: "[]" conditions: "[]" - id: 12 name: "Last Message" primary: "thread__lastmessage" filter: "date:human" truncate: "wrap" annotations: "[]" conditions: "[]" - id: 13 name: "Last Response" primary: "thread__lastresponse" filter: "date:human" truncate: "wrap" annotations: "[]" conditions: "[]" - id: 14 name: "Team" primary: "team_id" truncate: "wrap" annotations: "[]" conditions: "[]" - #Columns are not necessary and a default list is used if no columns are #specified. #Fields: #id: --- id: 1 name: Priority + Most Recently Updated columns: '["-cdata__priority","-lastupdate"]' - id: 2 name: Priority + Most Recently Created columns: '["-cdata__priority","-created"]' - id: 3 name: Priority + Due Date columns: '["-cdata__priority","-est_duedate"]' - id: 4 name: Due Date columns: '["-est_duedate"]' - id: 5 name: Closed Date columns: '["-closed"]' - id: 6 name: Create Date columns: '["-created"]' - id: 7 name: Update Date columns: '["-lastupdate"]' - #Basic queues for the initial ticket system. Queues installed for #- Open / All #- Open / Unassigned #- Open / Overdue #- Answered / All #- My Tickets / All #- Closed / All #Fields: #id: #parent_id: #flags: #0x01: FLAG_PUBLIC #0x02: FLAG_QUEUE (should be set for everything here) #0x04: FLAG_DISABLED #0x08: FLAG_INHERIT (inherit criteria from parent) #0x10: FLAG_INHERIT_COLUMNS #0x20: FLAG_INHERIT_SORTING #staff_id: User owner of the queue #sort: Manual sort order #title: Display name of the queue #config: Criteria configuration #filter: Quick filter field #root: Object type of the queue listing #'T': Tickets #'A': Tasks --- id: 1 title: Open parent_id: 0 flags: 0x03 sort: 1 sort_id: 1 root: T config: '[["status__state","includes",{"open":"Open"}]]' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 10 bits: 1 sort: 2 width: 150 heading: Last Updated - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 5 bits: 1 sort: 5 width: 85 heading: प्राथमिकता - column_id: 8 bits: 1 sort: 6 width: 160 heading: को सौपा sorts: - sort_id: 1 - sort_id: 2 - sort_id: 3 - sort_id: 4 - sort_id: 6 - sort_id: 7 - id: 2 title: Open parent_id: 1 flags: 43 root: T sort: 1 sort_id: 4 config: '{"criteria":[["isanswered","nset",null]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 10 bits: 1 sort: 2 width: 150 heading: Last Updated - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 5 bits: 1 sort: 5 width: 85 heading: प्राथमिकता - column_id: 8 bits: 1 sort: 6 width: 160 heading: को सौपा - id: 3 title: Answered parent_id: 1 flags: 43 root: T sort: 2 sort_id: 4 config: '{"criteria":[["isanswered","set",null]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 10 bits: 1 sort: 2 width: 150 heading: Last Updated - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 5 bits: 1 sort: 5 width: 85 heading: प्राथमिकता - column_id: 8 bits: 1 sort: 6 width: 160 heading: को सौपा - id: 4 title: अतिदेय parent_id: 1 flags: 43 root: T sort: 3 sort_id: 4 config: '{"criteria":[["isoverdue","set",null]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 9 bits: 1 sort: 9 width: 150 heading: Due Date - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 5 bits: 1 sort: 5 width: 85 heading: प्राथमिकता - column_id: 8 bits: 1 sort: 6 width: 160 heading: को सौपा - id: 5 title: My Tickets parent_id: 0 flags: 0x03 root: T sort: 3 sort_id: 3 config: '{"criteria":[["assignee","includes",{"M":"Me","T":"One of my teams"}],["status__state","includes",{"open":"Open"}]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 10 bits: 1 sort: 2 width: 150 heading: Last Update - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 5 bits: 1 sort: 5 width: 85 heading: प्राथमिकता - column_id: 11 bits: 1 sort: 6 width: 160 heading: विभाग sorts: - sort_id: 1 - sort_id: 2 - sort_id: 3 - sort_id: 4 - sort_id: 6 - sort_id: 7 - id: 6 title: Assigned to Me parent_id: 5 flags: 43 root: T sort: 1 config: '{"criteria":[["assignee","includes",{"M":"Me"}]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 10 bits: 1 sort: 2 width: 150 heading: Last Update - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 5 bits: 1 sort: 5 width: 85 heading: प्राथमिकता - column_id: 11 bits: 1 sort: 6 width: 160 heading: विभाग sorts: - sort_id: 1 - sort_id: 2 - sort_id: 3 - sort_id: 4 - sort_id: 6 - sort_id: 7 - id: 7 title: Assigned to Teams parent_id: 5 flags: 43 root: T sort: 2 config: '{"criteria":[["assignee","!includes",{"M":"Me"}]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 10 bits: 1 sort: 2 width: 150 heading: Last Update - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 5 bits: 1 sort: 5 width: 85 heading: प्राथमिकता - column_id: 14 bits: 1 sort: 6 width: 160 heading: Team sorts: - sort_id: 1 - sort_id: 2 - sort_id: 3 - sort_id: 4 - sort_id: 6 - sort_id: 7 - id: 8 parent_id: 0 title: बंद flags: 0x03 sort: 4 root: T sort_id: 5 config: '{"criteria":[["status__state","includes",{"closed":"Closed"}]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 7 bits: 1 sort: 2 width: 150 heading: Date Closed - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 8 bits: 1 sort: 6 width: 160 heading: Closed By sorts: - sort_id: 5 - sort_id: 1 - sort_id: 2 - sort_id: 3 - sort_id: 4 - sort_id: 6 - sort_id: 7 - id: 9 parent_id: 8 title: Today flags: 43 sort: 1 root: T sort_id: 5 config: '{"criteria":[["closed","period","td"]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 7 bits: 1 sort: 2 width: 150 heading: Date Closed - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 8 bits: 1 sort: 6 width: 160 heading: Closed By sorts: - sort_id: 5 - sort_id: 1 - sort_id: 2 - sort_id: 3 - sort_id: 4 - sort_id: 6 - sort_id: 7 - id: 10 parent_id: 8 title: Yesterday flags: 43 sort: 2 root: T sort_id: 5 config: '{"criteria":[["closed","period","yd"]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 7 bits: 1 sort: 2 width: 150 heading: Date Closed - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 8 bits: 1 sort: 6 width: 160 heading: Closed By sorts: - sort_id: 5 - sort_id: 1 - sort_id: 2 - sort_id: 3 - sort_id: 4 - sort_id: 6 - sort_id: 7 - id: 11 parent_id: 8 title: This Week flags: 43 sort: 3 root: T sort_id: 5 config: '{"criteria":[["closed","period","tw"]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 7 bits: 1 sort: 2 width: 150 heading: Date Closed - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 8 bits: 1 sort: 6 width: 160 heading: Closed By sorts: - sort_id: 5 - sort_id: 1 - sort_id: 2 - sort_id: 3 - sort_id: 4 - sort_id: 6 - sort_id: 7 - id: 12 parent_id: 8 title: This Month flags: 43 sort: 4 root: T sort_id: 5 config: '{"criteria":[["closed","period","tm"]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 7 bits: 1 sort: 2 width: 150 heading: Date Closed - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 8 bits: 1 sort: 6 width: 160 heading: Closed By sorts: - sort_id: 5 - sort_id: 1 - sort_id: 2 - sort_id: 3 - sort_id: 4 - sort_id: 6 - sort_id: 7 - id: 13 parent_id: 8 title: This Quarter flags: 43 sort: 5 root: T sort_id: 6 config: '{"criteria":[["closed","period","tq"]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 7 bits: 1 sort: 2 width: 150 heading: Date Closed - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 8 bits: 1 sort: 6 width: 160 heading: Closed By sorts: - sort_id: 5 - sort_id: 1 - sort_id: 2 - sort_id: 3 - sort_id: 4 - sort_id: 6 - sort_id: 7 - id: 14 parent_id: 8 title: This Year flags: 43 sort: 6 root: T sort_id: 7 config: '{"criteria":[["closed","period","ty"]],"conditions":[]}' columns: - column_id: 1 bits: 1 sort: 1 width: 100 heading: टिकट - column_id: 7 bits: 1 sort: 2 width: 150 heading: Date Closed - column_id: 3 bits: 1 sort: 3 width: 300 heading: विषय - column_id: 4 bits: 1 sort: 4 width: 185 heading: द्वारा - column_id: 8 bits: 1 sort: 6 width: 160 heading: Closed By sorts: - sort_id: 5 - sort_id: 1 - sort_id: 2 - sort_id: 3 - sort_id: 4 - sort_id: 6 - sort_id: 7 - #Default roles defined for the system #Fields: #id - Primary id for the role #flags - (bit mask) role flags #name - (string) descriptive name for the role #notes - (string) internal notes #permissions: (list<keys>) #NOTE: ------------------------------------ #--- id: 1 flags: 1 name: All Access notes: | Role with unlimited access permissions: - ticket.create - ticket.edit - ticket.merge - ticket.link - ticket.markanswered - ticket.assign - ticket.release - ticket.transfer - ticket.refer - ticket.reply - ticket.close - ticket.delete - task.create - task.edit - task.assign - task.transfer - task.reply - task.close - task.delete - canned.manage - thread.edit - id: 2 flags: 1 name: Expanded Access notes: | Role with expanded access permissions: - ticket.create - ticket.edit - ticket.merge - ticket.link - ticket.assign - ticket.release - ticket.transfer - ticket.refer - ticket.reply - ticket.close - task.create - task.edit - task.assign - task.transfer - task.reply - task.close - canned.manage - id: 3 flags: 1 name: Limited Access notes: | Role with limited access permissions: - ticket.create - ticket.merge - ticket.link - ticket.assign - ticket.release - ticket.transfer - ticket.refer - ticket.reply task.create - task.assign - task.transfer - task.reply - id: 4 flags: 1 name: View only notes: Simple role with no permissions permissions: [ ] - #Initial set of schedules and entries #Fields: #id: #flags: #0x01: FLAG_BIZHRS (Business Hours - Otherwise Holidays is assumed) #sort: Manual sort order #name: Name of the Schedule #timezone: Timezone of the Schedule #description: Description of the Schedule #entries: Schedule Entries --- id: 1 flags: 0x01 name: Monday - Friday 8am - 5pm with U.S. Holidays configuration: holidays: - 4 entries: - name: Monday repeats: weekly #notrans starts_on: 2019-01-07 starts_at: 08:00:00 ends_on: 2019-01-07 ends_at: 17:00:00 day: 1 - name: Tuesday repeats: weekly #notrans starts_on: 2019-01-08 starts_at: 08:00:00 ends_on: 2019-01-08 ends_at: 17:00:00 day: 2 - name: Wednesday repeats: weekly #notrans starts_on: 2019-01-09 starts_at: 08:00:00 ends_on: 2019-01-09 ends_at: 17:00:00 day: 3 - name: Thursday repeats: weekly #notrans starts_on: 2019-01-10 starts_at: 08:00:00 ends_on: 2019-01-10 ends_at: 17:00:00 day: 4 - name: Friday repeats: weekly #notrans starts_on: 2019-01-11 starts_at: 08:00:00 ends_on: 2019-01-11 ends_at: 17:00:00 day: 5 - id: 2 flags: 0x01 name: 24/7 entries: - name: Daily repeats: daily #notrans starts_on: 2019-01-01 starts_at: 00:00:00 ends_on: 2019-01-01 ends_at: 23:59:59 - id: 3 flags: 0x01 name: 24/5 entries: - name: Weekdays repeats: weekdays #notrans starts_on: 2019-01-01 starts_at: 00:00:00 ends_on: 2019-01-01 ends_at: 23:59:59 - id: 4 flags: 0 name: U.S. Holidays entries: - name: New Year's Day repeats: yearly #notrans starts_on: 2019-01-01 starts_at: 00:00:00 ends_on: 2019-01-01 ends_at: 23:59:59 day: 1 month: 1 - name: MLK Day repeats: yearly #notrans starts_on: 2019-01-21 starts_at: 00:00:00 ends_on: 2019-01-21 ends_at: 23:59:59 day: 1 week: 3 month: 1 - name: Memorial Day repeats: yearly #notrans starts_on: 2019-05-27 starts_at: 00:00:00 ends_on: 2019-05-27 ends_at: 23:59:59 day: 1 week: -1 month: 5 - name: Independence Day (4th of July) repeats: yearly #notrans starts_on: 2019-07-04 starts_at: 00:00:00 ends_on: 2019-07-04 ends_at: 23:59:59 day: 4 month: 7 - name: Labor Day repeats: yearly #notrans starts_on: 2019-09-02 starts_at: 00:00:00 ends_on: 2019-09-02 ends_at: 23:59:59 day: 1 week: 1 month: 9 - name: Indigenous Peoples' Day (Whodat Columbus) repeats: yearly #notrans starts_on: 2019-10-14 starts_at: 00:00:00 ends_on: 2019-10-14 ends_at: 23:59:59 day: 1 week: 2 month: 10 - name: Veterans Day repeats: yearly #notrans starts_on: 2019-11-11 starts_at: 00:00:00 ends_on: 2019-11-11 ends_at: 23:59:59 day: 11 month: 11 - name: Thanksgiving Day repeats: yearly #notrans starts_on: 2019-11-28 starts_at: 00:00:00 ends_on: 2019-11-28 ends_at: 23:59:59 day: 4 week: 4 month: 11 - name: Christmas Day repeats: yearly #notrans starts_on: 2019-11-25 starts_at: 00:00:00 ends_on: 2019-11-25 ends_at: 23:59:59 day: 25 month: 12 - #Sequences installed with the system #Fields: #id: PK #name: Name of the sequence #next: Next value of the sequence #padding: Padding character #increment: Distance between two numbers of the sequence #flags: Bitmask of flag settings. Currently known values are #INTERNAL:=0x0001 (restrict delete) #ID:1 is reserved for upgrades. When transitioning to osTicket 1.10, the #sequence ID:1 will be configured to start counting from the current #MAX(ticket.ticket_id). The upgrade will miss this step if there is no #sequence with ID:1 --- id: 1 name: "सामान्य टिकट" next: 1 padding: '0' increment: 1 flags: 1 - id: 2 name: "Tasks Sequence" next: 1 padding: '0' increment: 1 flags: 1 - #Initial Service-Level-Agreements (SLA) defined for the system #Fields: #id - (int:optional) id number in the database #flags - (int:bitmask) #isactive - (flag:1) true of false if the SLA should initially be active #enable_priority_escalation - (flag:2) true or false if the SLA should #cause the ticket priority to be escalated when it is marked overdue #disable_overdue_alerts - (flag:4) - true or false if the overdue alert #emails should _not_ go out for tickets assigned to this SLA #transient - (flag:8) - true if the SLA should change when changing #department or help topic. #grace_period - (int) number or hours after the ticket is opened before it #is marked overdue #name - (string) descriptive name of the SLA #notes - (string) administrative notes (viewable internally only) --- id: 1 flags: 3 grace_period: 18 name: पूर्वनिर्धारित सेवा स्तर समझौता notes: | - #Initial teams defined for the system. #Fields: #flags - (int) #- isenabled - (0x01) true or false if the team should be initially #enabled #- noalerts - (0x02) #name - Descriptive name for the team #notes - Administrative notes (viewable internal only) --- flags: 0x01 name: स्तर 1 समर्थन notes: | Tier 1 support, responsible for the initial iteraction with customers - #Default system data for ticket statuses #Fields: #id - (int:optional) id number in the database #name - (string) descriptive name of the status #state - (string) Main status of a ticket #(open, closed, archived, deleted) #mode - (bit) access mask (1 - enabled, 2 - internal) #flags - (bit) flags that can be set on a ticket #properties: #description - (string) Description of the status --- id: 1 name: Open state: open mode: 3 sort: 1 flags: 0 properties: description: > खुली टिकट - id: 2 name: सुलझाया गया state: closed mode: 1 sort: 2 flags: 0 properties: allowreopen: true reopenstatus: 0 description: > Resolved tickets - id: 3 name: बंद state: closed mode: 3 sort: 3 flags: 0 properties: allowreopen: true reopenstatus: 0 description: > Closed tickets. Tickets will still be accessible on client and staff panels. - id: 4 name: संग्रहीत state: archived mode: 3 sort: 4 flags: 0 properties: description: > Tickets only adminstratively available but no longer accessible on ticket queues and client panel. - id: 5 name: मिटाया गया state: deleted mode: 3 sort: 5 flags: 0 properties: description: > Tickets queued for deletion. Not accessible on ticket queues. #This is popup help messages for the Admin Panel -> Dashboard -> Audit Logs page #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- audit_logs: title: Audit Logs content: > This is where you will find any activities written to the audit log while the Audit plugin is enabled links: - title: Configure Plugins href: /scp/plugins.php date_span: title: Date Span content: > Select the date range that you would like to view in the <span class="doc-desc-title">Audit Logs</span>. type: title: Type content: > Choose which object type you would like to see Audits for. events: title: Events content: > Narrow down results based on a specific Event. #This is popup help messages for the Staff Panel -> Dashboard -> Dashboard #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- ticket_activity: title: टिकट गतिविधि content: > Select a date range to cause both the graph and the table (cf. <span class="doc-desc-title">Statistics</span>) below to focus on any corresponding data for those dates. The graph below will always reflect a broad overview of the whole system’s data (i.e., population). However, you may navigate through the <span class="doc-desc-title">Statistics </span> table below to focus on a narrower subject of interest (e.g., Department, Topics, or Staff). Additionally, you may export any data currently displayed in the <span class="doc-desc-title">Statistics </span> table. report_timeframe: title: रिपोर्ट समय सीमा content: > Choose a start date for the desired data sample using the date picker. Then, choose the length of time from that date to define the end date for your data sample. statistics: title: आंकड़े content: > Navigate to the subject of interest by clicking on the appropriate tab in order to view the specific sample of data. Within the table, the circles represent the size of the nominal data. Therefore, the larger the number in a particular cell, the larger the adjacent circle will be. opened: title: खोला गया content: > Tickets that were originally opened having the Department or Help Topic on the ticket, or the number of tickets an Agent has opened on behalf of a User. assigned: title: सौंपा गया content: > Tickets that have been assigned to either an Agent or a Team. The number reflects tickets that are manually assigned to agents or teams, claimed tickets, and tickets assigned from ticket filters/other auto-assignment rules. overdue: title: अतिदेय content: > Tickets that have been marked ‘Overdue’ by the system. Tickets are marked Overdue when they have violated the SLA Plan to which they belonged, causing them to have a status of ‘Open’ past their Due Date. closed: title: बंद content: > The number of Tickets that are currently in the Closed status. reopened: title: पुनः खोला गया content: > The total number of times a ticket was Reopened. Tickets are reopened whenever their status is changed from Closed to Open. deleted: title: मिटाया गया content: > The amount of tickets that have been deleted. service_time: title: सेवा में लगा समय content: > Refers to the duration of time that begins at the opening of a ticket and ends when the ticket is closed. The Service Time column measures the average Service Time per ticket, in hours. response_time: title: प्रतिक्रिया में लगा समय content: > Shows an average response time by an Agent, in hours, to ticket correspondence. #This is popup help messages for the Staff Panel -> Dashboard -> My Profile #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- contact_information: title: संपर्क जानकारी content: > username: title: उपयोगकर्ता का नाम content: > Only those Agents with Admin status may change a username. If you are an Agent with Admin privileges, you may accomplish this by selecting an Agent to edit from the <span class="doc-desc-title">Staff Members</span> table. links: - title: Change a username as an Administrator href: /scp/staff.php config2fa: title: Two Factor Authentication content: > Two Factor Authentication adds an extra layer of security when logging into the helpdesk. Once you correctly submit your username and password, you will need to enter a token to finish logging into the helpdesk. time_zone: title: समय क्षेत्र content: > daylight_saving: title: Daylight Saving content: > maximum_page_size: title: Maximum Page Size content: > auto_refresh_rate: title: Auto Refresh Rate content: > default_signature: title: Default Signature content: > default_paper_size: title: Default Paper Size content: > show_assigned_tickets: title: निरुपित टिकट दिखाएँ content: > <p>ईस विकल्प का चुनाव करने पर पूर्व मे ग्लोबल सेट्टिंग के विकल्प खुली कतार से अनुमोदित टिकट को हटाना को निष्क्रीय कर दिया जायेगा।</p> <p class="info-banner"> <i class="icon-info-sign"></i> ये विकल्प तभी उपलब्ध होगा जब अनुमोदित टिकट को वैश्विक रूप से छोड़ा जाए।</p> password: title: पासवर्ड content: > current_password: title: वर्तमान पासवर्ड content: > new_password: title: नया पासवर्ड content: > confirm_new_password: title: नए पासवर्ड की पुष्टि करें content: > signature: title: हस्ताक्षर content: > Create an optional <span class="doc-desc-title">Signature</span> that perhaps appears at the end of your Ticket Responses. Whether this <span class="doc-desc-title">Signature</span> appears, or not, depends on the <span class="doc-desc-title">Email Template</span> that will be used in a Ticket Response. links: - title: Create Emails Templates in the Admin Panel href: /scp/templates.php #This is popup help messages for the Staff Panel -> Dashboard -> Staff Directory #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- staff_members: title: सदस्य कर्मचारी content: > निम्न तालिका यह ऊपर फिल्टर के परिणामों को प्रदर्शित करता है। कोई फ़िल्टर सेटिंग्स नहीं चुना जाता है, तो सभी <span class="doc-desc-title">सदस्य कर्मचारी </span> को विभिन्न पन्नों पर प्रदर्शित कर रहे हैं। अधिक परिणामों के माध्यम से संचालन करने के लिए नीचे दिए गए पृष्ठों अनुभाग देखें। apply_filtering_criteria: title: निस्पंदन मानदंड लागू करे content: > अपने वर्तमान हितों की प्रासंगिक के लिए एक <span class="doc-desc-title">विभाग</span> चुनें। आप भी एक विशिष्ट एजेंट के लिए एक खोज प्रदर्शन कर सकते हैं। #This is popup help messages for the Admin Panel -> Dashboard -> System Logs page #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- system_logs: title: System Logs content: > This is where you will find any troubleshooting related logging activity (e.g., Errors, Warnings, or Bugs). links: - title: Customize what type of activity is logged by changing the <br /><span class="doc-desc-title">Default Log Level</span>. href: /scp/settings.php?t=system date_span: title: Date Span content: > Select your calendar range that you would like to view in the <span class="doc-desc-title">System Logs</span>. type: title: Type content: > Choose an option to narrow your focus on a specific type of activity. <span class="doc-desc-opt">Debug</span> represents the least severity, and <span class="doc-desc-opt">Error</span> represents the greatest severity. showing_logs: title: Showing…Logs content: > Be sure to check the <span class="doc-desc-title">Page</span> section below to make sure that there are not more pages displaying available System Logs. log_title: title: Log Title content: > Click the <span class="doc-desc-title">Log Title</span> table header if you would like to sort the results according to the <span class="doc-desc-title">Log Title</span>. log_type: title: Log Type content: > Click the <span class="doc-desc-title">Log Type</span> table header if you would like to sort the results according to the <span class="doc-desc-title">Log Type</span>. log_date: title: Log Date content: > This is the date the log was generated by the software. If you would like to sort the results according to the <span class="doc-desc-title">Log Date</span>, simply click the <span class="doc-desc-title">Log Date</span> table header. (Use the <span class="doc-desc-title">Date Span</span> form above to narrow your calendar span of logs.) ip_address: title: IP Address content: > This refers to the <span class="doc-desc-title">IP</span><span class="doc-desc-title"> Address</span> of either the agent or client that was using osTicket at the time the log was generated. #This is popup help messages for the Admin Panel -> Emails -> Banlist #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- ban_list: title: प्रतिबंधित ईमेल पते content: > प्रतिबंध सूची में सूचीबद्ध ई-मेल पते से प्राप्त ईमेल स्वचालित रूप से अस्वीकार कर दिया जाएगा। #This is popup help messages for the Admin Panel -> Emails -> Diagnostics #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- test_outgoing_email: title: निवर्तमान ईमेल परीक्षण content: > The email’s delivery depends on your server settings (php.ini) and/or SMTP configuration. links: - title: Select an email to configure SMTP (Outgoing) Settings href: /scp/emails.php from: title: द्वारा content: > to: title: के लिये content: > subject: title: विषय content: > message: title: संदेश content: > #This is popup help messages for the Admin Panel -> Emails -> Add New Email #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- new_ticket_help_topic: title: New Ticket Help Topic content: > Choose a <span class="doc-desc-title">Help Topic</span> to be automatically associated with tickets created via this Email Address. <br/><br/> Forms associated with the Help Topic will be added to the ticket, but will not have any data. links: - title: Manage Help Topics href: /scp/helptopics.php new_ticket_priority: title: New Ticket Priority content: > Choose the <span class="doc-desc-title">priority</span> for new tickets created via this Email Address. new_ticket_department: title: नया टिकट विभाग content: > Choose the <span class="doc-desc-title">Department</span> to which new tickets created via this Email Address will be routed. links: - title: विभागों को प्रबंधित करें href: /scp/departments.php auto_response: title: New Ticket Auto-Response content: > You may disable the Auto-Response sent to the User when a new ticket is created via this Email Address. userid: title: उपयोगकर्ता का नाम content: > The Username is utilized in the email authentication process. We accept single address strings, shared mailbox strings, servername + username strings, and a combination of all. links: - title: More Information href: https://docs.osticket.com/en/latest/Admin/Emails/Emails.html username: title: उपयोगकर्ता का नाम content: > password: title: पासवर्ड content: > login_information: title: Email Login Information content: > The <span class="doc-desc-title">Username</span> and <span class="doc-desc-title">Password</span> are required to fetch email from IMAP / POP mail boxes as well as to send email through SMTP. mail_account: title: Fetching Email content: > Fetch emails from a remote IMAP or POP mail box and convert them to tickets in your help desk. links: - title: Manage <span class="doc-desc-title">Email Polling</span> & <span class="doc-desc-title">AutoCron</span> settings. href: /scp/settings.php?t=emails host_and_port: title: Remote Host content: > Enter the <span class="doc-desc-title">hostname</span> and <span class="doc-desc-title">port</span> number for your mail server. This may be available in the documentation for your hosting account or from your email administrator. <br/><br/> If using non-standard <span class="doc-desc-title">port</span> number with <span class="doc-desc-title">encryption</span> enabled then prefix the hostname with ssl:// or tls:// scheme to hint to supported encryption. <br/><br/> To force a plain connection even when using a standard encryption <span class="doc-desc-title">port</span> then use plain:// scheme. mailbox_folder: title: Mail Folder content: > Enter the <span class="doc-desc-title">Folder</span> name that you wish to fetch mail from. If left empty the system will fetch from the INBOX. protocol: title: Mail Box Protocol content: > Select the mail box protocol supported by your remote mail server. IMAP on a secure port highly recommended. authentication: title: Authentication content: > osTicket <span class="doc-desc-title">OAuth2 Plugin</span> is required for Modern Authentication support. links: - title: Download osTicket Plugins href: https://osticket.com/download/ fetch_frequency: title: Fetch Frequency content: > Enter how often, in minutes, the system will poll the mail box. <br/><br/> This will define the average delay in receiving an Auto-Response after a User sends an email to this mail box. emails_per_fetch: title: Emails Per Fetch content: > Enter the number of emails processed at one time. fetched_emails: title: Fetched Emails content: > Decide what to do with processed emails: <br/><br/> <span class="doc-desc-opt"><b>Move to Folder</b></span>: This will backup your email from the INBOX to a folder you specify. If the folder does not yet exist on the server, the system will attempt to automatically create it. (<b>Recommended</b>) <hr> <span class="doc-desc-opt"><b>Delete Emails</b></span>: This will delete your email from the INBOX once it is processed. <hr> <span class="doc-desc-opt"><b>Do Nothing</b></span>: This will leave emails in your INBOX. The system will record the message ids of your email and attempt not to refetch it. However, this option may cause duplicate tickets to be created. (<em>Not Recommended</em>) smtp_settings: title: SMTP Settings content: > Email sent from the help desk can be sent through an SMTP server. This is recommended, if possible, as it will increase the likelyhood of email delivery and will make the emails less likely to be marked as spam. header_spoofing: title: Allow Header Spoofing content: > Enable this to allow sending emails via this mail box from an address other that the one given in the <span class="doc-desc-title">Email Address</span> setting above. <br/><br/> This advanced setting is generally used when sending mail from aliases of this mail box. strict_matching: title: Strict Email Matching content: > <b>Enable</b> this option to require the Email Address and the Token's Resource Owner to match. This is useful for preventing accidental authorization of a completely different account. <br><br> <b>Disable</b> this option to allow a different Resource Owner for the Token than the Email Address. This is useful for Shared Mailboxes/Aliases/etc. where you need to use a Service Account or Global Admin to authorize on behalf of the email. #This is popup help messages for the Admin Panel -> Emails -> Templates #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- email_templates: title: Email Templates content: > Email Template Sets are used to send Auto-Responses and Alerts for various actions that can take place during a Ticket’s lifetime. template_to_clone: title: Template to Clone content: > Choose a Template Set to clone or simply start with the stock email templates. language: title: Language content: > Select desired language for the <span class="doc-desc-opt">stock</span> <span class="doc-desc-title">Email Template Set</span>. Language packs are available on osTicket.com. links: - title: osTicket भाषा पैक्स href: https://osticket.com/download status: title: Status content: > <span class="doc-desc-opt">Enabled</span> Template Sets are available to be associated with Departments and set to the system default. Template Sets currently in-use cannot be <span class="doc-desc-opt">Disabled</span>. #This is popup help messages for the Admin Panel -> Settings -> System page #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- form_title: title: Form Headline content: > This title text is shown in a gray box above the form fields form_instructions: title: Form Instructions content: > You can add extra instructions which will help guide the user into the context of the form fields and possibly highlight required data. field_sort: title: Field Display Position content: > Click on the up-and-down arrow icon and drag the field row to sort within this form. Sorting preference does not take effect until the form is saved. field_label: title: Field Label content: > This label is shown as the prompt for this field. Typically, a short-answer field would be rendered like this one:<br> <strong>Label:</strong> <input type="text"> field_type: title: Field Content Type content: > This is used to define the type of input expected from the user. You can select from short and long answer, phone number, date and time, checkbox, drop-down list, or a custom list selection. links: - title: Custom Lists href: /scp/lists.php field_visibility: title: Field Visibility content: > Choose a visibility and requirement option for this field. <table border="1" cellpadding="2px" cellspacing="0" style="margin-top:7px" ><tbody style="vertical-align:top;"> <tr><th>Setting</th> <th>Result</th></tr> <tr><td>Optional</td> <td>Agents and EndUsers can see the field, but neither is required to answer.</td></tr> <tr><td>Required</td> <td>Agents and EndUsers can see the field, and both are required to answer</td></tr> <tr><td>Required for EndUsers</td> <td>Agents and EndUsers can see the field, only EndUsers are required to answer</td></tr> <tr><td>Required for Agents</td> <td>Agents and EndUsers can see the field, only Agents are required to answer</td></tr> <tr><td>Internal, Optional</td> <td>Only Agents can see the field, but no answer is required.</td></tr> <tr><td>Internal, Required</td> <td>Only Agents can see the field, and an answer is required.</td></tr> <tr><td>For EndUsers Only</td> <td>Only EndUsers can see the field, and an answer is required.</td></tr> </tbody></table> field_variable: title: Field Automation content: > The field data will be available to email and page templates via the name used in this column. For instance, fields on the common ticket form are available via <code>%{ticket.variable}</code>, where <strong>variable</strong> is the name used in this column.<br> <br> <em>Company information is available via <code>%{</code><code>company.variable}</code> and user information is available via <code>%{ticket.user.variable}</code></em> field_delete: title: Remove this Field content: > Check and save the form to remove a field from this form.<br> <br> <em>Deleting a field does not remove previously entered data for the field on completed forms. For instance, if a previously submitted ticket has data for a field, deleting the field from this form will not remove the data on the ticket.</em> #Help popup items for the installer #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- helpdesk_name: title: सहायता प्रणाली के लिये नाम content: | <p>अापकी समर्थन प्रणाली का नाम जैसे "[कंपनी का नाम] समर्थन"</p> system_email: title: डिफ़ॉल्ट/मूल सिस्टम ईमेल content: | <p>डिफ़ॉल्ट/मूल ईमेल पता जैसे support@yourcompany.com - आप बाद में और भी जोड़ सकते हैं !</p> default_lang: title: सिस्टम की डिफ़ॉल्ट/मूल भाषा content: | <p>इस भाषा के लिए प्रारंभिक डेटा, जैसे ईमेल टेम्पलेट्स और डिफ़ॉल्ट/मूल सिस्टम पृष्ठ, डेटाबेस में स्थापित किये जाएंगे।</p> links: - title: osTicket भाषा पैक्स href: 'https://osticket.com/download/#ostLang' first_name: title: प्रथम नाम content: | <p>ऎडमिन/व्यवस्थापक का प्रथम नाम</p> last_name: title: अंतिम नाम content: | <p>ऎडमिन/व्यवस्थापक का अंतिम नाम</p> email: title: ईमेल पता content: | <p>ऎडमिन/व्यवस्थापक का व्यक्तिगत ईमेल पता। यह सिस्टम के डिफ़ॉल्ट/मूल ईमेल पते से अलग होना चाहिए।</p> username: title: उपयोगकर्ता का नाम content: | <p>ऎडमिन/व्यवस्थापक का लाॅग-इन नाम। यह कम से कम तीन (3) वर्ण होना चाहिए।</p> password: title: पासवर्ड content: | <p>Admin's password. Must be six (6) characters or more.</p> password2: title: पासवर्ड की पुष्टि करें content: | <p>ऎडमिन/व्यवस्थापक का पासवर्ड दोबारा लिखें। यह पहले लिखे पासवर्ड से मिलना चाहिए।</p> db_prefix: title: MySQL टेबल प्रि्फिक्स content: | <p>एक साझा डेटाबेस में तालिकाओँ के बीच संघर्ष से बचने के लिए osTicket को तालिका उपसर्ग (टेबल प्रिफिक्स) की आवश्यकता होति है।</p> db_host: title: MySQL होस्ट-नाम content: | <p> अधिक्तर होस्ट लोकल डेटाबेस होस्ट-नाम के लिए 'लोकलहोस्ट' का प्रयोग करते हैं। यदि लोकलहोस्ट का प्रयोग करना विफल रहता है तो अपने होसट के साथ जाँच करें। </p> <p>Php. ini में निर्धारित डिफ़ॉल्ट पोर्ट का प्रयोग एक मानक पोर्ट के तौर पर किया जाता है। एक गैर मानक (नाॅन-स्टैंडर्ड) पोर्ट नंबर <code>hostname:port</code> के रूप में निर्दिष्ट किया जा सकता है</p> db_schema: title: MySQL डाटाबेस content: | <p>उस डेटाबेस का नाम जिसका उपयोग osTicket करेगा।</p> db_user: title: MySQL उपयोगकर्ता का नाम content: | <p>MySQL उपयोगकर्ता के पास डेटाबेस पर पूर्ण अधिकार होने चाहिए।</p> db_password: title: MySQL पासवर्ड content: | <p>ऊपर दिये गये उपयोगकर्ता से संबंद्धित MySQL पासवर्ड।</p> #This is popup help messages for the Staff Panel -> Knowledgebase -> Canned Responses -> Add New Response #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- canned_response: title: Canned Response content: > Create a <span class="doc-desc-title">Canned Response</span> that can be included in a ticket response. It can also be used as a <span class="doc-desc-title">Ticket Auto-Response</span> setup by a <span class="doc-desc-title">Ticket Filter</span>. links: - title: Setup a Ticket Filter href: /scp/filters.php canned_attachments: title: Canned Attachments content: > Attach a file that you would like to be automatically included in the ticket response that utilizes the new <span class="doc-desc-title"> Canned Response</span>. #This is popup help messages for the Staff Panel -> Knowledgebase -> Add New Category -> FAQ Category (Form) #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template.#This is popup help messages for the Staff Panel -> Knowledgebase -> FAQ #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- listing_type: title: Listing Type content: > Choose <span class="doc-desc-opt">Public (publish)</span> if you would like this <span class="doc-desc-title"> FAQ</span> to be published on public knowledgebase if the parent category is public. links: - title: Enable the Public Knowledgebase for the Client Portal href: /scp/settings.php?t=kb #This is popup help messages for the Admin Panel -> Manage -> API Keys #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- api_key: title: API Key content: > API keys are used to authenticate clients submitting new tickets via the Application Programming Interface (API). API keys are used instead of passwords. Since API keys may be sent unencrypted, they are linked to each client's network IP address. links: - title: osTicket API Documentation href: https://github.com/osTicket/osTicket-1.8/blob/develop/setup/doc/api.md ip_addr: title: IP Address content: > Client's network IP address. Each unique client IP address will require separate API keys #This is popup help messages for the Admin Panel -> Manage -> Add New Custom List #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- custom_lists: title: Custom Lists content: > Your <span class="doc-desc-title">custom lists</span> will permit you to create dropdown boxes with predefined options from which a Client can select in your <span class="doc-desc-title">Custom Forms</span>. If you would like to use this <span class="doc-desc-title">custom list</span> as a <span class="doc-desc-title">target</span> in a <span class="doc-desc-title">Ticket Filter</span>, be sure to add this list to your <span class="doc-desc-title">Ticket Details</span> form. name: title: नाम content: > plural_name: title: बहुवचन नाम content: > sort_order: title: क्रमबद्ध content: > list_s_initial_items: title: प्रारंभिक आइटम की सूची content: > value: title: Value content: > extra: title: अतिरिक्त content: > Abbreviations and such. If you happen to use internal codes for the items in this list, those codes and abbreviations can be entered in this column. If the custom list is rendered as a <span class="doc-desc-option"> TypeAhead</span>, these abbreviations can be used to search for the custom list items. #This is popup help messages for the Admin Panel -> Manage -> Filter #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- execution_order: title: Execution Order content: > Enter a number that controls the priority of the filter. The lower the number, the higher the priority this filter will have in being executed over against another filter that might have higher order of execution. <br><br> If you want this filter to be the last filter applied on a match, enable <span class="doc-desc-title">Stop Processing Further On Match</span>. target_channel: title: कुल्यिका content: > Choose the target <span class="doc-desc-title">Channel</span> for your <span class="doc-desc-title">ticket Filter</span>. The <span class="doc-desc-title">Channel</span> is the source through which the ticket arrived into the system. <br><br> For example, if you choose <span class="doc-desc-opt">Web Forms</span>, you are saying that you want to apply the <span class="doc-desc-title">ticket Filter</span> to those tickets that originated from the Client Portal's webform. rules_matching_criteria: title: Rules Matching Criteria content: > Choose how elastic you want the matches of your <span class="doc-desc-title">ticket Filter</span> to be. If you would like the <span class="doc-desc-title">ticket Filter</span> to match any of the rules, and then stop, choose <span class="doc-desc-opt">Match Any</span>. If you would like <em><strong>all rules</strong></em> of the <span class="doc-desc-title">ticket Filter</span> to be matched, choose <span class="doc-desc-opt">Match All</span>. reject_ticket: title: टिकट अस्वीकार content: > If this is enabled, further processing is stopped and all other choices of action below will be ignored on match. reply_to_email: title: Reply-To Email content: > Enable this if you want your Help Desk to honor a User's email application's <span class="doc-desc-title">Reply To</span> header. This field is only relevant if the <span class="doc-desc-title">Channel</span> above includes <span class="doc-desc-opt">Email</span>. ticket_auto_response: title: Disable Ticket Auto-Response content: > <em>Note: This will override any <span class="doc-desc-title">Department</span> or <span class="doc-desc-title">Autoresponder settings</span>.</em> canned_response: title: Canned Auto-Reply content: > Choose a <span class="doc-desc-title">Canned Response</span> you want to be emailed to the user on <span class="doc-desc-title">Ticket Filter</span> match. The <span class="doc-desc-title">New Ticket Auto-Reply</span> template used depends on what <span class="doc-desc-title">template set</span> is assigned as default, or to a matching ticket's <span class="doc-desc-title">Department</span>. links: - title: Manage Canned Responses href: /scp/canned.php - title: खाका समूह प्रबंधन href: /scp/templates.php - title: New Ticket Auto-Reply Template href: /scp/templates.php?id=2&a=manage department: title: विभाग content: > Choose what <span class="doc-desc-title">Department</span> you want the matches of the <span class="doc-desc-title">Ticket Filter</span> to be assigned. links: - title: विभागों को प्रबंधित करें href: /scp/departments.php priority: title: प्राथमिकता content: > Choose the <span class="doc-desc-title">Priority</span> level you want to be applied to the matches of the <span class="doc-desc-title">Ticket Filter</span>.<br /> <br /> <em>Note: This will override <span class="doc-desc-title">Department</span> or <span class="doc-desc-title"> Help Topic</span> settings.</em> sla_plan: title: SLA योजना content: > Choose the <span class="doc-desc-title">SLA Plan</span> you want to be applied to the matches of the <span class="doc-desc-title">Ticket Filter</span>. links: - title: SLA योजनाओं का प्रबंधन href: /scp/slas.php auto_assign: title: 'स्वत: आवंटित' content: > Choose an Agent or a Team to whom you want the matches of the <span class="doc-desc-title">Ticket Filter</span> to be assigned. links: - title: एजेंटों का प्रबंधन href: /scp/staff.php - title: टीमों का प्रबंधन href: /scp/teams.php help_topic: title: सहायक विषय content: > Choose the <span class="doc-desc-title">Help Topic</span> you want to be applied to the matches of the <span class="doc-desc-title">Ticket Filter</span>. links: - title: Manage Help Topics href: /scp/helptopics.php admin_notes: title: व्यवस्थापक नोट्स content: > These notes are only visible to those whose account type is ‘<span class="doc-desc-title">Admin</span>.’ #This is popup help messages for the Admin Panel -> Manage -> Help Topic #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- help_topic_information: title: Help Topic Information content: > <span class="doc-desc-title">Help Topics</span> guide what information is gathered from Users and how tickets are routed or assigned. topic: title: Topic Name content: > Unique Help Topic name. htstatus: title: Status content: > If disabled or archived, this <span class="doc-desc-title">Help Topic</span> will not be available. status: title: Ticket Status content: > Select the Ticket Status assigned to new tickets related to this <span class="doc-desc-title">Help Topic</span>. <br><br> Ticket Filters can override new Ticket Status. type: title: Type content: > If a <span class="doc-desc-title">Help Topic</span> is labeled as Private, it will only be available for Agents to choose when an Agent opens a new Ticket under the Staff Panel. parent_topic: title: Parent Topic content: > Select the Parent Topic to which this <span class="doc-desc-title">Help Topic</span> will belong. The Parent Topic will appear first in the listing with this <span class="doc-desc-title">Help Topic</span> listed behind the parent. custom_form: title: Custom Form content: > Custom Forms will help you acquire more specific information from Users that are relevant to this <span class="doc-desc-title">Help Topic</span>. links: - title: Manage Custom Forms href: /scp/forms.php priority: title: प्राथमिकता content: > Select the Priority assigned to new tickets related to this <span class="doc-desc-title">Help Topic</span>. <br><br> Ticket Filters can override new ticket Priority. department: title: विभाग content: > Choose Department to which new tickets under this Help Topic will be routed. links: - title: विभागों को प्रबंधित करें href: /scp/departments.php sla_plan: title: SLA योजना content: > Choose SLA plan associated with this <span class="doc-desc-title">Help Topic</span>. <br><br> This selection will override any selected Department's SLA plan links: - title: SLA योजनाओं का प्रबंधन href: /scp/slas.php thank_you_page: title: Thank-You Page content: > Choose the Thank-You Page to which a User is directed after opening a Ticket under this <span class="doc-desc-title">Help Topic</span>. links: - title: Manage Thank-You Pages href: /scp/pages.php auto_assign_to: title: Auto-assign New Tickets content: > Optionally choose an Agent or Team to auto-assign tickets opened with this <span class="doc-desc-title">Help Topic</span> <br><br> Ticket Filters can override assignment. links: - title: Manage Staff and Teams href: /scp/staff.php ticket_auto_response: title: Ticket Auto-response content: > If checked, the setting will disable new ticket auto-responses for this <span class="doc-desc-title">Help Topic</span>. <br><br> This overrides the autoresponder setting for the <span class="doc-desc-title">Department</span> as well as global <span class="doc-desc-title">Autoresponder settings</span>. links: - title: Autoresponder Settings href: /scp/settings.php?t=autoresp custom_numbers: title: Custom Ticket Numbers content: > Choose "Custom" here to override the system default ticket numbering format for tickets created in this help topic. See the help tips on the Settings / Tickets page for more details on the settings. #This is popup help messages for the Admin Panel -> Manage -> Pages #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- site_pages: title: Site Pages content: > Site pages can serve as a mini Content Management System (CMS). You can define multiple landing, offline, and thank-you pages and configure them in the company settings and help topics. links: - title: Company Settings href: /scp/settings.php?t=pages type: title: Type content: > <span class="doc-desc-opt">Offline</span> pages are displayed on the client portal if your help desk is disabled. <span class="doc-desc-opt">Landing</span> pages are displayed on the home page of your client portal. <span class="doc-desc-opt">Thank You</span> pages are displayed after a user submits a ticket. <span class="doc-desc-opt">Other</span> pages can be used as a simple content management system (CMS). #This is popup help messages for the Admin Panel -> Manage -> Schedules #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- schedule: title: Schedule Definition content: > <b>Name</b>: Unique name for the schedule. <hr> <b>Type</b>: Choose the type of Schedule. <span class="doc-desc-title">Business Hours</span> defines the hours that are included when calculating SLA hours, whereas <span class="doc-desc-title">Holiday Hours</span> define hours that are excluded. <hr> <b>Timezone</b>: Choose the time zone for the schedule. It's recommended that you leave it empty for a <span class="doc-desc-title">Floating</span> time zone. <br><br> Floating time zone allows for times to be relative to the effective time zone at the time of use. #This is popup help messages for the Admin Panel -> Manage -> SLA Plan #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- name: title: नाम content: > Choose a discriptive name for this <span class="doc-desc-title">SLA Plan</span> that will reflect its purpose. grace_period: title: Grace Period content: > Determine the number of hours after a ticket is created that it will be automatically marked as overdue. <br><br> Hours are counted during the specified Schedule. The hierarchy is Department Schedule, SLA Schedule, then System Default Schedule. If no Schedule is configured, the Hours are counted 24/7 (even after business hours) until the Ticket is Overdue. transient: title: Transient content: > Transient SLAs are considered temporary and can be overridden by a non-transient SLA on <span class="doc-desc-opt">Department</span> transfer or when its <span class="doc-desc-title">Help Topic</span> is changed. schedule: title: Schedule content: > Choose the Schedule to be used by this SLA when rendering tickets Overdue. <br><br> Please note that Department settings can override this schedule. links: - title: Manage Schedules href: /scp/schedules.php #This is the view / management page for an organization in the user #directory #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- org_sharing: title: Ticket Sharing content: > <p> संस्थागत टिकट का सहभाजन संस्था के किसी सदस्य द्वारा अपने टिकट को संस्था के दुसरे सदस्यो को सहभाजन की अनुमति प्रदान करता है। </p> <p class="info-banner"> <i class="icon-info-sign"></i> संस्था के सहकर्मी टिकटों का हमेशा सहभाजन कर सकते है। </p> email_domain: title: Email Domain content: > उपयोगकर्ता अपने email domain(s) के आधार पर इस संस्था में स्वत: ही सम्मिलित किये जा सकते है। निम्न box के उपयोग से एक या अधिक अल्प विराम से विभाजित domains प्रविष्टि करें। उदाहरणार्थ: ऎसे email addresses जिसके अन्त में @mycompany.com आते है के लिए <code>mycompany.com</code> प्रविष्ट करें। #This is popup help messages for the Admin Panel -> Settings -> Agents #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. #General Settings --- agent_name_format: title: प्रतिनिधि का नाम स्वरूपण content: > सिस्टम में कार्यकर्ताओ के नामकरण के लिये प्रारूप का निर्धारण करें। यदि प्रारूप का निर्धारण नही किया गया है तो Email templates का उपयोग कर लिया जायेगा। staff_identity_masking: title: Staff Identity Masking content: > If enabled, this will hide the Agent’s name from the Client during any communication. disable_agent_collabs: title: Disable Agent Collaborators content: > If Enabled, Agents that are added as Collaborators by Users will be automatically Disabled. This is helpful when Users are blindly adding Agents to the CC field causing the Agents to receive all of the Participant Alerts. <br><br> <strong>Note:</strong> <br> This setting is global for all User created Tickets via API, Piping, and Fetching. #Authentication settings agent_password_policy: title: Password Management Policy content: > Chose a <span class="doc-desc-title">Password Policy</span> for <span class="doc-desc-title">Agents</span>. <br><br> Additional policies can be added by installing <span class="doc-desc-title">Password Policy</span> plugins. allow_password_resets: title: Allow Password Resets content: > यदि आप गलत पासवर्ड के उपयोग से लागिन नही कर पाए और <span class="doc-desc-title">अपना नया पासवर्ड बनाए</span> का लिंक <span class="doc-desc-title">कर्मचारी लागिन पेज मे</span> चाहते है तो इस विकल्प का चुनाव करें। reset_token_expiration: title: Password Reset Window content: > Choose the duration (in minutes) for which the <span class="doc-desc-title"> Password Reset Tokens</span> will be valid. When an Agent requests a <span class="doc-desc-title">Password Reset</span>, they are emailed a token that will permit the reset to take place. staff_session_timeout: title: Agent Session Timeout content: > कार्यकर्ता के लागिन के उपरांत अधिकतम समय (मिनट में) का निर्धारण करें जिसके उपरांत कार्यकर्ता को पुन: लागिन की आवस्यकता होगी।<br><br> यदि आप <span class="doc-desc-title">कार्यकर्ता सत्र समय समाप्ति</span> निर्धारण नही चाहते तो 0 प्रविष्टि करें। bind_staff_session_to_ip: title: Bind Agent Session to IP content: > कार्यकर्ता द्वारा किसी IP से लागिन किये जाने को बनाए रखने के लिए इस विकल्प का चुनाव करें।<br><br> dynamic IP addresses वाले उपयोगकर्ताओ को इस विकल्प का चुनाव नही करने की सिफारिश की जाती है। require_agent_2fa: title: Require Two Factor Authentication content: > Enable this feature if you would like to have an extra layer of authentication set up for Agents when they log into the helpdesk. Once they correctly submit their username and password, they will be required to submit a token to finish logging into the helpdesk. #This is popup help messages for the Account Panel -> #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- page_title: title: Alerts and Notices content: > Alerts and Notices are automated email notifications sent to Agents when various ticket events are triggered. ticket_alert: title: नया टिकट अधिसूचना content: > <p> Alert sent out to Agents when a new ticket is created. </p><p class="info-banner"> <i class="icon-info-sign"></i> This alert is not sent out if the ticket is auto-assigned via a Ticket Filter or Help Topic. </p> links: - title: Default New Ticket Alert Template href: /scp/templates.php?default_for=ticket.alert message_alert: title: नया संदेश सूचना content: > Alert sent out to Agents when a new message from the User is appended to an existing ticket. links: - title: Default New Message Alert Template href: /scp/templates.php?default_for=message.alert internal_note_alert: title: New Internal Activity Alert content: > Alert sent out to Agents when internal activity such as an internal note or an agent reply is appended to a ticket. links: - title: Default Ticket Activity Template href: /scp/templates.php?default_for=note.alert assignment_alert: title: Ticket Assignment Alert content: > Alert sent out to Agents on ticket assignment. links: - title: Default Ticket Assignment Alert Template href: /scp/templates.php?default_for=assigned.alert transfer_alert: title: Ticket Transfer Alert content: > Alert sent out to Agents on ticket transfer between Departments. links: - title: Default Ticket Transfer Alert Template href: /scp/templates.php?default_for=transfer.alert overdue_alert: title: Overdue Ticket Alert content: > Alert sent out to Agents when a ticket becomes overdue based on SLA or Due Date. links: - title: Default Stale Ticket Alert Template href: /scp/templates.php?default_for=ticket.overdue - title: Manage SLAs href: /scp/slas.php system_alerts: title: System Alerts content: > Significant system events that are sent out to the Administrator (%{config.admin_email}). Depending on the configured <span class="doc-desc-title">Log Level</span>, the events are also made available in the <span class="doc-desc-title">System Logs</span> links: - title: View System Logs href: /scp/logs.php - title: Change Admin Email href: /scp/settings.php?t=emails #This is popup help messages for the Admin Panel -> Settings -> Autoresponder #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- new_ticket: title: New Ticket content: > Enable this if you want an autoresponse to be sent to the User on new ticket. links: - title: New Ticket Autoresponse Template href: /scp/templates.php?default_for=ticket.autoresp new_ticket_by_staff: title: New Ticket by Staff content: > Notice sent when an Agent creates a ticket on behalf of the User. <em>Agent can override this when creating new tickets.</em> links: - title: New Ticket Notice Template href: /scp/templates.php?default_for=ticket.notice new_message_for_submitter: title: New Message Confirmation content: > Confirmation notice sent when a new message is appended to an existing ticket. links: - title: New Message Confirmation Template href: /scp/templates.php?default_for=message.autoresp new_message_for_participants: title: New Message Notice content: > Broadcast messages received from message submitter to all other participants on the ticket. links: - title: New Activity Notice Template href: /scp/templates.php?default_for=ticket.activity.notice overlimit_notice: title: Overlimit Notice content: > Ticket denied notice sent to User on <span class="doc-desc-title">Maximum Open Tickets</span> violation. links: - title: Overlimit Notice Template href: /scp/templates.php?default_for=ticket.overlimit - title: Set <em>Maximum Open Tickets</em> href: /scp/settings.php?t=tickets #This is popup help messages for the Admin Panel -> Settings -> Emails #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- default_email_templates: title: Default Email Template Set content: > Select <span class="doc-desc-title">Email Template Set</span> used to send <span class="doc-desc-title">Auto-Responses</span> and <span class="doc-desc-title">Alerts</span> for various actions that can take place during a Ticket’s lifetime. <br><br> Departments can be assigned a specific Email Template Set. links: - title: Manage Email Template Sets href: /scp/templates.php default_system_email: title: Default Outgoing Email content: > Choose an email address from which outgoing emails are sent. <br><br> <span class="doc-desc-title">Department</span> can set its own <span class="doc-desc-title">email address</span> which will override what is set here. links: - title: Manage Email Addresses href: /scp/emails.php default_alert_email: title: Default Alert Email content: > Choose an email address from which <span class="doc-desc-title">Alerts & Notices</span> are sent to Agents. links: - title: Manage Email Addresses href: /scp/emails.php admins_email_address: title: Admin’s Email Address content: > Enter an adminstrator's email address to which <span class="doc-desc-title">System Errors</span> and <span class="doc-desc-title">New Ticket Alerts</span> (if enabled) are sent. links: - title: Manage Alerts & Notices href: /scp/settings.php?t=alerts email_fetching: title: Email Fetching content: > Allow IMAP/POP polling for configured and enabled <span class="doc-desc-title">Mail Boxes</span>. links: - title: Manage Mail Boxes href: /scp/emails.php enable_autocron_fetch: title: Fetch Emails using Auto-cron content: > Enables periodic email fetching using an internal task manager triggered by Agents' activity. <br><br> Please note that emails will not be fetched if no one is logged in to Staff Control Panel. External task scheduler is highly recommended for predictable fetch intervals. links: - title: Using External Task Scheduler href: https://docs.osticket.com/en/latest/Getting%20Started/POP3-IMAP%20Settings.html strip_quoted_reply: title: Strip Quoted Reply content: > If enabled, this will remove preceding correspondence between email communications. <br><br> This feature is relationally dependent on the <span class="doc-desc-title">Reply Separator Tag</span> below. reply_separator_tag: title: Reply Separator Tag content: > This is a token indicating to the User to reply above the line. <br><br> <strong>Note:</strong> this is only relevant if <span class="doc-desc-title">Strip Quoted Reply</span> is enabled above. emailed_tickets_priority: title: Emailed Tickets Priority content: > Choose whether you would like the priority/importance option of the User's email (e.g. OutLook) to dictate the new ticket’s priority. <br><br> This setting can be overridden by a <span class="doc-desc-title">Ticket Filter</span>. links: - title: Create & Manage Ticket Filters href: /scp/filters.php accept_all_emails: title: Accept All Emails content: > Accept emails from unknown Users. <br><br> Unchecking this setting will result in tickets getting rejected. accept_email_collaborators: title: Accept Email Collaborators content: > Add email participants included in the <code><strong>To</strong></code> and <code><strong>CC</strong></code> fields as ticket collaborators. <br /><br /> <em>Collaborators can always be added manually by Agents when viewing a ticket.</em> default_mta: title: Default MTA content: > <span class="doc-desc-title">Default MTA</span> takes care of email delivery process for outgoing emails without SMTP setting. ticket_response_files: title: Ticket Response Files content: > If enabled, any attachments an Agent may attach to a ticket response will be also included in the email to the User. verify_email_addrs: title: Verify Email Addresses content: > Enable this option to check if the email address has a mail exchanger (MX) in the domain's DNS. This is useful to detect incorrectly typed email addresses. This is performed in addition to checking the email address wellformedness. #This is popup help messages for the Admin Panel -> Settings -> Knowledgebase #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- knowledge_base_settings: title: ज्ञानकोश सेटिंग content: > knowledge_base_status: title: ज्ञानकोश स्थिति content: > Enable this setting to allow your users self-service access to your public knowledge base articles. <br><br> Knowledge base categories and FAQs can be made internal (viewable only by Agents). links: - title: ज्ञानकोष प्रबंधन href: /scp/kb.php restrict_kb: title: Restrict Access to the Knowledge Base content: > Enable this setting to prevent unregistered users from accessing your knowledge base articles on the client interface. links: - title: Access Control Settings href: /scp/settings.php?t=users canned_responses: title: पूर्व आरक्षित प्रतिक्रियाएँ content: > Enable this setting to allow Agents to use <span class="doc-desc-title">Canned Responses</span> when replying to tickets. links: - title: Manage Canned Responses href: /scp/canned.php #This is popup help messages for the Account Panel -> #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- company_information: title: कंपनी की जानकारी content: > This refers to the company or organization that will benefit from osTicket’s software and its support staff. The information here will appear in email signatures (i.e., the footer) when tickets are responded to by agents. links: - title: Company Information Form href: /scp/forms.php?type=C landing_page: title: Landing Page content: > The <span class="doc-desc-title">Landing Page</span> is displayed on the front page of your support site. offline_page: title: Offline Page content: > The <span class="doc-desc-title">Offline Page</span> is displayed in the support site when the help desk is offline, see Admin Panel -> Setting -> System -> Helpdesk Status. default_thank_you_page: title: Default Thank-You Page content: > The <span class="doc-desc-title">thank-you page</span> is displayed to the customer when a <span class="doc-desc-title">Client</span> submits a new ticket. <br/><br/> <span class="doc-desc-title">Thank you</span> pages can be associated with help topics. logos: title: Logos content: > You may customize the <span class="doc-desc-title">Logo</span> that will be displayed to the Client in the Client Portal (i.e., your Support Site). upload_a_new_logo: title: Upload a new logo content: > Choose an image in the .gif, .jpg or .png formats. We will proportionally resize the display of your image. We will not, however, resize the image’s data. Therefore, to speed load times, it is recommended that you keep your image close to the default image size (817px × 170px). backdrops: title: पृष्ठभूमि content: > कर्मचारियों के लागिन पृष्ठ हेतु <span class="doc-desc-title">पृष्ठभूमि</span> में बदलाव हेतु पृष्ठभूमि का चुनाव कर सकते है। upload_a_new_backdrop: title: नया पृष्ठभूमि अपलोड करे। content: > .gif, .jpg अथवा .png प्रारूप में चित्र का चुनाव करें। हम आपके चित्र के जानकारी को बिना परिवर्तन किये सिर्फ आकार को आनुपातिक रूप में कर लेंगे। अत: आपसे सिफारिश किया जाता है कि आप ऎसे चित्र का चुनाव करें जिनका आकार कम से कम हो (1 मेगाबाईट के अंदर)। ये भी याद रखे कि इसमे PHP max upload की सेटिंग भि लागू होगी। #This is popup help messages for the Admin Panel -> Settings -> System #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- helpdesk_status: title: Helpdesk Status content: > If the status is changed to <span class="doc-desc-opt">Offline</span>, the client interface will be disabled. Only Admins will be able to access the system. helpdesk_url: title: Helpdesk URL content: > This URL is the base of your osTicket installation. It is used in email communication to direct end-users back to your helpdesk. helpdesk_name_title: title: Helpdesk Name/Title content: > This is the title that appears in the browser tab. If your help desk page is bookmarked, this will be the title/name of the site page. default_department: title: Default Department content: > Choose a default <span class="doc-desc-title">department</span> for tickets that are not automatically routed to a department. <br/><br/> Ticket can be routed base on help topic, incoming email and ticket filter settings. default_schedule: title: Default Schedule content: > Choose the default Schedule to be used by SLA when rendering tickets Overdue. links: - title: Manage Schedules href: /scp/schedules.php force_https: title: Force HTTPS content: > This setting allows Admins to configure wether or not they want to Force HTTPS system-wide. If enabled, any request that is using the HTTP protocol will be redirected to the HTTPS protocol. Note, this will only work if you have an SSL certificate installed and have HTTPS configured on the server. <br/><br/> <b>Note:</b><rb/> This might affect remote piping scripts. Reference new scripts included in <code>setup/scripts/</code> for updates. default_page_size: title: Default Page Size content: > Choose the number of items shown per page in the Ticket Queues in the Staff Panel. Each Agent can also customize this number for their own account under <span class="doc-desc-title">My Preferences</span>. default_log_level: title: Default Log Level content: > Determine the minimum level of issues which will be recorded in the <span class="doc-desc-title">system log</span>. <span class="doc-desc-opt">Debug</span> represents the least severity, and <span class="doc-desc-opt">Error</span> represents the greatest severity. For example, if you want to see all issues in the <span class="doc-desc-title">System Logs</span>, choose <span class="doc-desc-opt">Debug</span>. purge_logs: title: Purge Logs content: > Determine how long you would like to keep <span class="doc-desc-title">System Logs</span> before they are deleted. enable_richtext: title: Enable Rich Text content: > If enabled, this will permit the use of rich text formatting between Clients and Agents. enable_avatars: title: वार्तालाप में अवतार का दिखना निर्धारित करे। content: > संवाद अथवा वार्तालाप में <span class="doc-desc-title">अवतार</span> को दिखाने हेतु इसका चुनाव करें। <br><br> <span class="doc-desc-title">अवतार</span> का चुनाव कर्मचारियों अथवा उपयोगकर्ताओ के सेटिंग पृष्ठ से किया जा सकता है। links: - title: Agents Settings href: /scp/settings.php?t=agents - title: Users Settings href: /scp/settings.php?t=users collision_avoidance: title: Agent Collision Avoidance content: > Enter the maximum length of time an Agent is allowed to hold a lock on a ticket or task without any activity. <br><br> Enter <span class="doc-desc-opt">0</span> to disable the lockout feature. allow_iframes: title: Allow System iFrame content: > Enter comma separated list of urls/domains for the system to be framed in. If left empty, the system will default to 'self'. This accepts domain wildcards, HTTP/HTTPS URL scheme, and port numbers. <br><br> <b>Example:</b> <br> https://domain.tld, sub.domain.tld:443, http://*.domain.tld links: - title: Syntax Information (host-source) href: "https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors#Sources" acl: title: ACL (Access Control List) content: > Enter a comma separated list of IP addresses to allow access to the system. There are four options to choose which panel(s) to apply the ACL to. <table border="1" cellpadding="2px" cellspacing="0" style="margin-top:7px" ><tbody style="vertical-align:top;"> <tr><th>Apply To</th> <th>Description</th></tr> <tr><td>Disabled</td> <td>Disables ACL altogether.</td></tr> <tr><td>All</td> <td>Applies ACL to all Panels. (ie. Client Portal, Staff Panel, Admin Panel)</td></tr> <tr><td>Client Portal</td> <td>Applies ACL to only Client Portal.</td></tr> <tr><td>Staff Panel</td> <td>Applies ACL to only Staff Panel and Admin Panel.</td></tr> </tbody></table> embedded_domain_whitelist: title: Embedded Domain Whitelist content: > Enter a comma separated list of domains to be whitelisted for iFrames used in the system. Do not input <code>http(s)</code> or <code>www</code> with the domain; only the domain name will be accepted. This is used when you would like to embed content in the system (eg. YouTube video) via Client Portal, Knowledgebase, etc. If you add an iFrame with a non-whitelisted domain, the system will remove the iFrame automatically. By default the system allows YouTube, Vimeo, DailyMotion, and Microsoft Stream. <br><br> <b>Example:</b> <br> domain.tld, sub.domain.tld #Date and time options date_time_options: title: Date & Time Options content: > The following settings define the default settings for Date & Time settings for the help desk. You can choose to use the locale defaults for the selected locale or use customize the formats to meet your unique requirements. Refer to the ICU format strings as a reference for customization. The dates shown below simply illustrate the result of their corresponding values. links: - title: See the ICU Date Formatting Table href: http://userguide.icu-project.org/formatparse/datetime languages: title: System Languages content: > Choose a system primary language and optionally secondary languages to make your interface feel localized for your agents and end-users. primary_language: title: सिस्टम के लिए मूल भाषा का चुनाव करें। content: > Content of this language is displayed to agents and end-users if their respective language preference is not currently available. This includes the content of the interface, as well as, custom content such as thank-you pages and email messages. <br/><br/> This is the language in which the untranslated versions of your content should be written. secondary_language: title: Secondary Languages content: > Select language preference options for your agents and end-users. The interface will be available in these languages, and custom content, such as thank-you pages and help topic names, will be translatable to these languages. #Attachments attachments: title: Attachment Settings and Storage content: > संलग्नकॊ को भण्डारित किये जाने की प्रक्रिया निर्धारित करे। default_storage_bk: title: File Storage Backend content: > Choose how attachments are stored. <br><br> Additional storage backends can be added by installing storage plugins max_file_size: title: Maximum File Size content: > कार्यकर्ताओ द्वारा अपलोड हेतु अधिकतम आकार का संलग्नक फाईल का चुनाव करे। संलग्नक के रूप में स्कॆन किया फाईल, ज्ञानकोश आलेख और टिकट एवं कार्यो की उत्तर सम्मिलित कर सकते है। संलग्नक फाईल के आकार की अधिकतम सीमा PHP के सेटिंग <code>upload_max_filesize</code> द्वारा निर्धारित की जाएगी। links: - title: PHP ini की सेटिंग href: "http://php.net/manual/en/ini.core.php#ini.upload-max-filesize" files_req_auth: title: Require Login content: > Enable this setting to forbid serving attachments to unauthenticated users. That is, users must sign into the system (both end users and agents), in order to view attachments. <br><br> From a security perspective, be aware that the user's browser may retain previously-viewed files in its cache. Furthermore, all file links on your helpdesk automatically expire after about 24 hours. #This is popup help messages for the Admin Panel -> Settings -> Tasks #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- number_format: title: कार्यो के संख्या का प्रारूप content: > यह सेटिंग कार्य संख्या बनाने हेतु उपयोग की जायेगी। कार्य संख्या में जितना अंक उपयोग करना है उतने हैस ('#') निशान लगाए। कोइ अन्य निशान संख्या प्रारूप में यथावत रख लिया जायेगा। <br/><br/> उदाहरणार्थ: 6-अंको का कार्य संख्या बनाने हेतु <code>######</code> प्रविष्टि करें। sequence_id: title: कार्य संख्या का अनुक्रम content: > नये कार्य संख्याओं को प्राप्त करने हेतु अनुक्रम का चुनाव करें। सिस्टम में पूर्व से ही एक बढ़ते क्रम का अनुक्रम और क्रमरहित (random) अनुक्रम विद्यमान है। आप सुविधानुसार नये अनुक्रमों का निर्माण कर सकते है। default_sla: title: पूर्वनिर्धारित सेवा स्तर समझौता content: > Choose the default Service Level Agreement to manage how long a task can remain Open before it is rendered Overdue. links: - title: Create more SLA Plans href: /scp/slas.php default_priority: title: Default Priority content: > Choose a default <span class="doc-desc-title">priority</span> for tasks not assigned a priority automatically. task_attachment_settings: title: Task Thread Attachments content: > Configure settings for files attached to the <span class="doc-desc-title">description</span> field. These settings are used for all new tasks and new messages regardless of the source channel (web portal, email, api, etc.). page_title: title: Alerts and Notices content: > Alerts and Notices are automated email notifications sent to Agents when various task events are triggered. task_alert: title: New Task Alert content: > <p> Alert sent out to Agents when a new task is created. </p><p class="info-banner"> <i class="icon-info-sign"></i> This alert is not sent out if the task is auto-assigned. </p> links: - title: Default New Task Alert Template href: /scp/templates.php?default_for=task.alert activity_alert: title: New Activity Alert content: > Alert sent out to Agents when a new message is appended to an existing task. links: - title: Default New Activity Alert Template href: /scp/templates.php?default_for=task.activity.alert assignment_alert: title: Task Assignment Alert content: > Alert sent out to Agents on task assignment. links: - title: Default Task Assignment Alert Template href: /scp/templates.php?default_for=task.assignment.alert transfer_alert: title: Task Transfer Alert content: > Alert sent out to Agents on task transfer between Departments. links: - title: Default Task Transfer Alert Template href: /scp/templates.php?default_for=task.transfer.alert overdue_alert: title: Overdue Task Alert content: > Alert sent out to Agents when a task becomes overdue based on SLA or Due Date. links: - title: Default Stale Task Alert Template href: /scp/templates.php?default_for=task.overdue.alert - title: Manage SLAs href: /scp/slas.php #This is popup help messages for the Admin Panel -> Settings -> Tickets #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- number_format: title: Ticket Number Format content: > This setting is used to generate ticket numbers. Use hash signs (`#`) where digits are to be placed. Any other text in the number format will be preserved. <span class="doc-desc-title">Help Topics</span> can define custom number formats. <br/><br/> For example, for six-digit numbers, use <code>######</code>. sequence_id: title: Ticket Number Sequence content: > Choose a sequence from which to derive new ticket numbers. The system has a incrementing sequence and a random sequence by default. You may create as many sequences as you wish. Use various sequences in the <span class="doc-desc-title">Ticket Number Format</span> configuration for help topics. queue_bucket_counts: title: Top-Level Ticket Counts content: > This setting is used to hide or show the ticket counts on Main-Level queues. Get back to the way things used to be. default_ticket_status: title: Default Status for new Tickets content: > Choose a status as the default for new tickets. This can be defined for each help topic, if desired. It can also be overridden by a ticket filter. links: - title: Manage Ticket Statuses href: /scp/lists.php?type=ticket-status default_sla: title: पूर्वनिर्धारित सेवा स्तर समझौता content: > Choose the default Service Level Agreement to manage how long a ticket can remain Open before it is rendered Overdue. links: - title: Create more SLA Plans href: /scp/slas.php default_ticket_queue: title: Default Ticket Queue content: > Setting to determine the default queue for Agents upon log-in. Agents can also set their default queue in their Profile tab to override this setting. default_priority: title: Default Priority content: > Choose a default <span class="doc-desc-title">priority</span> for tickets not assigned a priority automatically. <br/><br/> Priority can be assigned via the help topic, routed department, or ticket filter settings. maximum_open_tickets: title: Maximum Open Tickets content: > Enter the maximum <em>number</em> of tickets a User is permitted to have <strong>open</strong> in your help desk. <br><br> Enter <span class="doc-desc-opt">0 </span> if you prefer to disable this limitation. email_ticket_priority: title: Email Ticket Priority content: > Use email priority assigned by addressee’s mail service show_related_tickets: title: Show Related Tickets content: > Show all related tickets on user login - otherwise access is restricted to one ticket view per login human_verification: title: Human Verification content: > Enable CAPTCHA on the Client Portal to verify an incoming ticket is the result of human activity. <br><br> Requires GDLib library claim_tickets: title: Claim Tickets on Response content: > Enable this to auto-assign unassigned tickets to the responding Agent. <br><br> Reopened tickets are always assigned to the last respondent unless auto assign on reopen is disabled on the Department level. auto_refer: title: Auto-refer Tickets on Close content: > Enable this to auto-refer tickets to the assigned or closing Agent when a ticket is closed. <br><br> This is necessary when you want to give agents with limited access continued access to assigned tickets after they're closed. collaborator_ticket_visibility: title: Collaborator Tickets Visibility content: > If Enabled, Users will have visibility to ALL Tickets they participate in when signing into the Web Portal. <br><br> If Disabled, Users will only be able to see their own Tickets when signing into the Web Portal. require_topic_to_close: title: Require Help Topic to Close content: > If Enabled, a Ticket must have a Help Topic in order to be Closed by an Agent allow_external_images: title: Allow External Images content: > If Enabled, the system will allow external inline images that have a valid image extension (.png, .jpg, .jpeg, .gif). If Disabled, the system will exclude any external inline images. One caveat to note, is if the setting is Disabled we will still store external inline images that have a valid image extension in case the setting is re-enabled in the future. assigned_tickets: title: Assigned Tickets content: > Enable this feature to exclude assigned tickets from the <span class="doc-desc-title">Open Tickets Queue</span>. answered_tickets: title: Answered Tickets content: > Enable this feature to show answered tickets in the <span class="doc-desc-title">Answered Tickets Queue</span>. Otherwise, it will be included in the <span class="doc-desc-title">Open Tickets Queue</span>. ticket_attachment_settings: title: Ticket Thread Attachments content: > Configure settings for files attached to the <span class="doc-desc-title">issue details</span> field. These settings are used for all new tickets and new messages regardless of the source channel (web portal, email, api, etc.). #This is popup help messages for the Admin Panel -> Settings -> Users #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. #General Settings --- client_name_format: title: प्रतिनिधि का नाम स्वरूपण content: > Choose a format for Users names throughout the system. Email templates will use it for names if no other format is specified. #Authentication settings client_password_policy: title: Password Management Policy content: > Chose a <span class="doc-desc-title">Password Policy</span> for <span class="doc-desc-title">Users</span>. <br><br> Additional policies can be added by installing <span class="doc-desc-title">Password Policy</span> plugins. client_session_timeout: title: User Session Timeout content: > Choose the maximum idle time (in minutes) before a User is required to log in again. <br><br> If you would like to disable <span class="doc-desc-title">User Session Timeouts,</span> enter 0. registration_method: title: Registration Options content: > <span class="doc-desc-title">Registration Method</span> and <span class="doc-desc-title">Registration Required</span> are used together to configure how users register and access the web portal of your help desk. The table below summarizes how the two settings are interpreted by the system. <table border="1" cellpadding="2px" cellspacing="0" style="margin-top:7px" ><tbody style="vertical-align:top;"> <tr><th>Registration Required</th> <th>Registration Method</th> <th>Result</th></tr> <tr><td>No</td><td>Public</td> <td>Registration encouraged but not required for new tickets.</td></tr> <tr><td>Yes</td><td>Public</td> <td>Registration and login are required for new tickets</td></tr> <tr><td>No</td><td>Private</td> <td>Anyone can create a ticket, but only agents can register accounts</td></tr> <tr><td>Yes</td><td>Private</td> <td>User access is by invitation only</td></tr> <tr><td>No</td><td>Disabled</td> <td>No one can register for an account, but anyone can create a ticket. <em>This was how osTicket functioned prior to 1.9</em></td></tr> <tr><td>Yes</td><td>Disabled</td> <td>Disable new tickets via web portal</td></tr> </tbody></table> client_verify_email: title: Require Email Verification content: > Disable this option to give your users immediate access to tickets via the "Check Ticket Status" login page in the client portal. If enabled, (which is the default), users will be required to receive an email and follow a link in the email to view the ticket. <br><br> Disabling email verification might allow third-parties (e.g. ticket collaborators) to impersonate the ticket owner. allow_auth_tokens: title: Enable Authentication Tokens content: > Enable this option to allow use of authentication tokens to auto-login users on ticket link click. #This is popup help messages for the Admin Panel -> Staff -> Add Staff Form #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- username: title: उपयोगकर्ता का नाम content: > Please choose an Agent <span class="doc-desc-title">username</span> that is unique to your <span class="doc-desc-title">Help Desk</span>. reset2fa: title: Reset Two Factor Authentication content: > In the event that an Agent loses the ability to log into the helpdesk using their current 2FA configuration, an Admin can reset the Agent's 2FA configuration so that they can reconfigure it upon their next successful login. email_address: title: ईमेल पता content: > Enter Agent's email that will receive <span class="doc-desc-title">Alerts & Notices</span> from the <span class="doc-desc-title">Help Desk</span>. 0: <br><br> 1: Staff can sign in into the staff control panel with either username or email address. welcome_email: title: स्वागत ईमेल content: > Send the new Agent an account access link from which the Agent will be able to set thier own password. If unchecked, you will need to set password and communicate the log-in information to the new staff. account_password: title: खाते का पासवर्ड content: > As an <span class="doc-desc-title">administrator</span>, you may change an Agent’s password. forced_password_change: title: Forced Password Change content: > Enable this if you would like to force the new Agent to change their own password upon next log-in. agents_signature: title: Agent’s Signature content: > Create a signature for the Agent which can be selected when replying to a ticket. account_status: title: खाते की स्थिति content: > If the Agent's status is <span class="doc-desc-opt">Locked</span>, they will not be able to sign in to the help desk. assigned_group: title: Assigned Group content: > The <span class="doc-desc-title">Group</span> that you choose for this Agent to belong will determine what permissions the Agent has within the <span class="doc-desc-title">Help Desk</span>. links: - title: Manage Groups href: /scp/groups.php primary_department: title: Primary Department content: > Choose the primary <span class="doc-desc-title">department</span> to which this Agent belongs and an effective <span class="doc-desc-title">Role</span>. links: - title: विभागों को प्रबंधित करें href: /scp/departments.php primary_role: title: Primary Role content: > Choose the primary <span class="doc-desc-title">role</span> to which this agent belongs. primary_role_on_assign: title: कार्य के लिए प्राथमिक भूमिका का प्रयोग करें content: > Enable this to fallback to the <span class="doc-desc-title">primary role</span> when this agent is assigned tickets and tasks outside of the <span class="doc-desc-title">primary department</span> and <span class="doc-desc-title">extended access</span> departments. Otherwise the agent will have view only access. daylight_saving: title: Daylight Saving content: > Enable this feature if you would like Daylight Saving to automatically come into play for this Agent’s time zone. limited_access: title: Limited Access content: > If enabled, the Agent will only have access to tickets assigned directly or via the Team. directory_listing: title: Directory Listing content: > Enable this if you would like to list this Agent in the <span class="doc-desc-title">Staff Directory</span>. links: - title: Visit the Staff Directory href: /scp/directory.php vacation_mode: title: Vacation Mode content: > If you change the Agent’s status to <span class="doc-desc-opt">Vacation Mode</span>, the Agent will not receive any <span class="doc-desc-title">Alerts & Notices</span> nor be available for tickets assignment. #This is popup help messages for the Account Panel -> Agents -> Agents #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template.#This is popup help messages for the Admin Panel -> Staff -> Add New Department -> Department Form #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- status: title: Status content: > If disabled or archived, this <span class="doc-desc-title">Department</span> will not be available. type: title: Type content: > Select <span class="doc-desc-opt">Private</span> if you wish to mask assignments to this Department in the Client Portal. Additionally, when labeled as <span class="doc-desc-opt">Private</span>, the <span class="doc-desc-title">Department Signature</span> will not be displayed in email replies. <br/><br/> At least one department must be <span class="doc-desc-opt">Public</span> email: title: Email content: > Email Address used when responses are sent to Users when Agents post Responses to Tickets. template: title: Template Set content: > Email <span class="doc-desc-title">Template Set</span> used for Auto-Responses and Alerts & Notices for tickets routed to this Department. links: - title: टेम्पलेट प्रबंधन href: /scp/templates.php sla: title: सेवा स्तर समझौता content: > Service Level Agreement for tickets routed to this Department. links: - title: SLA योजनाओं का प्रबंधन href: /scp/slas.php schedule: title: Schedule content: > Schedule used by SLA when rendering tickets, routed to this Department, Overdue. <br><br> This setting takes precedence over System and SLA schedule settings. links: - title: Manage Schedules href: /scp/schedules.php manager: title: विभाग प्रबंधक content: > Select a <span class="doc-desc-title">Manager</span> for this department. <br/><br/> Managers can be configured to receive special alerts and also have the right to unassign tickets. links: - title: Manage Alerts & Notices href: /scp/settings.php?t=alerts group_membership: title: Alerts & Notices Recipients content: > Select the recipients of configured <span class="doc-desc-title">Alerts & Notices</span>. links: - title: Configure Alerts & Notices href: "/scp/settings.php?t=tickets#alerts" sandboxing: title: Ticket Assignment Restrictions content: > Determine if Tickets can be assigned to all agents, agents with Primary or Extended Department access, or only agents with Primary Department access. disable_auto_claim: title: Disable Auto Claim content: > Check this to <strong>disable</strong> auto-claim on response/reply for this department. <br><br> Agents can still manually claim unassigned tickets disable_reopen_auto_assign: title: Disable Auto Assign on Reopen content: > Check this to <strong>disable</strong> auto-assignment of reopened tickets for this department. <br><br> Otherwise, the Ticket will be auto assigned to the last responding Agent auto_response_settings: title: Autoresponder Settings content: > This allows you to override the global Autoresponder settings for this Department. new_ticket: title: New Ticket Auto-Response content: > You may disable the Auto-Response sent to the User when a new ticket is created and routed to this Department. new_message: title: New Message Auto-Response content: > You may disable the Auto-Response sent to the User to confirm a newly posted message for tickets in this Department. auto_response_email: title: Auto Response Email content: > Select an email address from which Auto-Responses are sent for this Department. department_access: title: Group Access content: > Allow Agents of other Departments access to this Deparmtent's tickets. department_signature: title: Department Signature content: > Signature is made available as a choice, for <span class="doc-desc-opt">Public</span> Departments, on Agent Responses. #This is popup help messages for the Admin Panel -> Staff -> Departments #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- type: title: Type content: > If the Department’s Type is Private, then the Department Signature will not be available on response nor will the department assignment show from the Client Portal. dept_manager: title: विभाग प्रबंधक content: > You may choose an Agent as a Department Manager to receive Alerts & Notices for tickets in departments. 0: Agents do not have to be members of the Department to be the Manager of the Department #This is popup help messages for the Admin Panel -> Staff -> Add New Group -> User Group Form #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- groups: title: समूह content: > Groups are used to define an Agent's permissions in the help desk. Groups can also grant access to Departments other than an Agent's primary Department. status: title: Status content: > If <span class="doc-desc-opt">Disabled</span>, Agents assigned to this Group cannot sign in and will not receive Department Alerts & Notices. department_access: title: विभाग पहुंच content: > Check all departments to which the Group members are allowed access. #This is popup help messages for the Admin Panel -> Staff -> Staff Members #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- staff_members: title: सदस्य कर्मचारी content: > The following table displays the results of the filter above. If not filter settings are chosen, then all <span class="doc-desc-title">Agent</span> (Staff) <span class="doc-desc-title">Members</span> are displayed, and broken up by pages. See the pages section below to navigate through more results. status: title: Status content: > This will display whether the <span class="doc-desc-title">Agent</span> is Locked, Active, or Active (Vacation). #This is popup help messages for the Admin Panel -> Staff -> Teams #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- teams: title: Teams content: > Teams are one or more Agents teamed together for the purpose of ticket assignment. Team membership can span across Department boundaries. status: title: Status content: > If <span class="doc-desc-opt">Disabled</span>, this Team will not be available for ticket assignments nor receive Alerts & Notices on previous assignments. lead: title: Team Lead content: > A <span class="doc-desc-title">Team</span> can have an appointed leader who can receive <span class="doc-desc-title">Alerts & Notices</span> separate from the members. links: - title: Configure Alerts & Notices href: /scp/settings.php?t=alerts assignment_alert: title: Assignment Alert content: > You may disable the <span class="doc-desc-title">Ticket Assignment Alert</span> for tickets assigned to this Team. links: - title: Configure Alerts & Notices href: /scp/settings.php?t=alerts members: title: Team Members content: > Team membership is configured via the Agent profile. links: - title: कर्मचारियों का प्रबंधन href: /scp/staff.php #This is popup help messages for the Admin Panel -> Staff #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- signature: title: Staff Signature Line content: | Create staff’s signature for response to tickets. This signature will appear as an option at the bottom of a ticket response type: title: खाते का प्रकार content: | Admins have the privilege of accessing the Admin Panel. Staff only have access to manage tickets and the knowledge base group: title: Assigned Group content: | Group membership defines the staff’s role in the system. Visit the group management page to define what access this staff has to the help desk notes: title: आंतरिक टिप्पणियां content: | Place internal notes regarding staff; notes are only visible to staff whose account type is Admin #This is popup help messages for the Agents Panel -> Tasks #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- advanced: title: उन्नत content: > Narrow down your search parameters. Once you have selected your advanced search criteria and run the search, you can <span class="doc-desc-title">Export </span> the data at the bottom of the page. export: title: निर्यात content: > Export your data currently in view in a CSV file. CSV files may be opened with any spreadsheet software (i.e., Microsoft Excel, Apple Pages, OpenOffice, etc.). #This is popup help messages for the Staff Panel -> Tickets -> Open #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. --- search_field: title: खोज क्षेत्र content: > advanced: title: उन्नत content: > Narrow down your search parameters. Once you have selected your advanced search criteria and run the search, you can <span class="doc-desc-title">Export </span> the data at the bottom of the tickets page. open_tickets_table: title: खुला टिकट तालिका content: > All tickets currently opened and requiring attention ticket: title: टिकट content: > date: title: दिनांक content: > subject: title: विषय content: > from: title: द्वारा content: > priority: title: प्राथमिकता content: > assigned_to: title: को सौपा content: > export: title: निर्यात content: > Export your data currently in view in a CSV file. CSV files may be opened with any spreadsheet software (i.e., Microsoft Excel, Apple Pages, OpenOffice, etc.). advanced_search_dialog: title: उन्नत खोज content: > adv_keyword: title: संकेत शब्द खोज content: > Find hits based on the subject and message bodies of the ticket thread as well as all textual content associated with custom fields for the users and the tickets. adv_date_range: title: तिथि सीमा के आधार पर खोजें content: > परिभाषित यहाँ करे merge_types: title: Merge Types content: > <b>Combine Threads:</b> Threads from all Tickets will be displayed chronologically.</br> <b>Separate Threads:</b> Threads from Tickets will be displayed one Ticket at a time. child_status: title: Child Ticket Status content: > All Child Tickets will be set to a closed status since thread entries will all be moved to the Parent Ticket. parent_status: title: Parent Ticket Status content: > If you choose to set a Parent Status, the Parent Ticket will be changed to the status you select. The Ticket on top of the list will be the Parent Ticket. reply_types: title: Reply Types content: > <b>Reply All:</b> This reply is sent to the User and the Collaborators you choose to include.</br> <b>Reply to User:</b> This reply is sent to the User only, no Collaborators.</br> <b>Do Not Email Reply:</b> No email alerts are sent out, however, the Agent response is visible to <b>ALL</b> Users upon viewing the Ticket. - #Canned response templates --- isenabled: 1 title: What is osTicket (sample)? response: | osTicket is a widely-used open source support ticket system, an attractive alternative to higher-cost and complex customer support systems - simple, lightweight, reliable, open source, web-based and easy to setup and use. notes: | attachments: - name: osTicket.txt type: text/plain data: Canned Attachments Rock! - isenabled: 1 title: Sample (with variables) response: | Hi %{ticket.name.first}, <br> <br> Your ticket #%{ticket.number} created on %{ticket.create_date} is in %{ticket.dept.name} department. notes: | #Email template: assigned.alert.yaml #Sent to staff members when a ticket is assigned to them. Tickets can be #assigned automatically by the system or manually by another staff member. #Use %{assigner} to distinguish who made the assignment. --- notes: | Sent to staff members when a ticket is assigned to them. Tickets can be assigned automatically by the system or manually by another staff member. Use %{assigner} to distinguish who made the assignment. subject: | टिकट आप को सौंपा गया है body: | <h3><strong>Hi %{assignee.name.first},</strong></h3> Ticket <a href="%{ticket.staff_link}">#%{ticket.number}</a> has been assigned to you by %{assigner.name.short} <br> <br> <table> <tbody> <tr> <td> <strong>From</strong>: </td> <td> %{ticket.name} <%{ticket.email}> </td> </tr> <tr> <td> <strong>Subject</strong>: </td> <td> %{ticket.subject} </td> </tr> </tbody> </table> <br> %{comments} <br> <br> <hr> <div>To view/respond to the ticket, please <a href="%{ticket.staff_link}"><span style="color: rgb(84, 141, 212);" >login</span></a> to the support ticket system</div> <em style="font-size: small; ">Your friendly Customer Support System</em> <br> <img src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc" alt="Powered by osTicket" width="126" height="19" style="width: 126px;"> #Email template: message.alert.yaml #Sent to staff members when a new message is posted by a user to a ticket. #This can occur if the users responds to an email from the system or visits #the customer web portal and posts a new message there. --- notes: | Sent to staff members when a new message is posted by a user to a ticket. This can occur if the users responds to an email from the system or visits the customer web portal and posts a new message there. subject: | नया संदेश सूचना body: | <h3><strong>Hi %{recipient.name},</strong></h3> New message appended to ticket <a href="%{ticket.staff_link}">#%{ticket.number}</a> <br> <br> <table> <tbody> <tr> <td> <strong>From</strong>: </td> <td> %{poster.name} <%{ticket.email}> </td> </tr> <tr> <td> <strong>Department</strong>: </td> <td> %{ticket.dept.name} </td> </tr> </tbody> </table> <br> %{message} <br> <br> <hr> <div>To view or respond to the ticket, please <a href="%{ticket.staff_link}"><span style="color: rgb(84, 141, 212);" >login</span></a> to the support ticket system</div> <em style="color: rgb(127,127,127); font-size: small; ">Your friendly Customer Support System</em><br> <img src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc" alt="Powered by osTicket" width="126" height="19" style="width: 126px;"> #Email template: message.autoresp.yaml #Sent to a user when the user posts a new message to a ticket. This can #happen if the users responds to an email from the system or visits the #customer web portal and posts a new message there. --- notes: | Sent to a user when the user posts a new message to a ticket. This can happen if the user responds to an email from the system or visits the customer web portal and posts a new message there. subject: | संदेश की पुष्टि body: | <h3><strong>Dear %{recipient.name.first},</strong></h3> Your reply to support request <a href="%{recipient.ticket_link}">#%{ticket.number}</a> has been noted <br> <br> <div style="color: rgb(127, 127, 127); "> Your %{company.name} Team,<br> %{signature} </div> <hr> <div style="color: rgb(127, 127, 127); font-size: small; text-align: center"><em>You can view the support request progress <a href="%{recipient.ticket_link}">online here</a></em> </div> #Email template: note.alert.yaml #Sent to staff members when a new internal note is appended to a ticket. #Internal notes can only be added by staff members. --- notes: | Alert sent out to Agents when internal activity such as an internal note or an agent reply is appended to a ticket. subject: | New Internal Activity Alert body: | <h3><strong>Hi %{recipient.name},</strong></h3> An agent has logged activity on ticket <a href="%{ticket.staff_link}">#%{ticket.number}</a> <br> <br> <table> <tbody> <tr> <td> <strong>From</strong>: </td> <td> %{note.poster} </td> </tr> <tr> <td> <strong>Title</strong>: </td> <td> %{note.title} </td> </tr> </tbody> </table> <br> %{note.message} <br> <br> <hr> To view/respond to the ticket, please <a href="%{ticket.staff_link}">login</a> to the support ticket system <br> <br> <em style="font-size: small; ">Your friendly Customer Support System</em> <br> <img src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc" alt="Powered by osTicket" width="126" height="19" style="width: 126px;"> #Email template: task.activity.alert.yaml #Sent to agents when a new note/message is posted to a task. #This can occur if a collaborator or an agent responds to an email from the #system or visits the web portal and posts a new message there. --- notes: | Sent to agents when a new message/note is posted to a task. This can occur if a collaborator or an agent responds to an email from the system or visits the web portal and posts a new message there. subject: | Task Activity [#%{task.number}] - %{activity.title} body: | <h3><strong>Hi %{recipient.name},</strong></h3> Task <a href="%{task.staff_link}">#%{task.number}</a> updated: %{activity.description} <br> <br> %{message} <br> <br> <hr> <div>To view or respond to the task, please <a href="%{task.staff_link}"><span style="color: rgb(84, 141, 212);" >login</span></a> to the support system</div> <em style="color: rgb(127,127,127); font-size: small; ">Your friendly Customer Support System</em><br> <img src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc" alt="Powered by osTicket" width="126" height="19" style="width: 126px;"> #Email template: task.activity.notice.yaml #Notice sent to collaborators on task activity e.g reply or message --- notes: | Notice sent to collaborators on task activity e.g reply or message. subject: | Re: %{task.title} [#%{task.number}] body: | <h3><strong>Dear %{recipient.name.first},</strong></h3> <div> <em>%{poster.name}</em> just logged a message to a task in which you participate. </div> <br> %{message} <br> <br> <hr> <div style="color: rgb(127, 127, 127); font-size: small; text-align: center;"> <em>You're getting this email because you are a collaborator on task #%{task.number}. To participate, simply reply to this email.</em> </div> #Email template: task.alert.yaml #Sent to an agent when a new task is created in the system. --- notes: | Sent to an agent when a new task is created in the system. subject: | New Task Alert body: | <h2>Hi %{recipient.name},</h2> New task <a href="%{task.staff_link}">#%{task.number}</a> created <br> <br> <table> <tbody> <tr> <td> <strong>Department</strong>: </td> <td> %{task.dept.name} </td> </tr> </tbody> </table> <br> %{task.description} <br> <br> <hr> <div>To view or respond to the task, please <a href="%{task.staff_link}">login</a> to the support system</div> <em style="font-size: small">Your friendly Customer Support System</em> <br> <a href="https://osticket.com/"><img width="126" height="19" style="width: 126px; " alt="Powered By osTicket" src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc"/></a> #Email template: task.assignment.alert.yaml #Sent to agents when a task is assigned to them or the team to which #they belong. #Use %{assigner} to distinguish who made the assignment. --- notes: | Sent to agents when a task is assigned to them or the team to which they belong. Use %{assigner} to distinguish who made the assignment. subject: | Task Assigned to you body: | <h3><strong>Hi %{assignee.name.first},</strong></h3> Task <a href="%{task.staff_link}">#%{task.number}</a> has been assigned to you by %{assigner.name.short} <br> <br> %{comments} <br> <br> <hr> <div>To view/respond to the task, please <a href="%{task.staff_link}"><span style="color: rgb(84, 141, 212);" >login</span></a> to the support system</div> <em style="font-size: small; ">Your friendly Customer Support System</em> <br> <img src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc" alt="Powered by osTicket" width="126" height="19" style="width: 126px;"> #Email template: task.overdue.alert.yaml #Sent to agents when a tasks transitions to overdue in the system. #Overdue tasks occur based on set due-date. --- notes: | Sent to agents when a task transitions to overdue in the system. Overdue tasks occur based on the set due-date. subject: | Stale Task Alert body: | <h3><strong>Hi %{recipient.name}</strong>,</h3> A task, <a href="%{task.staff_link}">#%{task.number}</a> is seriously overdue. <br> <br> We should all work hard to guarantee that all tasks are being addressed in a timely manner. <br> <br> Signed,<br> %{task.dept.manager.name} <hr> <div>To view or respond to the task, please <a href="%{task.staff_link}"><span style="color: rgb(84, 141, 212);" >login</span></a> to the support system. You're receiving this notice because the task is assigned directly to you or to a team or department of which you're a member.</div> <em style="font-size: small">Your friendly <span style="font-size: smaller" >(although with limited patience)</span> Customer Support System</em><br> <img src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc" height="19" alt="Powered by osTicket" width="126" style="width: 126px;"> #Email template: task.transfer.alert.yaml #Sent to agents when a task is transfered to their department. --- notes: | Sent to agents when a task is transfered to a department to which they are a member. subject: | Task #%{task.number} transfer - %{task.dept.name} body: | <h3>Hi %{recipient.name},</h3> Task <a href="%{task.staff_link}">#%{task.number}</a> has been transferred to the %{task.dept.name} department by <strong>%{staff.name.short}</strong> <br> <br> <blockquote> %{comments} </blockquote> <hr> <div>To view or respond to the task, please <a href="%{task.staff_link}">login</a> to the support system. </div> <em style="font-size: small; ">Your friendly Customer Support System</em> <br> <a href="https://osticket.com/"><img width="126" height="19" alt="Powered By osTicket" style="width: 126px;" src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc"/></a> #Email template: ticket.activity.notice.yaml #Notice sent to collaborators on ticket activity e.g reply or message --- notes: | Notice sent to collaborators on ticket activity e.g reply or message. subject: | Re: %{ticket.subject} [#%{ticket.number}] body: | <h3><strong>Dear %{recipient.name.first},</strong></h3> <div> <em>%{poster.name}</em> just logged a message to a ticket in which you participate. </div> <br> %{message} <br> <br> <hr> <div style="color: rgb(127, 127, 127); font-size: small; text-align: center;"> <em>You're getting this email because you are a collaborator on ticket <a href="%{recipient.ticket_link}" style="color: rgb(84, 141, 212);" >#%{ticket.number}</a>. To participate, simply reply to this email or <a href="%{recipient.ticket_link}" style="color: rgb(84, 141, 212);" >click here</a> for a complete archive of the ticket thread.</em> </div> #Email template: ticket.alert.yaml #Sent to a staff member when a new ticket is created in the system. This #applies to tickets created via email, the web portal, or the api. --- notes: | Sent to a staff member when a new ticket is created in the system. This applies to tickets created via email, the web portal, or the api. subject: | नया टिकट अधिसूचना body: | <h2>Hi %{recipient.name},</h2> New ticket #%{ticket.number} created <br> <br> <table> <tbody> <tr> <td> <strong>From</strong>: </td> <td> %{ticket.name} <%{ticket.email}> </td> </tr> <tr> <td> <strong>Department</strong>: </td> <td> %{ticket.dept.name} </td> </tr> </tbody> </table> <br> %{message} <br> <br> <hr> <div>To view or respond to the ticket, please <a href="%{ticket.staff_link}">login</a> to the support ticket system</div> <em style="font-size: small">Your friendly Customer Support System</em> <br> <a href="https://osticket.com/"><img width="126" height="19" style="width: 126px; " alt="Powered By osTicket" src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc"/></a> #Email template: ticket.autoreply.yaml #Sent to a user when an automatic canned response is posted to a ticket #when it is created --- notes: | Sent to a user when an automatic canned response is posted to a ticket when it is created. Available variables for replacement: %{ticket.*}, %{response} subject: | Re: %{ticket.subject} [#%{ticket.number}] body: | <h3><strong>Dear %{recipient.name.first},</strong></h3> A request for support has been created and assigned ticket <a href="%{recipient.ticket_link}">#%{ticket.number}</a> with the following automatic reply <br> <br> Topic: <strong>%{ticket.topic.name}</strong> <br> Subject: <strong>%{ticket.subject}</strong> <br> <br> %{response} <br> <br> <div style="color: rgb(127, 127, 127);">Your %{company.name} Team,<br> %{signature}</div> <hr> <div style="color: rgb(127, 127, 127); font-size: small;"><em>We hope this response has sufficiently answered your questions. If you wish to provide additional comments or information, please reply to this email or <a href="%{recipient.ticket_link}"><span style="color: rgb(84, 141, 212);" >login to your account</span></a> for a complete archive of your support requests.</em></div> #Email template: ticket.autoresp.yaml #Sent to a user when a new ticket is created --- notes: | Sent to a user when a new ticket is created subject: | Support Ticket Opened [#%{ticket.number}] body: | <h3><strong>Dear %{recipient.name.first},</strong></h3> <p> A request for support has been created and assigned #%{ticket.number}. A representative will follow-up with you as soon as possible. You can <a href="%{recipient.ticket_link}">view this ticket's progress online</a>. </p> <br> <div style="color: rgb(127, 127, 127)"> Your %{company.name} Team, <br> %{signature} </div> <hr> <div style="color: rgb(127, 127, 127); font-size: small; "><em>If you wish to provide additional comments or information regarding the issue, please reply to this email or <a href="%{recipient.ticket_link}"><span style="color: rgb(84, 141, 212);" >login to your account</span></a> for a complete archive of your support requests.</em></div> #Email template: ticket.notice.yaml #Sent to a user when a staff member creates a ticket on the user's behalf. #This is most commonly performed when user's call in on the phone. --- notes: | Sent to a user when a staff member creates a ticket on the user's behalf. This is most commonly performed when user's call in on the phone. subject: | %{ticket.subject} [#%{ticket.number}] body: | <h3><strong>Dear %{recipient.name.first},</strong></h3> Our customer care team has created a ticket, <a href="%{recipient.ticket_link}">#%{ticket.number}</a> on your behalf, with the following details and summary: <br> <br> Topic: <strong>%{ticket.topic.name}</strong> <br> Subject: <strong>%{ticket.subject}</strong> <br> <br> %{message} <br> <br> %{response} <br> <br> If need be, a representative will follow-up with you as soon as possible. You can also <a href="%{recipient.ticket_link}">view this ticket's progress online</a>. <br> <br> <div style="color: rgb(127, 127, 127);"> Your %{company.name} Team,<br> %{signature}</div> <hr> <div style="color: rgb(127, 127, 127); font-size: small; "><em>If you wish to provide additional comments or information regarding the issue, please reply to this email or <a href="%{recipient.ticket_link}"><span style="color: rgb(84, 141, 212);" >login to your account</span></a> for a complete archive of your support requests.</em></div> #Email template: ticket.overdue.yaml #Sent to staff members when a ticket transitions to overdue in the system. #Overdue tickets occur based on the ticket's due-date as well as the SLA #defined for the ticket. --- notes: | Sent to staff members when a ticket transitions to overdue in the system. Overdue tickets occur based on the ticket's due-date as well as the SLA defined for the ticket. subject: | Stale Ticket Alert body: | <h3><strong>Hi %{recipient.name}</strong>,</h3> A ticket, <a href="%{ticket.staff_link}">#%{ticket.number}</a> is seriously overdue. <br> <br> We should all work hard to guarantee that all tickets are being addressed in a timely manner. <br> <br> Signed,<br> %{ticket.dept.manager.name} <hr> <div>To view or respond to the ticket, please <a href="%{ticket.staff_link}"><span style="color: rgb(84, 141, 212);" >login</span></a> to the support ticket system. You're receiving this notice because the ticket is assigned directly to you or to a team or department of which you're a member.</div> <em style="font-size: small">Your friendly <span style="font-size: smaller" >(although with limited patience)</span> Customer Support System</em><br> <img src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc" height="19" alt="Powered by osTicket" width="126" style="width: 126px;"> #Email template: ticket.overlimit.yaml #Sent to users when they have exceeded the maximum open ticket limit. The #limit is configurable in the Admin Panel, and is defined by the number of #tickets open by a particular email address. --- notes: | Sent to users when they have exceeded the maximum open ticket limit. The limit is configurable in the Admin Panel, and is defined by the number of tickets open by a particular email address. subject: | Open Tickets Limit Reached body: | <h3><strong>Dear %{ticket.name.first},</strong></h3> You have reached the maximum number of open tickets allowed. To be able to open another ticket, one of your pending tickets must be closed. To update or add comments to an open ticket simply <a href="%{url}/tickets.php?e=%{ticket.email}">login to our helpdesk</a>. <br> <br> Thank you,<br/> Support Ticket System #Email template: ticket.reply.yaml #Sent to users when a staff members makes a reply to their ticket. Replies #are only generated by staff members. --- notes: | Sent to users when a staff members makes a reply to their ticket. Replies are only generated by staff members. subject: | Re: %{ticket.subject} [#%{ticket.number}] body: | <h3><strong>Dear %{recipient.name.first},</strong></h3> %{response} <br> <br> <div style="color: rgb(127, 127, 127);"> Your %{company.name} Team,<br> %{signature} </div> <hr> <div style="color: rgb(127, 127, 127); font-size: small; text-align: center;" ><em>We hope this response has sufficiently answered your questions. If not, please do not send another email. Instead, reply to this email or <a href="%{recipient.ticket_link}" style="color: rgb(84, 141, 212);" >login to your account</a> for a complete archive of all your support requests and responses.</em></div> #Email template: transfer.alert.yaml #Sent to staff members when a ticket is assigned to them. Tickets can be #assigned automatically by the system or manually by another staff member. #Use %{assigner} to distinguish who made the assignment. --- notes: | Sent to agents when a ticket is transfered to a department to which they are a member. subject: | Ticket #%{ticket.number} transfer - %{ticket.dept.name} body: | <h3>Hi %{recipient.name},</h3> Ticket <a href="%{ticket.staff_link}">#%{ticket.number}</a> has been transferred to the %{ticket.dept.name} department by <strong>%{staff.name.short}</strong> <br> <br> <blockquote> %{comments} </blockquote> <hr> <div>To view or respond to the ticket, please <a href="%{ticket.staff_link}">login</a> to the support ticket system. </div> <em style="font-size: small; ">Your friendly Customer Support System</em> <br> <a href="https://osticket.com/"><img width="126" height="19" alt="Powered By osTicket" style="width: 126px;" src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc"/></a> #access-link.yaml #Ticket access link sent to clients for guest-only systems where the ticket #number and email address will trigger an access link sent via email --- notes: > This template defines the notification for Clients that an access link was sent to their email. The ticket number and email address trigger the access link. name: "टिकट प्रवेश लिंक [#%{ticket.number}] " body: > <h3><strong>Hi %{recipient.name.first},</strong></h3> <div> An access link request for ticket #%{ticket.number} has been submitted on your behalf for the helpdesk at %{url}.<br /> <br /> Follow the link below to check the status of the ticket #%{ticket.number}.<br /> <br /> <a href="%{recipient.ticket_link}">%{recipient.ticket_link}</a><br /> <br /> If you <strong>did not</strong> make the request, please delete and disregard this email. Your account is still secure and no one has been given access to the ticket. Someone could have mistakenly entered your email address.<br /> <br /> --<br /> %{company.name} </div> #banner-client.yaml #This forms the header on the staff login page. It can be useful to inform #your clients about your login and registration policies. --- notes: > This composes the header on the Client Log In page. It can be useful to inform your Clients about your log in and registration policies. name: "Sign in to %{company.name}" body: > To better serve you, we encourage our Clients to register for an account. #banner-staff.yaml #This is the initial message and banner shown on the staff login page --- notes: > This is the initial message and banner shown on the Staff Log In page. The first input field refers to the red-formatted text that appears at the top. The latter textarea is for the banner content which should serve as a disclaimer. name: "Authentication Required" body: "" #email2fa-staff.yaml #Template of the email sent to staff members when using the Email #Two Factor Authentication --- notes: > This template defines the email sent to Staff who use Email for Two Factor Authentication name: "osTicket Two Factor Authentication" body: > <h3><strong>Hi %{staff.name.first},</strong></h3> <div> You have just logged into for the helpdesk at %{url}.<br /> <br /> Use the verification code below to finish logging into the helpdesk.<br /> <br /> %{otp}<br /> <br /> <em style="font-size: small">Your friendly Customer Support System</em> <br /> <img src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc" alt="Powered by osTicket" width="126" height="19" style="width: 126px" /> </div> #Page template: landing.yaml #The landing page is served on the front page of the customer portal above #the two links for creating new tickets and viewing ticket status. --- notes: > The Landing Page refers to the content of the Customer Portal's initial view. The template modifies the content seen above the two links <strong>Open a New Ticket</strong> and <strong>Check Ticket Status</strong>. name: Landing body: > <h1>Welcome to the Support Center</h1> <p> In order to streamline support requests and better serve you, we utilize a support ticket system. Every support request is assigned a unique ticket number which you can use to track the progress and responses online. For your reference we provide complete archives and history of all your support requests. A valid email address is required to submit a ticket. </p> #Page template: offline.yaml #The offline page is served to the customer portal when the help desk is #configured offline in the Admin Panel --- notes: | ऑफ़लाइन पृष्ठ ग्राहक पोर्टल में दिखाई देता है जब सहायता डेस्क ऑफ़लाइन है। name: ऑफ़लाइन body: | <div><h1> <span style="font-size: medium">समर्थन टिकट प्रणाली ऑफलाइन है</span> </h1> <p>हमसे संपर्क करने में आपकी रुचि के लिए धन्यवाद।</p> <p>हमारे हेल्पडेस्क अब ऑफ़लाइन है। कृपया बाद में वापस आकर देखें।</p> </div> #pwreset-client.yaml #Template of the email sent to clients when using the Forgot My Password #link on the login page --- notes: > This template defines the email sent to Clients who select the <strong>Forgot My Password</strong> link on the Client Log In page. name: "%{company.name} Help Desk Access" body: > <h3><strong>Hi %{user.name.first},</strong></h3> <div> A password reset request has been submitted on your behalf for the helpdesk at %{url}.<br /> <br /> If you feel that this has been done in error, delete and disregard this email. Your account is still secure and no one has been given access to it. It is not locked and your password has not been reset. Someone could have mistakenly entered your email address.<br /> <br /> Follow the link below to login to the help desk and change your password.<br /> <br /> <a href="%{link}">%{link}</a><br /> <br /> <em style="font-size: small">Your friendly Customer Support System <br /> %{company.name}</em> </div> #pwreset-staff.yaml #Template of the email sent to staff members when using the Forgot My #Password link --- notes: > This template defines the email sent to Staff who select the <strong>Forgot My Password</strong> link on the Staff Control Panel Log In page. name: "osTicket Staff Password Reset" body: > <h3><strong>Hi %{staff.name.first},</strong></h3> <div> A password reset request has been submitted on your behalf for the helpdesk at %{url}.<br /> <br /> If you feel that this has been done in error, delete and disregard this email. Your account is still secure and no one has been given access to it. It is not locked and your password has not been reset. Someone could have mistakenly entered your email address.<br /> <br /> Follow the link below to login to the help desk and change your password.<br /> <br /> <a href="%{link}">%{link}</a><br /> <br /> <em style="font-size: small">Your friendly Customer Support System</em> <br /> <img src="cid:b56944cb4722cc5cda9d1e23a3ea7fbc" alt="Powered by osTicket" width="126" height="19" style="width: 126px" /> </div> #registration-staff.yaml #Confirmation email sent to clients when accounts are created for them by #staff or via the client portal. This email serves as an email address #verification. --- notes: > This template defines the email sent to Clients when their account has been created in the Client Portal or by an Agent on their behalf. This email serves as an email address verification. Please use %{link} somewhere in the body. name: "Welcome to %{company.name}" body: > <h3><strong>Hi %{recipient.name.first},</strong></h3> <div> We've created an account for you at our help desk at %{url}.<br /> <br /> Please follow the link below to confirm your account and gain access to your tickets.<br /> <br /> <a href="%{link}">%{link}</a><br /> <br /> <em style="font-size: small">Your friendly Customer Support System <br /> %{company.name}</em> </div> #registration-confirm.yaml #Template of the page shown to the user after registering for an account. #The system will send the user an email with a link they should follow to #confirm the account. This page should inform them of the next step in #the process. --- notes: > This templates defines the page shown to Clients after completing the registration form. The template should mention that the system is sending them an email confirmation link and what is the next step in the registration process. name: "खाता पंजीकरण" body: > <div><strong>Thanks for registering for an account.</strong><br/> <br /> We've just sent you an email to the address you entered. Please follow the link in the email to confirm your account and gain access to your tickets. </div> #registration-staff.yaml #Initial (optional) email sent to staff members when accounts are created #for them in the staff control panel --- notes: > This template defines the initial email (optional) sent to Agents when an account is created on their behalf. name: "Welcome to osTicket" body: > <h3><strong>Hi %{recipient.name.first},</strong></h3> <div> We've created an account for you at our help desk at %{url}.<br /> <br /> Please follow the link below to confirm your account and gain access to your tickets.<br /> <br /> <a href="%{link}">%{link}</a><br /> <br /> <em style="font-size: small">Your friendly Customer Support System<br /> %{company.name}</em> </div> #registration-thanks.yaml #Page shown to the user after successfully registring and confirming their #account. This page should inform the user that the process is complete and #that the user can now submit a ticket or access existing tickets --- notes: > This template defines the content displayed after Clients successfully register by confirming their account. This page should inform the user that registration is complete and that the Client can now submit a ticket or access existing tickets. name: "Account Confirmed!" body: > <div> <strong>Thanks for registering for an account.</strong><br /> <br /> You've confirmed your email address and successfully activated your account. You may proceed to open a new ticket or manage existing tickets.<br /> <br /> <em>Your friendly support center</em><br /> %{company.name} </div> #Page template: thank-you.yaml #The thank-you page is served to the customer portal when a user submites a #new ticket via the customer portal. --- notes: | This template defines the content displayed on the Thank-You page after a Client submits a new ticket in the Client Portal. name: Thank You body: | <div>%{ticket.name}, <br> <br> Thank you for contacting us. <br> <br> A support ticket request has been created and a representative will be getting back to you shortly if necessary.</p> <br> <br> Support Team </div> #Welcome ticket template #When the system if first installed and the installer finishes setting up #the database, it creates a first ticket with a welcome message to the #administrator --- deptId: 1 #support topicId: 1 #support name: osTicket Team email: feedback@osticket.com source: वेब #notrans subject: osTicket स्थापित! message: | <p> Thank you for choosing osTicket. </p><p> Please make sure you join the <a href="https://forum.osticket.com">osTicket forums</a> and our <a href="https://osticket.com">mailing list</a> to stay up to date on the latest news, security alerts and updates. The osTicket forums are also a great place to get assistance, guidance, tips, and help from other osTicket users. In addition to the forums, the <a href="https://docs.osticket.com">osTicket Docs</a> provides a useful collection of educational materials, documentation, and notes from the community. We welcome your contributions to the osTicket community. </p><p> If you are looking for a greater level of support, we provide professional services and commercial support with guaranteed response times, and access to the core development team. We can also help customize osTicket or even add new features to the system to meet your unique needs. </p><p> If the idea of managing and upgrading this osTicket installation is daunting, you can try osTicket as a hosted service at <a href="https://supportsystem.com">https://supportsystem.com/</a> -- no installation required and we can import your data! With SupportSystem's turnkey infrastructure, you get osTicket at its best, leaving you free to focus on your customers without the burden of making sure the application is stable, maintained, and secure. </p><p> Cheers, </p><p> -<br/> osTicket Team - https://osticket.com/ </p><p> <strong>PS.</strong> Don't just make customers happy, make happy customers! </p> #Upgrade completed ticket #This ticket is added to the system after the completion of an upgrade. It #might include information specific to the release, perhaps with some new #feature highlights, etc. --- source: वेब #notrans name: osTicket Team email: feedback@osticket.com subject: osTicket Upgraded! message: | <p> osTicket upgraded successfully! Please refer to the Release Notes (https://github.com/osTicket/osTicket/releases) for more information about changes and new features. </p><p> Be sure to join the <a href="https://forum.osticket.com">osTicket forums</a> and our <a href="https://osticket.com">mailing list</a> to stay up to date on announcements, security updates and alerts! Your contribution to osTicket community will be appreciated! </p><p> The osTicket team is committed to providing support to all users through our free online resources and a full range of commercial support packages and services. For more information, or to discuss your needs, please contact us today at https://osticket.com/support/. Any feedback will be appreciated! </p><p> If managing and upgrading this osTicket installation is daunting, you can try osTicket as a hosted service at https://supportsystem.com/ -- no upgrading ever, and we can import your data! With SupportSystem's turnkey infrastructure, you get osTicket at its best, leaving you free to focus on your customers without the burden of making sure the application is stable, maintained, and secure. </p><p> -<br/> osTicket Team<br/> https://osticket.com/ </p> /* Hindi initialisation for the jQuery UI date picker plugin. */ /* Written by Michael Dawart. */ ( function( factory ) { "use strict"; if ( typeof define === "function" && define.amd ) { // AMD. Register as an anonymous module. define( [ "../widgets/datepicker" ], factory ); } else { // Browser globals factory( jQuery.datepicker ); } } )( function( datepicker ) { "use strict"; datepicker.regional.hi = { closeText: "बंद", prevText: "पिछला", nextText: "अगला", currentText: "आज", monthNames: [ "जनवरी ", "फरवरी", "मार्च", "अप्रेल", "मई", "जून", "जूलाई", "अगस्त ", "सितम्बर", "अक्टूबर", "नवम्बर", "दिसम्बर" ], monthNamesShort: [ "जन", "फर", "मार्च", "अप्रेल", "मई", "जून", "जूलाई", "अग", "सित", "अक्ट", "नव", "दि" ], dayNames: [ "रविवार", "सोमवार", "मंगलवार", "बुधवार", "गुरुवार", "शुक्रवार", "शनिवार" ], dayNamesShort: [ "रवि", "सोम", "मंगल", "बुध", "गुरु", "शुक्र", "शनि" ], dayNamesMin: [ "रवि", "सोम", "मंगल", "बुध", "गुरु", "शुक्र", "शनि" ], weekHeader: "हफ्ता", dateFormat: "dd/mm/yy", firstDay: 1, isRTL: false, showMonthAfterYear: false, yearSuffix: "" }; datepicker.setDefaults( datepicker.regional.hi ); return datepicker.regional.hi; } ); <?php return array ( '' => 'Project-Id-Version: osticket-official X-Osticket-Major-Version: 1.18 POT-Create-Date: 2023-07-11 20:52 +0000 Report-Msgid-Bugs-To: support@osticket.com Language: hi_IN MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Generator: osTicket i18n CLI Plural-Forms: nplurals=2; plural=(n != 1); X-Crowdin-Project: osticket-official X-Crowdin-Project-ID: 25755 X-Crowdin-Language: hi X-Crowdin-File: /1.18.x/LC_MESSAGES/messages.po X-Crowdin-File-ID: 2069 Language-Team: Hindi PO-Revision-Date: 2025-02-04 17:27 ', 'Account Type' => 'खाते का प्रकार', 'Admin Notes' => 'व्यवस्थापक नोट्स', 'Advanced' => 'उन्नत', 'Advanced Search' => 'उन्नत खोज', 'Archived' => 'संग्रहीत', 'Assigned' => 'सौंपा गया', 'Assigned To' => 'को सौपा', 'Banned Email Addresses' => 'प्रतिबंधित ईमेल पते', 'Canned Responses' => 'पूर्व आरक्षित प्रतिक्रियाएँ', 'Closed' => 'बंद', 'Company Information' => 'कंपनी की जानकारी', 'Confirm New Password' => 'नए पासवर्ड की पुष्टि करें', 'Confirm Password' => 'पासवर्ड की पुष्टि करें', 'Current Password' => 'वर्तमान पासवर्ड', 'Date' => 'दिनांक', 'Default SLA' => 'पूर्वनिर्धारित सेवा स्तर समझौता', 'Default System Email' => 'डिफ़ॉल्ट/मूल सिस्टम ईमेल', 'Deleted' => 'मिटाया गया', 'Department' => 'विभाग', 'Department Manager' => 'विभाग प्रबंधक', 'Email Address' => 'ईमेल पता', 'Export' => 'निर्यात', 'First Name' => 'प्रथम नाम', 'From' => 'द्वारा', 'Help Topic' => 'सहायक विषय', 'Helpdesk Name' => 'सहायता प्रणाली के लिये नाम', 'Internal Notes' => 'आंतरिक टिप्पणियां', 'Internal list for email banning. Do not remove' => 'ईमेल पर प्रतिबंध लगाने के लिए आंतरिक सूची । दूर नहीं करते', 'Knowledge Base Status' => 'ज्ञानकोश स्थिति', 'Last Name' => 'अंतिम नाम', 'Manage Agents' => 'एजेंटों का प्रबंधन', 'Message' => 'संदेश', 'MySQL Database' => 'MySQL डाटाबेस', 'MySQL Hostname' => 'MySQL होस्ट-नाम', 'MySQL Password' => 'MySQL पासवर्ड', 'MySQL Table Prefix' => 'MySQL टेबल प्रि्फिक्स', 'MySQL Username' => 'MySQL उपयोगकर्ता का नाम', 'Name' => 'नाम', 'New Message Alert' => 'नया संदेश सूचना', 'New Password' => 'नया पासवर्ड', 'New Ticket Alert' => 'नया टिकट अधिसूचना', 'Offline' => 'ऑफ़लाइन', 'Opened' => 'खोला गया', 'Overdue' => 'अतिदेय', 'Password' => 'पासवर्ड', 'Plural Name' => 'बहुवचन नाम', 'Priority' => 'प्राथमिकता', 'Reject Ticket' => 'टिकट अस्वीकार', 'Reopened' => 'पुनः खोला गया', 'Report timeframe' => 'रिपोर्ट समय सीमा', 'Response Time' => 'प्रतिक्रिया में लगा समय', 'SLA' => 'सेवा स्तर समझौता', 'SLA Plan' => 'SLA योजना', 'Service Time' => 'सेवा में लगा समय', 'Signature' => 'हस्ताक्षर', 'Sort Order' => 'क्रमबद्ध', 'Statistics' => 'आंकड़े', 'Subject' => 'विषय', 'Test Outgoing Email' => 'निवर्तमान ईमेल परीक्षण', 'Ticket' => 'टिकट', 'Ticket Activity' => 'टिकट गतिविधि', 'Time Zone' => 'समय क्षेत्र', 'To' => 'के लिये', 'Username' => 'उपयोगकर्ता का नाम', 'Web' => 'वेब', 'ticket state nameArchived' => 'संग्रहीत', 'ticket state nameClosed' => 'बंद', 'ticket state nameDeleted' => 'मिटाया गया', 0 => array ( 'Revision' => 0, 'Total-Strings' => 69, 'Table-Size' => 69, 'Build-Timestamp' => 'Tue, 04 Feb 25 17:27:09 +0000', 'Format-Version' => 'A', 'Encoding' => 'UTF-8', ), );(function($){$.oststrings={"Cancel":"Cancel","You sure?":"You sure?","File Upload Error":"File Upload Error","Uploading ...":"Uploading ...","Your browser is not supported":"Your browser is not supported","You are trying to upload too many files":"You are trying to upload too many files","File is too large":"File is too large","This type of file is not allowed":"This type of file is not allowed","Could not find or read this file":"Could not find or read this file","Are you sure you want to leave? Any changes or info you've entered will be discarded!":"Are you sure you want to leave? Any changes or info you've entered will be discarded!","Show Images":"Show Images","Download":"Download","all changes saved":"all changes saved","Delete Draft":"Delete Draft","Save Draft":"Save Draft","saving...":"saving...","save error":"save error","Unable to save draft.":"Unable to save draft.","Refresh the current page to restore and continue your draft.":"Refresh the current page to restore and continue your draft.","unsaved":"unsaved","Annotate":"Annotate","Annotate Image":"Annotate Image","Commit":"Commit","Add Shape":"Add Shape","Add Arrow":"Add Arrow","Add Box":"Add Box","Add Ellipse":"Add Ellipse","Add Text":"Add Text","Add Scribble":"Add Scribble","Shape Color":"Shape Color","Font Size":"Font Size","Font Family":"Font Family","Outline":"Outline","Bring Forward":"Bring Forward","Toggle Opacity":"Toggle Opacity","Delete Shape":"Delete Shape","Fill":"Fill","Text":"Text","Translate":"Translate","save translation":"save translation","Loading":"Loading","Add":"Add","Not currently translated":"Not currently translated","Save":"Save","Saving":"Saving","You're limited to only {0} selections.\\n":"You're limited to only {0} selections.\\n","You have made {0} selections.\\n":"You have made {0} selections.\\n","Please remove {0} selection(s).":"Please remove {0} selection(s).","Alert":"Alert","Please make at least {0} selections. {1} checked so far.":"Please make at least {0} selections. {1} checked so far.","Are you sure you want to remove this attachment?":"Are you sure you want to remove this attachment?","Please Confirm":"Please Confirm","Please confirm to continue.":"Please confirm to continue.","OK":"OK","Oops":"Oops","You need to select at least one item":"You need to select at least one item","Confirm Deletion":"Confirm Deletion","Create":"Create","just now":"just now","about a minute ago":"about a minute ago","%d minutes ago":"%d minutes ago","about an hour ago":"about an hour ago","%d hours ago":"%d hours ago","yesterday":"yesterday","%d days ago":"%d days ago","Acquiring Lock":"Acquiring Lock","Your lock is expiring soon.":"Your lock is expiring soon.","The lock you hold on this ticket will expire soon. Would you like to renew the lock?":"The lock you hold on this ticket will expire soon. Would you like to renew the lock?","Renew":"Renew","Unable to lock the ticket.":"Unable to lock the ticket.","Someone else could be working on the same ticket.":"Someone else could be working on the same ticket.","Still busy... smile #":"Still busy... smile #","Cleaning up!...":"Cleaning up!...","Error occurred. Aborting...":"Error occurred. Aborting...","Manual upgrade required (ajax failed)":"Manual upgrade required (ajax failed)","Something went wrong":"Something went wrong"};})(jQuery);<?php return array ( 'Build-Date' => 'Tue, 04 Feb 25 17:27:09 +0000', 'Phrases-Version' => '1.18', 'Build-Version' => 'v1.18.2', 'Build-Major-Version' => '1.18', 'Language' => 'hi_IN', 'Id' => 'lang:hi', 'Last-Revision' => '2025-02-04 17:27', 'Version' => 173869, );1�l~f�#�X�h;���?�nwW GBMB
Close
