meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tickets [2023/09/14 15:33] – johnnytickets [2023/12/16 11:15] (current) – [API] wrongecho
Line 8: Line 8:
  
   * All tickets (from all clients)   * All tickets (from all clients)
- +{{:tickets-listing.png?900|}}
-{{:tickets-listing.png|}} +
-{{:tickets-listing.png?nolink|}}+
  
   * Client-specific tickets - accessed via a client's view/page   * Client-specific tickets - accessed via a client's view/page
- +{{:client-tickets-list.png?900|}}
-{{:client-tickets-list.png|}}+
  
  
Line 42: Line 39:
  
   * Scheduled tickets   * Scheduled tickets
-{{:scheduled-tickets-create.png|}}+{{:scheduled-tickets-create.png?500|}}
   * Invoicing   * Invoicing
-{{:tickets-invoice.png|}} +{{:tickets-invoice.png?300|}} 
-  * Auto-close tickets+  * Close - Once a ticket is closed, it cannot be re-opened 
 +  * Auto-close tickets - sends a friendly chaser message before automatically closing the ticket for good
  
 ==== Email Ticketing ==== ==== Email Ticketing ====
 Registered client contacts can create/update tickets via e-mail. Registered client contacts can create/update tickets via e-mail.
   * Configure at: **Settings > Mail**:   * Configure at: **Settings > Mail**:
-    * IMAP Host +    * IMAP Host, Port, Encryption 
-    * IMAP Port +    * Ticket from email/name
-    * IMAP Encryption+
   * Turn on: **Settings > Ticket > Email-to-ticket parsing**   * Turn on: **Settings > Ticket > Email-to-ticket parsing**
   * Add a cron job to run email_parser_cron.php every min   * Add a cron job to run email_parser_cron.php every min
 +
 +=== Notifications ===
 +  * Client notifications can be configured to be sent on ticket creation & closure //("Send clients general notification emails")//
 +  * New ticket email notifications can be configured to a email/distribution list, so your team is always aware of new tickets //("Email address to notify when new tickets are raised")//
 +  * IN PROGRESS: Agents will be notified when assigned a ticket & when their assigned ticket is replied to / updated
  
 ==== Notes ==== ==== Notes ====
   * Only supports basic authentication (no oAuth) for now - a "nice to have" in the future   * Only supports basic authentication (no oAuth) for now - a "nice to have" in the future
-  * The IMAP connection uses the same SMTP Username/Password configured for sending emails - should be configurable in future +  * Emails from unregistered contacts without a ticket reference are ignored (unless the from domain matches a domain registered in ITFlow)
-  * Emails from unregistered contacts without a ticket reference are ignored - we plan to auto-create contacts based on a client domain in future +
 ==== API ==== ==== API ====
 /api/v1/tickets /api/v1/tickets
Line 70: Line 70:
 <code> <code>
  
-Invoke-RestMethod -Uri "http://127.0.0.1/itflow/api/v1/tickets/read.php?api_key=3iVeTipINS9eDGpm&ticket_id=3" | ConvertTo-Json+Invoke-RestMethod -Uri "https://demo.itflow.org/api/v1/tickets/read.php?api_key=YOUR-API-KEY&ticket_id=3" | ConvertTo-Json
 { {
     "success":  "True",     "success":  "True",