incubator-bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joachim Dreimann <joachim.dreim...@wandisco.com>
Subject Re: [Apache Bloodhound] #210: Cleverer ticket CC behaviour
Date Wed, 26 Sep 2012 12:22:42 GMT
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 <mat.booth@wandisco.com> wrote:

> On 26 September 2012 11:07, Branko ─îibej <brane@wandisco.com> 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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message