POST /tickets/newmessage could only reach a ticket via its track_id (fetch was hardcoded to id=0). This resolves the ticket by id, then ref, then track_id (kept as fallback), so integrations that store the Dolibarr ticket id can append messages without knowing the track_id. |
||
|---|---|---|
| .. | ||
| class | ||
| img | ||
| stats | ||
| tpl | ||
| agenda.php | ||
| card.php | ||
| contact.php | ||
| document.php | ||
| index.php | ||
| list.php | ||
| messaging.php | ||
| note.php | ||
| README.md | ||
Ticket module
An issue tracker that provides a delicate balance between simplicity and power and complete integration with the other modules. Offer your customers an easy to use interface to report and follow status of their issue. Manage your issues from your backoffice.
By enabling the Email Collector module, you can also having your ticket created automatically from input emails.