From bloodhound-dev-return-791-apmail-incubator-bloodhound-dev-archive=incubator.apache.org@incubator.apache.org Wed Sep 26 12:54:07 2012 Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A8E1FD296 for ; Wed, 26 Sep 2012 12:54:07 +0000 (UTC) Received: (qmail 17827 invoked by uid 500); 26 Sep 2012 12:54:07 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 17770 invoked by uid 500); 26 Sep 2012 12:54:07 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 17761 invoked by uid 99); 26 Sep 2012 12:54:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 12:54:06 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gary.martin@wandisco.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Sep 2012 12:53:59 +0000 Received: by bkcjk7 with SMTP id jk7so270174bkc.6 for ; Wed, 26 Sep 2012 05:53:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=P+Cvo6stOhimyrcT1ppcufg2An9sCkYVdaARt4dxEUc=; b=p23IDlASSpTJFObbud87wkeuEF3fmEDCSxTYnJtyXgV8wovppyACBZjsMWdQtzh8N3 Tn9M38wR3gLlT3xLp1fXA1N8p5wjcAVenDD7bTLzGd6V1tO3gHYMfMcS9l+VOO42muLl i+Av5kIRHgUSkwCevcvZT4sjPMmNwxno3wyYEokRyWIuSUtJSIzW224JRYDljOtOdgi4 9vAV04pVjenQPVHx1PgvpHtnrYHGeZL3j/Iz6r8ldGm4CrP23RiZ2Ps6zzjWWh7W2Ijc ZcMtgaHnjgcNgihoXAQvux7wjpte0/W6HZn00WcoXIvZNZvZVtKy4VpbQfe6ERLzqcgB EjoQ== Received: by 10.204.152.137 with SMTP id g9mr362104bkw.106.1348664017079; Wed, 26 Sep 2012 05:53:37 -0700 (PDT) Received: from [10.2.5.205] ([77.86.30.139]) by mx.google.com with ESMTPS id d13sm2362932bkw.12.2012.09.26.05.53.35 (version=SSLv3 cipher=OTHER); Wed, 26 Sep 2012 05:53:36 -0700 (PDT) Message-ID: <5062FACE.8030303@wandisco.com> Date: Wed, 26 Sep 2012 13:53:34 +0100 From: Gary Martin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: bloodhound-dev@incubator.apache.org Subject: Re: [Apache Bloodhound] #210: Cleverer ticket CC behaviour References: <055.b50dbb0224108ed543de19d326c4d3ad@incubator.apache.org> <070.338933cccbb21f46678da17c1216d2e6@incubator.apache.org> <5062CC30.5050208@wandisco.com> <5062CD74.4030304@wandisco.com> <5062D136.1030306@wandisco.com> <5062D3C9.5000208@wandisco.com> <5062F9CC.9070606@wandisco.com> In-Reply-To: <5062F9CC.9070606@wandisco.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Gm-Message-State: ALoCoQkpUqNd0abZixl5XyK5IY7n0AozkeMnwfq7SgdWh70EehXuy1ffmh8U/Emg7F26vSTuX70D Of course, I should test whether changing always_notify_updater is actually enough. On 26/09/12 13:49, Gary Martin wrote: > If the current set of configuration options are enough to achieve the > aim then we can update the base.ini to include this. I suspect that it > will take more work to achieve this. > > I would be happy to see this ticket split into global and user > preferences. > > Cheers, > Gary > > > On 26/09/12 13:22, Joachim Dreimann wrote: >> I agree with Brane's suggestion for the defaults. We could set these >> defaults now and deal with the notification system configured by >> individual users with a further ticket, as that likely requires much >> more >> in depth work. >> >> - Joe >> >> On 26 September 2012 11:14, Mat Booth wrote: >> >>> On 26 September 2012 11:07, Branko Čibej wrote: >>> >>>> This is not something you'll figure out without a) getting user >>>> feedback, or b) looking at the competition. AFAICR, both Jira, Redmina >>>> and Bugzilla all default to not sending notifications about stuff >>>> you've >>>> just done in the UI. >>>> >>> Indeed. Just to re-iterate my last comment on the ticket: >>> >>> Probably the notification system wants re-working to expose >>> notification >>> settings to users instead of them being globally enforced. Something >>> like >>> (but probably not as complex as) what Bugzilla does: >>> http://fedorapeople.org/~mbooth/BugzillaEmail.png >>> >>> >>> >>>> Trying to make the defaults perfect for everybody is an exercise in >>>> futility. And whatever you do, you'll only hear complaints from the >>>> vocal minority. :) >>>> >>>> -- Brane >>>> >>>> On 26.09.2012 11:56, Gary Martin wrote: >>>>> I wonder if in this case it might be better for initial configuration >>>>> to send by default in both cases, but mitigate this by providing an >>>>> appropriate direct link to help users adjust the behaviour. I'm >>>>> trying >>>>> to weigh up whether it would be a pity for a user to miss emails that >>>>> were actually wanted against annoyance at any perceived spamming. >>>>> >>>>> Cheers, >>>>> Gary >>>>> >>>>> >>>>> On 26/09/12 10:40, Branko Čibej wrote: >>>>>> This is something that should IMO be configurable. I suggest sane >>>>>> defaults are: >>>>>> >>>>>> * if ticket is changed via the Web UI, do not send notification; >>>>>> * if its changed via e-mail, do send notification (that's >>> essentially >>>>>> an e-mail receipt). >>>>>> >>>>>> However, both cases should be user-configurable, preferably >>> per-project >>>>>> and per ticket (workflow) type and eventually possibly even per >>> workflow >>>>>> transition. >>>>>> >>>>>> -- Brane >>>>>> >>>>>> >>>>>> On 26.09.2012 11:34, Gary Martin wrote: >>>>>>> Hi, >>>>>>> >>>>>>> I thought that this ticket might be worth discussing here if anyone >>>>>>> has any interest in it: >>>> https://issues.apache.org/bloodhound/ticket/210 >>>>>>> Essentially it arises from a complaint that a user might not >>>>>>> want to >>>>>>> receive a notification email when they have made a change to a >>> ticket. >>>>>>> Cheers, >>>>>>> Gary >>>>>>> >>>>>>> On 26/09/12 10:21, Apache Bloodhound wrote: >>>>>>>> #210: Cleverer ticket CC behaviour >>>>>>>> --------------------------+-------------------- >>>>>>>> Reporter: mbooth | Owner: nobody >>>>>>>> Type: enhancement | Status: new >>>>>>>> Priority: major | Milestone: >>>>>>>> Component: trac core | Version: 1.0 >>>>>>>> Resolution: | Keywords: >>>>>>>> --------------------------+-------------------- >>>>>>>> >>>>>>>> Comment (by mbooth): >>>>>>>> >>>>>>>> Probably the notification system wants re-working to expose >>>>>>>> notification >>>>>>>> settings to users instead of them being globally enforced. >>>>>>>> Something like >>>>>>>> (but maybe not as complex as) what Bugzilla does: >>>>>>>> http://fedorapeople.org/~mbooth/BugzillaEmail.png >>>>>>>> >>>> >>>> -- >>>> Certified & Supported Apache Subversion Downloads: >>>> http://www.wandisco.com/subversion/download >>>> >>>> >>> >>> -- >>> Mat Booth >>> Software Engineer >>> WANdisco, Inc. >>> http://www.wandisco.com >>> >