Travis Vitek wrote:
Farid Zaripov-2 wrote:
Travis Vitek wrote:
I have no objections. Either way, I need to look at both sets
of messages regardless of where they come from. So, for me,
moving the Jira messages to a new -issues list doesn't have
any significant impact.
I guess it might be useful for users with 'dumb' e-mail
clients that don't have proper message filtering.
My +1 for the change.
I'm using the MS Outlook and filtering the JIRA messages by the
"[jira]"
in subject. But any reply to jira messages with "Re: [jira]" in subject
are
filtered also :( And Outlook dosn't provide the possibility to make more
flexible rule :(
Farid.
I don't know how the infra group will set this up, but I wouldn't expect the
addition of a new list to fix this problem for you. All generated messages
from jira would come from the user that modified the case and be sent to the
[EMAIL PROTECTED] list. Any response would appear the same. This is
how it works now.
This, btw., is pretty extensively configurable in Jira. stdcxx
is subject to the STDCXX notifications Scheme that I set up for
us back in 2005 when our Jira was first created.
The latest documentation that explains how this works is here:
http://www.atlassian.com/software/jira/docs/latest/notification_schemes.html
I suspect you may not be able to view the stdcxx notifications
page w/o Jira admin access but here it is anyway:
https://issues.apache.org/jira/secure/admin/EditNotifications!default.jspa?schemeId=12310060
Here's our current setup for those who can't access the page,
with Events first and the set of available Notifications below
(defaults in parens):
Issue Created (System)
* Reporter
* Single Email Address (stdcxx-dev@incubator.apache.org)
Issue Updated (System)
* Reporter
* Current Assignee
* Single Email Address (stdcxx-dev@incubator.apache.org)
* All Watchers
Issue Assigned (System)
* All Watchers
* Single Email Address (stdcxx-dev@incubator.apache.org)
Issue Resolved (System)
* Current Assignee
* All Watchers
* Reporter
* Single Email Address (stdcxx-dev@incubator.apache.org)
Issue Closed (System)
* All Watchers
* Current Assignee
* Single Email Address (stdcxx-dev@incubator.apache.org)
* Reporter
Issue Commented (System)
* Reporter
* Current Assignee
* All Watchers
* Single Email Address (stdcxx-dev@incubator.apache.org)
Issue Comment Edited (System)
* Current Assignee
* Reporter
* Single Email Address (stdcxx-dev@incubator.apache.org)
* All Watchers
Issue Reopened (System)
* Single Email Address (stdcxx-dev@incubator.apache.org)
* Reporter
* All Watchers
* Current Assignee
Issue Deleted (System)
* Single Email Address (stdcxx-dev@incubator.apache.org)
Issue Moved (System)
* Single Email Address (stdcxx-dev@incubator.apache.org)
Work Logged On Issue (System)
Work Started On Issue (System)
Work Stopped On Issue (System)
Issue Worklog Updated (System)
Issue Worklog Deleted (System)
Generic Event (System)
Also, I believe that Outlook rules allow you to make a rule handle this
situation. You just add an exception to your rule that checks for the
strings "RE:" or "Re:".
Travis
