You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently Emails are sent synchronously when posting or modifying a ticket. This poses two problems:
If Email sending is slow it is noticed directly by the end user.
If Email sending fails, the end user gets a failure page. The ticket is created anyway. The user has no
clear indication how to recover correctly from the situation.
Describe the solution you'd like
Use a mail queuing module like Django Mail Queue, which
stores to be sent Emails in the database and allows for asynchronous delivery.
Describe alternatives you've considered
The case of failed Email sending could be handled gracefully with sensible user feedback. However it burdens
the end user with a task that should be handled by the system administrator of the django-helpdesk installation.
Additional context
I might provide a PR at a later point of time.
The text was updated successfully, but these errors were encountered:
In my humble opinion this is out of scope of the project. We use django-post-office in production to this effect and that requires,no changes to helpdesk. You can just set your email backend like so
For us it would be quite annoying to have Django Mail Queue baked into gelpdesk as then there would be a longer debug chain and more entries in the DB.
Is your feature request related to a problem? Please describe.
Currently Emails are sent synchronously when posting or modifying a ticket. This poses two problems:
clear indication how to recover correctly from the situation.
Describe the solution you'd like
Use a mail queuing module like Django Mail Queue, which
stores to be sent Emails in the database and allows for asynchronous delivery.
Describe alternatives you've considered
The case of failed Email sending could be handled gracefully with sensible user feedback. However it burdens
the end user with a task that should be handled by the system administrator of the django-helpdesk installation.
Additional context
I might provide a PR at a later point of time.
The text was updated successfully, but these errors were encountered: