My 2 cents is we either keep Jira updates to dev@ list or as Ted mentioned maybe send emails only on create, and postpone issues@ list creation once we have everything setup or until Jira updates become too noisy in the dev@ list.
Creating issues@ list at this point i believe is too early. I am seeing good traffic of Jira updates that have not been noise in the dev@ list for now. On Wednesday, June 11, 2014, Ted Dunning <[email protected]> wrote: > JIRA can also be reconfigured to send only to dev@ on create. > > > > > On Wed, Jun 11, 2014 at 4:08 PM, Sean Owen <[email protected] > <javascript:;>> wrote: > > > I think it is helpful to separate automated test / commit > > notifications into a separate list, separate from even dev and user. > > Especially if there is no dev list, it's essential. I like issues@ > > myself as a place for automated notifications of all kinds. Later, > > consider a dev@ list if it's clear there is a lot of traffic that is > > not really user-relevant. > > > > On Wed, Jun 11, 2014 at 5:27 PM, Robert Metzger <[email protected] > <javascript:;>> > > wrote: > > > Hi, > > > > > > I wanted to ask if we should set up a [email protected] list? > > > It seems that JIRA is sending emails for every activity. And I think > our > > > activity in JIRA is pretty low currently, so the traffic is probably > > going > > > up in the future. > > > > > > Since we do not have a separate users@ and dev@ mailing list, I don't > > want > > > to scare away users that are just subscribed for support or because > they > > > are interested. > > > Or would it be more common to send the JIRA mails to > [email protected] > > ? > > > > > > What do you think? > > > > > > Robert > > >
