hadzo Posted June 23, 2014 Report Share Posted June 23, 2014 My customers use the support ticketing in Blesta, and everytime I get an support email there is not link to the ticket itself - therefore I have to manually search it in blesta and than reply. It would be great to have a link to the ticket in the email. Quote Link to comment Share on other sites More sharing options...
Michael Posted June 23, 2014 Report Share Posted June 23, 2014 There is mate I use this template for ours: {ticket.details_html} To reply to this ticket, be sure to email {ticket.department_email} from the address we sent this notice to. You may also update the ticket in our support area at http://{update_ticket_url}. ---------------- Ticket ID: #{ticket.code} Priority: {ticket.priority} Status: {ticket.status} Last reply: {ticket.reply_by} Opened: {ticket.date_added} Ticket URL: {update_ticket_url} ---------------- If you mean the staff end you just reply to the email received and it will add it. ariq01 1 Quote Link to comment Share on other sites More sharing options...
kikloo Posted June 25, 2014 Report Share Posted June 25, 2014 Hi, Which template do I put it in ? If you're refering to Ticket recieved and ticket updated then they don't support that tags. How its working ? Thanks. Quote Link to comment Share on other sites More sharing options...
Michael Posted June 25, 2014 Report Share Posted June 25, 2014 That's in the update ticket one, not the staff update.Ticket Updated - - - Support Manager - - - Notice sent when a ticket is updated. Quote Link to comment Share on other sites More sharing options...
kikloo Posted June 25, 2014 Report Share Posted June 25, 2014 That's in the update ticket one, not the staff update. Ticket Updated - - - Support Manager - - - Notice sent when a ticket is updated. Says only these tags are available: {ticket} {update_ticket_url} {ticket_hash_code} Quote Link to comment Share on other sites More sharing options...
Michael Posted June 25, 2014 Report Share Posted June 25, 2014 Says only these tags are available: {ticket} {update_ticket_url} {ticket_hash_code} Oh yeah, ticket.whatevercode after works due to the ticket tag. ariq01 1 Quote Link to comment Share on other sites More sharing options...
Tyson Posted June 26, 2014 Report Share Posted June 26, 2014 Don't use {ticket} as a tag by itself. It should be obvious a ticket has many fields, such as {ticket.code} and {ticket.summary}, which you should use instead. Until we come up with a better way to display supported tags in the interface, you can check out the documentation for a list of all supported tags. Michael 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.