mirror of
https://gitea.mueller.network/extern/django-helpdesk.git
synced 2024-11-21 23:43:11 +01:00
93 lines
6.8 KiB
ReStructuredText
93 lines
6.8 KiB
ReStructuredText
Configuration
|
|
=============
|
|
|
|
**IMPORTANT NOTE**: Any tickets created via POP3 or IMAP mailboxes will DELETE the original e-mail from the mail server.
|
|
|
|
Before django-helpdesk will be much use, you need to do some basic configuration. Most of this is done via the Django admin screens.
|
|
|
|
1. Visit ``http://yoursite/admin/`` and add a Helpdesk Queue. If you wish, enter your POP3 or IMAP server details.
|
|
|
|
2. Visit ``http://yoursite/helpdesk/`` (or whatever path as defined in your ``urls.py``)
|
|
|
|
3. If you wish to automatically create tickets from the contents of an e-mail inbox, set up a cronjob to run the management command on a regular basis. (Or use Celery, see below)
|
|
|
|
Don't forget to set the relevant Django environment variables in your crontab::
|
|
|
|
*/5 * * * * /path/to/helpdesksite/manage.py get_email
|
|
|
|
This will run the e-mail import every 5 minutes
|
|
|
|
You will need to create a support queue, and associated login/host values, in the Django admin interface, in order for mail to be picked-up from the mail server and placed in the tickets table of your database. The values in the settings file alone, will not create the necessary values to trigger the get_email function.
|
|
|
|
If you wish to use `celery` instead of cron, you must add 'django_celery_beat' to `INSTALLED_APPS` and add a periodic celery task through the Django admin.
|
|
|
|
You will need to create a support queue, and associated login/host values, in the Django admin interface, in order for mail to be picked-up from the mail server and placed in the tickets table of your database. The values in the settings file alone, will not create the necessary values to trigger the get_email function.
|
|
|
|
DEBUGGING EMAIL EXTRACTION
|
|
==========================
|
|
You can run the management command manually from the command line with additional commands options:
|
|
**debug_to_stdout** - set this when manually running the command from a terminal so that additional debugging about which queues are being processed is written to stdout (console by default)
|
|
For example:
|
|
**/path/to/helpdesksite/manage.py get_email --debug_to_stdout**
|
|
|
|
4. If you wish to automatically escalate tickets based on their age, set up a cronjob to run the escalation command on a regular basis::
|
|
|
|
0 * * * * /path/to/helpdesksite/manage.py escalate_tickets
|
|
|
|
This will run the escalation process hourly, using the 'Escalation Days' setting for each queue to determine which tickets to escalate.
|
|
|
|
5. If you wish to exclude some days (eg, weekends) from escalation calculations, enter the dates manually via the Admin, or setup a cronjob to run a management command on a regular basis::
|
|
|
|
0 0 * * 0 /path/to/helpdesksite/manage.py create_escalation_exclusions --days saturday,sunday --escalate-verbosely
|
|
|
|
This will, on a weekly basis, create exclusions for the coming weekend.
|
|
|
|
6. Log in to your Django admin screen, and go to the 'Sites' module. If the site ``example.com`` is listed, click it and update the details so they are relevant for your website.
|
|
|
|
7. If you do not send mail directly from your web server (eg, you need to use an SMTP server) then edit your ``settings.py`` file so it contains your mail server details::
|
|
|
|
EMAIL_HOST = 'XXXXX'
|
|
EMAIL_HOST_USER = 'YYYYYY@ZZZZ.PPP'
|
|
EMAIL_HOST_PASSWORD = '123456'
|
|
|
|
8. If you wish to use SOCKS4/5 proxy with Helpdesk Queue email operations, install PySocks manually. Please note that mixing both SOCKS and non-SOCKS email sources for different queues is only supported under Python 2; on Python 3, SOCKS proxy support is all-or-nothing: either all queue email sources must use SOCKS or none may use it. If you need this functionality on Python 3 please `let us know <https://github.com/django-helpdesk/django-helpdesk/issues/new>`_.
|
|
|
|
You're now up and running! Happy ticketing.
|
|
|
|
Queue settings via admin interface
|
|
----------------------------------
|
|
Locale
|
|
^^^^^^
|
|
The *Locale* value must match the value in the ``locale`` column in the ``helpdesk_emailtemplate`` table if you wish to use those templates. For default installations/templates those values are ``cs``, ``de``, ``en``, ``es``, ``fi``, ``fr``, ``it``, ``pl``, ``ru`` and ``zh``.
|
|
|
|
If you want to use a different *Local* then you will need to generate/edit the necessary templates (and set the value in the ``locale`` column) for those locales. This includes when using language variants, such as ``de-CH``, ``en-GB`` or ``fr-CA`` for example.
|
|
|
|
E-Mail Check Interval
|
|
^^^^^^^^^^^^^^^^^^^^^
|
|
This setting does not trigger e-mail collection, it merely throttles it. In order to trigger e-mail collection you must run a crontab to trigger ``manage.py get_email``. The setting in *E-Mail Check Interval* prevents your crontab from running the e-mail trigger more often than the interval set.
|
|
|
|
For example, setting *E-Mail Check Interval* to ``5`` will limit the collection of e-mail to once every five minutes, even if your crontab is firing every five seconds. If your cron job is set to fire once every hour, then e-mail will only be collected once every hour.
|
|
|
|
The cron job triggers the collection of e-mail, *E-Mail Check Interval* restricts how often the trigger is effective.
|
|
|
|
To remove this limit, set *E-Mail Check Interval* to ``0``.
|
|
|
|
Potential problems
|
|
""""""""""""""""""
|
|
There is potential for a timing clash to prevent triggering of mail collection if *E-Mail Check Interval* and your crontab interval are identical. Because the crontab runs fractionally before, or at exactly the same time as *E-Mail Check Interval* is run, if the timings for both are identical then every second call by the crontab will be ignored by *E-Mail Check Interval* because its interval has yet to expire.
|
|
|
|
The result is that if both crontab and *E-Mail Check Interval* are set to run at five minute intervals, then mail may actually only be collected every ten minutes. You will see the evidence of this in the helpdesk mail log, or in the logs of your mail server.
|
|
|
|
To avoid this problem set the crontab and *E-Mail Check Interval* to marginally different values (or set *E-Mail Check Interval* to ``0``). *E-Mail Check Interval* will only take an integer value, in minutes, so if you want a five minute interval between mail checks, then you will either have to set *E-Mail Check Interval* to ``4`` and the crontab interval to ``300 seconds``, or the *E-Mail Check Interval* to ``5`` and the crontab interval to ``305 seconds``.
|
|
|
|
The crontab interval overrides the *E-Mail Check Interval*, and resets the *E-Mail Check Interval* each time it fires, as long as the crontab interval is greater than *E-Mail Check Interval*.
|
|
|
|
Custom Navigation Header
|
|
------------------------
|
|
You may add your own site specific navigation header to be included inside the <body> tag and before django-helpdesk navbar.
|
|
|
|
1. Create an override template in your project's templates directory::
|
|
|
|
helpdesk/custom_navigation_header.html
|
|
|
|
2. Update the contents to display your custom navigation. |