I don't know about needing to create labels necessarily. By altering the e-mail template to include an additional table row (see attached image) I was able to have the e-mail send showing the URL:
However, it did not like using the %{ticket_URL} variable. Not sure if that's a valid variable name.
Hope this is what you were asking about.
The need for a dynamic label is when you use different help topics in opening a ticket, there are custom fields included. when the emails are sent. I wanted to include a label for the custom variables.Here's the scenario:assuming I open a ticket using the help topic "Domain issues", I have 2 custom variables called domain and url. using the "New Message Alert" template, I will be receiving an email containing the standard variable (show on the screenshots) plus the two variable values from %{ticket.domain} & %{ticket.url}Now, when I open another ticket using the help topic"Website Issues". I also have 2 custom variables called issues and request. using the "New Message Alert" template I will be receiving an email containing the standard variable (show on the screenshots) plus the two variable values I want to add %{ticket.issues} & %{ticket.request}When clients received different Message alerts with different help topics. It is difficult to identify, different custom fields without putting a label (e.g. ISSUES: %{ticket.issues} REQUEST: %{ticket.request} ). Putting a fixed label, would result in a wrong field value.
