[Rt-commit] rt branch 5.0/clarify-emailsubjecttagregex-doc created. rt-5.0.3-471-g610f6a0efe

[BPS Git Server]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "rt".

The branch, 5.0/clarify-emailsubjecttagregex-doc has been created
        at  610f6a0efe6c8aa5ffa8762779cfcc2a2e407f83 (commit)

- Log -----------------------------------------------------------------
commit 610f6a0efe6c8aa5ffa8762779cfcc2a2e407f83
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Thu Apr 13 10:11:59 2023 -0400

    Clarify usage of the $EmailSubjectTagRegex setting

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index 59a34a4856..6f978bdc3f 100644
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -388,20 +388,29 @@ Set(@LogToSyslogConf, ());
 
 =item C<$EmailSubjectTagRegex>
 
-This regexp controls what subject tags RT recognizes as its own.  If
-you're not dealing with historical C<$rtname> values, or historical
-queue-specific subject tags, you'll likely never have to change this
-configuration.
+This setting allows you to customize the way RT evaluates email
+subject tags. RT uses subject tags to determine if an email should
+update a ticket in this RT instance.
 
-Be B<very careful> with it. Note that it overrides C<$rtname> for
-subject token matching.
+C<$EmailSubjectTagRegex> is most useful if you change your C<$rtname> setting,
+or change a queue-specific subject tag. In those cases, you can set
+this option to still match the old values, allowing replies to old email
+to still be recognized by this RT and get correctly routed to
+existing tickets.
 
-The setting below would make RT behave exactly as it does without the
-setting enabled.
+Note that it overrides the current C<$rtname> setting for subject
+token matching, so if you need to match and old value and also the
+new value, include C<$rtname> in your regex.
 
-=cut
+As an example, the setting below would make RT behave exactly as it
+does without the setting enabled.
+
+    Set($EmailSubjectTagRegex, qr/\Q$rtname\E/i );
+
+This would match email replies for an old queue-level subject tag
+called "Old Tag" that was changed:
 
-# Set($EmailSubjectTagRegex, qr/\Q$rtname\E/i );
+    Set($EmailSubjectTagRegex, qr/\Q$rtname\E|Old Tag/i);
 
 =item C<$OwnerEmail>
 

commit 0acdad13ff2066c2e2165682590c92327da01664
Merge: b64d8d4d75 db90da00f5
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Thu Apr 13 09:04:10 2023 -0400

    Merge branch '5.0/ignore-disabled-lifecycles-in-mapping-validation' into 5.0-trunk


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


hooks/post-receive
-- 
rt