Depends on JIRA volume, also. There are projects where the dev@ is heavily populated with create JIRA notifications (and other traffic goes under a bit).
I'm generally in favor of making the creation of JIRAs more visible. But if there isn't broad enough interest these notifications can still be surfaced individually by filtering. With "close" you probably mean resolved? That's kind of nice to know when something is complete, but I'm unsure if it should go to dev@, because create provided the opportunity for interested parties to watch the JIRA they care about. On Wed, Oct 9, 2019 at 8:58 PM Manu Zhang <[email protected]> wrote: > +1. Like the subscribe to only "close issue" action instead of each > comment on GitHub > > Manu > > On Thu, Oct 10, 2019 at 10:51 AM Kenneth Knowles <[email protected]> wrote: > >> Currently, all email from JIRA goes to [email protected]. >> >> I just learned that HBase has a JIRA configuration so that issue >> open/close goes to dev@ and every other notification goes to issues@. >> That actually seems nice for involving all of the community in new issue >> triage and also closed issue verification/notification. >> >> What do you think about such a system? >> >> Kenn >> >
