That's great! I wonder if we have that feature turned on in the ASF
installation....
Craig Blake wrote:
One of the cooler Jira features is the mailing list integration. You
can subscribe it to the mailing list, after which it will automatically
scan email subjects for issue identifiers (i.e. HARMONY-xxxx) and add
the email content as a comment to the referenced issue, including
attachments. That might make it easier to maintain discussion on the
list and have it propagated into JIRA rather than the other way around,
if that's the way people want to go.
http://www.atlassian.com/software/jira/docs/latest/issue_creation_email.html
Craig
On Mar 7, 2006, at 10:48 AM, Tim Ellison wrote:
Geir Magnusson Jr wrote:
Tim Ellison wrote:
Is there some way to teach JIRA not to send so much mail?
Stop using it as a chat room. :)
So what is the right way to use JIRA?
- people open an issue,
- maybe comment with a test case
- maybe attach a patch or two
- I may comment on the issue, with comments that are relevant to that
specific issue
- when I work on it I assign it to me, and say progress started
- when I'm done I resolve it
- when the reporter has verified it they comment to say so
- I close it as verified
What steps should I stop doing?
Every state change produces mail to the world - even though it is
likely
only of interest to the reporter, assignee, and watchers. i.e. any way
to solve the problem rather than move it ;-)
Every change should be visible to everyone for maximum transparency, or
so I believe. It would be a pain in the rear if one had to explicitly
sign up for each jira one was interested in.
Some people say every JIRA state change / comment is too much 'spam' --
you want to see them all ...
That said, once the VM activity gets really honking, we'll probably need
a second stream for those...
Not sure why the VM is special here.
Regards,
Tim
Leo Simons wrote:
Taking care of this now...
I will note that this makes it even more important for committers and
active contributors to subscribe to the commits mailing list - a
lot of
important information is in those jira messages.
I will also note that it *also* makes it even more important that Jira
is not used for discussion - that really needs to happen here on the
mailing list where everyone can track it. The ASF has had some bad
experience in the past with too much communication going via the issue
tracker; this isn't so much a guideline as it is a pretty hard
requirement.
- Leo
On Tue, Mar 07, 2006 at 08:17:45AM -0600, Archie Cobbs wrote:
Mark Hindess wrote:
Geir, There are quite a lot of JIRA messages these days, perhaps it
is time to split the JIRA traffic to a separate list with a reply-to
set to harmony-dev. Or perhaps just have them sent to the commit
list?
Yes, please... +1e6
-Archie
--
Tim Ellison ([EMAIL PROTECTED])
IBM Java technology centre, UK.
