On May 10, 2013 9:57 AM, "Alex Harui" <aha...@adobe.com> wrote: > > > > > On 5/10/13 6:26 AM, "Justin Mclean" <jus...@classsoftware.com> wrote: > > > Hi, > > > >> or I've lost my mind and it's sent to "dev@flex.apache.org" > > > > It's set to dev@flex.apache.org but it's from j...@flex.com.au, filter on the > > from address. Even web based client emails can do filtering so it's shouldn't > > be that hard. > > > While I agree that filtering should work, it is possible for us to request a > new mailing list. It requires a vote. > > But I think an important question is: should committers be allowed to > "ignore" JIRA emails? Sure, we can't control what you filter out from your > email client, but hopefully you will work on JIRA issues someday and will > want to see other folk's comments on those issues, even months after you > worked on it. Do we know if committers who don't sign up for JIRA emails > but "watch" JIRA issues they work on will still receive notification emails?
JIRA automatically adds a user to the watch list when they comment on an issue. That would ensure an email directly to their email if when there is some action on that ticket. One could manually choose to watch a ticket as well. > And if that does work, that might be better than having a client side filter > which might also filter the watch notification email? I believe so. Having a new mailing list will give us that benefit of not spamming the dev list. At the same time committers can choose to add themselves to the new list or just 'watch' the issues they care about. Personally, I think hard when I do bulk updates in JIRA with the fear of spamming the dev list. I ended up creating a filter on my gmail client, but now I have to remember to check that directory once every few days to make sure I don't miss some important ones(for me) Thanks, Om > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui >
