[Rt-commit] rt branch, 4.2-trunk, updated. rt-4.2.13-131-g12b5adc
Shawn Moore
shawn at bestpractical.com
Thu May 25 11:32:44 EDT 2017
The branch, 4.2-trunk has been updated
via 12b5adcef50fde3c9744edf0cf0f8ea4acb83f7b (commit)
via 6dd3fbdc8c9ae28048e978d1c6154ea616fbf002 (commit)
from ba6ec8faea8146e1a53a62e949a4ca90c3bdee90 (commit)
Summary of changes:
docs/format-strings.pod | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
- Log -----------------------------------------------------------------
commit 6dd3fbdc8c9ae28048e978d1c6154ea616fbf002
Author: Richard Poole <richard at 2ndQuadrant.com>
Date: Thu May 25 11:30:13 2017 -0400
add brief documentation for custom fields in format strings
diff --git a/docs/format-strings.pod b/docs/format-strings.pod
index 6040d74..ff322a7 100644
--- a/docs/format-strings.pod
+++ b/docs/format-strings.pod
@@ -95,6 +95,26 @@ quotes and underscores can be omitted. That is, the format:
id, Subject
+=item Custom fields
+
+If you have created custom fields applied to tickets, you can refer to
+them using C< CF. >. For example, if you have a custom field named
+C<Component>, you could use a format like:
+
+ '__id__', '__Subject__', 'CF.Component'
+
+or:
+
+ '__id__', '__Subject__', '__CustomField.{Component}__'
+
+Alternatively, you can use the custom field's numeric ID instead of its
+name. This is mostly useful if you have multiple custom fields with the
+same name and you need to disambiguate.
+
+ '__id__', '__Subject__', 'CF.3'
+
+ '__id__', '__Subject__', '__CustomField.{3}__'
+
=item HTML
HTML formatting can be included, which will by default be included in
commit 12b5adcef50fde3c9744edf0cf0f8ea4acb83f7b
Merge: ba6ec8f 6dd3fbd
Author: Shawn M Moore <shawn at bestpractical.com>
Date: Thu May 25 11:31:46 2017 -0400
Merge branch '4.2/cf-format-doc' into 4.2-trunk
-----------------------------------------------------------------------
More information about the rt-commit
mailing list