Customized email notifications from Jira +1. Jira notifications will be useful to some, but not all, so they should be opt-in rather than filter-out. I spend enough time filtering internal spam as is :/
On Thu, Oct 10, 2019 at 8:12 AM Chad Dombrova <chad...@gmail.com> wrote: > > > On Thu, Oct 10, 2019 at 10:56 AM Maximilian Michels <m...@apache.org> > wrote: > >> Our mailing list already has decent traffic. The current solution is >> better for its readability. People would simply adapt to more emails by >> creating a filter or ignoring them. > > > > +1. I find the dev generally informative, but as a part-time external > contributor open/close emails would detract from its usefulness for me. > > As an alternative to a dedicated mailing list for this purpose, we could > create a wiki article on how to setup customized email notifications from > Jira, with an example specifically for open/close events. That’s something > I might actually use, but only with additional filters like “sdk-python”. > > -chad > > > >> >> I know that the triaging of issues can be slow. How about a dedicated >> mailing for only open/close notifications, and a weekly / monthly >> summary of untriaged issues to the dev mailing list? >> >> Thanks, >> Max >> >> On 09.10.19 21:58, Thomas Weise wrote: >> > 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 <owenzhang1...@gmail.com >> > <mailto:owenzhang1...@gmail.com>> 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 <k...@apache.org >> > <mailto:k...@apache.org>> wrote: >> > >> > Currently, all email from JIRA goes to iss...@beam.apache.org >> > <mailto:iss...@beam.apache.org>. >> > >> > 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 >> > >> >
