Commit b85f1687 authored by Kevin Falcone's avatar Kevin Falcone
Browse files

Merge branch '3.0/subjecttag' into 3.0-trunk

parents ccac566d 326ba231
......@@ -64,6 +64,6 @@ Find all templates with the following text:
And replace it with:
[{$Ticket->QueueObj->SubjectTag || $rtname} #{$Ticket->id}]
[{$Ticket->SubjectTag} #{$Ticket->id}]
=cut
......@@ -169,7 +169,22 @@ Tools -> Configuration -> Queues -> Investigations -> Scrips with:
Template: Global Template: Correspondence
=head1 UPGRADING FROM 3.0.0 AND EARLIER
=head2 SubjectTag corrections
During the upgrade from 2.4 to 2.6, instructions were provided to begin including
Queue SubjectTags in outgoing mail. New installs of 2.6.0 also used SubjectTags in
templates. However, they suggested an old-style
[{$Ticket->QueueObj->SubjectTag || $rtname} #{$Ticket->id}]
Instead, you should use the more modern
[{$Ticket->SubjectTag} #{$Ticket->id}]
Because correspondence templates are frequently modified, it is
not practical to script updates and they will need to be done
through the UI.
=cut
......@@ -420,7 +420,7 @@ Subject: { $Ticket->Subject }
-------------------------------------------------------------------------
Please include the string:
[{ $Ticket->QueueObj->SubjectTag || $rtname } #{ $Ticket->id }]
[{ $Ticket->SubjectTag } #{ $Ticket->id }]
in the subject line of all future correspondence about this issue. To do so,
you may reply to this message.
......@@ -452,7 +452,7 @@ Block #{$Ticket->id} was removed.
-------------------------------------------------------------------------
Please include the string:
[{ $Ticket->QueueObj->SubjectTag || $rtname } #{$Ticket->id}]
[{ $Ticket->SubjectTag } #{$Ticket->id}]
in the subject line of all future correspondence about this issue. To do so,
you may reply to this message.
......@@ -470,7 +470,7 @@ Subject: {$Ticket->Subject}
-------------------------------------------------------------------------
Please include the string:
[{ $Ticket->QueueObj->SubjectTag || $rtname } #{$Ticket->id}]
[{ $Ticket->SubjectTag } #{$Ticket->id}]
in the subject line of all future correspondence about this issue. To do so,
you may reply to this message.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment