From 9096dfc7742a738b17fc55484b49ae4ceab4224b Mon Sep 17 00:00:00 2001 From: Tim Abbott Date: Sat, 9 Jan 2016 20:21:31 -0800 Subject: [PATCH] trac: Cleanup documentation of TRAC_NOTIFY_FIELDS. --- integrations/trac/zulip_trac_config.py | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/integrations/trac/zulip_trac_config.py b/integrations/trac/zulip_trac_config.py index 753c1d1..aa6b2b1 100644 --- a/integrations/trac/zulip_trac_config.py +++ b/integrations/trac/zulip_trac_config.py @@ -34,13 +34,13 @@ TRAC_BASE_TICKET_URL = "https://trac.example.com/ticket" # and annoying. We solve this issue by only sending a notification # for changes to the fields listed below. # -# Total list of possible fields is: +# TRAC_NOTIFY_FIELDS lets you specify which fields will trigger a +# Zulip notification in response to a trac update; you should change +# this list to match your team's workflow. The complete list of +# possible fields is: +# # (priority, milestone, cc, owner, keywords, component, severity, # type, versions, description, resolution, summary, comment) -# -# The following is the list of fields which can be changed without -# triggering a Zulip notification; change these to match your team's -# workflow. TRAC_NOTIFY_FIELDS = ["description", "summary", "resolution", "comment", "owner"] ## If properly installed, the Zulip API should be in your import