Jump to content
  • 0

Ticket Subject & Reference


serge

Question

It's normal to receive Ticket by email having this kind of structure reference in subject.

------------

Update to Ticket #5131426 -aa73-

----------

and at every ticket update last 4 string change slightly.

 

I'm surprised because from Blesta interface (admin or client), the ticket reference is shorter, only this: 5131426

 

It's normal?

Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 0

ok, thank you for explaination. So it was normal, good!

 

Strangelly I tried with same subject field as you (without Licensecart of course) but it's still using previous value even after clear Blesta cache, when even in database at table email It's well the update value in the email subject but that is not a real issue

 

It should happen to new tickets :) customer side only.

 

If you are doing the staff side you could do with:

Licensecart {ticket.department_name} - Update to Ticket {ticket.code} - Priority: {ticket.priority}

Link to comment
Share on other sites

  • 0

It's normal to receive Ticket by email having this kind of structure reference in subject.

------------

Update to Ticket #5131426 -aa73-

----------

and at every ticket update last 4 string change slightly.

 

I'm surprised because from Blesta interface (admin or client), the ticket reference is shorter, only this: 5131426

 

It's normal?

 

The hash is a reference to the ticket, and the Ticket# number is the ticket number.

I have: Licensecart {ticket.department_name} - Opened ticket #{ticket.code} [{ticket_hash_code}]

And: Licensecart {ticket.department_name} - #{ticket.code} has been updated. [{ticket_hash_code}]

 

Eg: Licensecart Sales Enquires - #123456 has been updated [-ab43-]

Link to comment
Share on other sites

  • 0

ok, thank you for explaination. So it was normal, good!

 

Strangelly I tried with same subject field as you (without Licensecart of course) but it's still using previous value even after clear Blesta cache, when even in database at table email It's well the update value in the email subject but that is not a real issue

Link to comment
Share on other sites

  • 0

ok, I got it, I  well made update at client email template subject VS staff version, but I done my test by sending email from a client's email software & using same email account as blesta admin, so when re-doing the test from an other email, it's was working as expected, or maybe my cache was a little persistent before that.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...