You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by Erik Weathers <ew...@groupon.com> on 2015/09/22 02:15:31 UTC
does anyone else hate the verbose logging of all PR comments in the
Storm JIRAs?
I find that these comments majorly distract from any discussion that may
occur in the JIRA issues themselves. What value are these providing? I
guess just insurance against GitHub being unavailable or going away? But
that doesn't seem worth the distraction cost. Is there any possibility of
removing this spamminess, or somehow putting them into attachments within
the JIRA issues so that they aren't directly in the comments?
- Erik
Re: does anyone else hate the verbose logging of all PR comments in
the Storm JIRAs?
Posted by Erik Weathers <ew...@groupon.com.INVALID>.
Yay, I have one convert to my perspective! ;-)
The emails are less annoying to me than the dilution / hiding of manual
comments within the JIRA tickets.
- Erik
On Sun, May 15, 2016 at 7:24 PM, Jungtaek Lim <ka...@gmail.com> wrote:
> Moving opinions from other thread,
>
> Abhishek
>
> 3* - I also get one extra email from notifications@github.com if I am
> participating in a pull request from notifications@github.com. It will be
> great to avoid that as well. By the way, removing notifications from Github
> means that PRs with no JIRA id might go unnoticed for long time.
>
> Harsha
>
> -1 to what Abhishek said. notifications important for everyone else. if you
> are getting
> spammed by this create a mail rule.
>
> Aaron
>
> 3* Agree that limiting duplicate emails would be good.
>
> Thanks,
> Jungtaek Lim (HeartSaVioR)
>
> 2016년 5월 16일 (월) 오전 11:23, Jungtaek Lim <ka...@gmail.com>님이 작성:
>
> > This thread was forgotten, and I think I was wrong since I also hate the
> > verbose logging now :)
> >
> > I'm clicking two mails for one new comment from github, which is really
> > bad.
> > I strongly agree with Erik, and linking github PR with JIRA is enough for
> > me.
> >
> > 2015년 9월 22일 (화) 오후 6:06, 임정택 <ka...@gmail.com>님이 작성:
> >
> >> Matthias,
> >> Personally I can't turn off github notification because of I'm also
> >> collaborator of Jedis, which repository is belong to Github. ;(
> >>
> >> I just wish to reduce notifications via same event (Github event &
> >> JIRA automatic posting) from dev. mailing list.
> >> Actually I don't have strong opinion about this. Just a wish. :)
> >>
> >>
> >> 2015-09-22 17:23 GMT+09:00 Matthias J. Sax <mj...@apache.org>:
> >>
> >>> On Github, you can disable mail notification about each comment in your
> >>> profile configuration (at least for you personal email address -- I
> >>> guess it still goes over the mailing list)
> >>>
> >>> Profile -> Settings -> Notification Center
> >>>
> >>> -Matthias
> >>>
> >>> On 09/22/2015 03:21 AM, Erik Weathers wrote:
> >>> > Sure, STORM-*. ;-)
> >>> >
> >>> > Here's a good example:
> >>> >
> >>> > - https://issues.apache.org/jira/browse/STORM-329
> >>> >
> >>> > Compare that to this one:
> >>> >
> >>> > - https://issues.apache.org/jira/browse/STORM-404
> >>> >
> >>> > STORM-404 has a bunch of human-created comments, but it's readable
> >>> since it
> >>> > has no github-generated comments. STORM-329 however intermixes the
> >>> human
> >>> > comments with the github ones. It's really hard to read through.
> >>> >
> >>> > To be clear, it's not that it's *confusing* per se -- it's that the
> >>> > behavior is *cluttering* the comments, making it harder to see any
> >>> > human-created comments since any JIRA issue with a PR will usually
> end
> >>> up
> >>> > with many automated comments.
> >>> >
> >>> > BTW, I totally agree that linking from the JIRA issue to the github
> PR
> >>> is
> >>> > important! Would be even nicer if the github PRs also directly
> linked
> >>> back
> >>> > to the JIRA issue with a clickable link.
> >>> >
> >>> > - Erik
> >>> >
> >>> > On Mon, Sep 21, 2015 at 6:03 PM, 임정택 <ka...@gmail.com> wrote:
> >>> >
> >>> >> Hi Erik,
> >>> >>
> >>> >> I think verbose logging of PR comments could be OK. I didn't
> >>> experience any
> >>> >> confusing.
> >>> >> Maybe referring sample JIRA issues could help us to understand.
> >>> >>
> >>> >> But I'm also open to change cause other projects already have been
> >>> doing.
> >>> >> (for example, https://issues.apache.org/jira/browse/SPARK-10474)
> >>> >>
> >>> >> In addition to SPARK has been doing, I'd like to still leave some
> >>> events on
> >>> >> github PR to JIRA issue, too.
> >>> >>
> >>> >> Btw, the thing I'm really annoyed is multiple mail notifications on
> >>> each
> >>> >> github comment.
> >>> >>
> >>> >> Thanks,
> >>> >> Jungtaek Lim (HeartSaVioR)
> >>> >>
> >>> >> 2015-09-22 9:15 GMT+09:00 Erik Weathers <ew...@groupon.com>:
> >>> >>
> >>> >>> I find that these comments majorly distract from any discussion
> that
> >>> may
> >>> >>> occur in the JIRA issues themselves. What value are these
> >>> providing? I
> >>> >>> guess just insurance against GitHub being unavailable or going
> >>> away? But
> >>> >>> that doesn't seem worth the distraction cost. Is there any
> >>> possibility
> >>> >> of
> >>> >>> removing this spamminess, or somehow putting them into attachments
> >>> within
> >>> >>> the JIRA issues so that they aren't directly in the comments?
> >>> >>>
> >>> >>> - Erik
> >>> >>>
> >>> >>
> >>> >>
> >>> >>
> >>> >> --
> >>> >> Name : 임 정택
> >>> >> Blog : http://www.heartsavior.net / http://dev.heartsavior.net
> >>> >> Twitter : http://twitter.com/heartsavior
> >>> >> LinkedIn : http://www.linkedin.com/in/heartsavior
> >>> >>
> >>> >
> >>>
> >>>
> >>
> >>
> >> --
> >> Name : 임 정택
> >> Blog : http://www.heartsavior.net / http://dev.heartsavior.net
> >> Twitter : http://twitter.com/heartsavior
> >> LinkedIn : http://www.linkedin.com/in/heartsavior
> >>
> >
>
Re: does anyone else hate the verbose logging of all PR comments in
the Storm JIRAs?
Posted by Jungtaek Lim <ka...@gmail.com>.
Moving opinions from other thread,
Abhishek
3* - I also get one extra email from notifications@github.com if I am
participating in a pull request from notifications@github.com. It will be
great to avoid that as well. By the way, removing notifications from Github
means that PRs with no JIRA id might go unnoticed for long time.
Harsha
-1 to what Abhishek said. notifications important for everyone else. if you
are getting
spammed by this create a mail rule.
Aaron
3* Agree that limiting duplicate emails would be good.
Thanks,
Jungtaek Lim (HeartSaVioR)
2016년 5월 16일 (월) 오전 11:23, Jungtaek Lim <ka...@gmail.com>님이 작성:
> This thread was forgotten, and I think I was wrong since I also hate the
> verbose logging now :)
>
> I'm clicking two mails for one new comment from github, which is really
> bad.
> I strongly agree with Erik, and linking github PR with JIRA is enough for
> me.
>
> 2015년 9월 22일 (화) 오후 6:06, 임정택 <ka...@gmail.com>님이 작성:
>
>> Matthias,
>> Personally I can't turn off github notification because of I'm also
>> collaborator of Jedis, which repository is belong to Github. ;(
>>
>> I just wish to reduce notifications via same event (Github event &
>> JIRA automatic posting) from dev. mailing list.
>> Actually I don't have strong opinion about this. Just a wish. :)
>>
>>
>> 2015-09-22 17:23 GMT+09:00 Matthias J. Sax <mj...@apache.org>:
>>
>>> On Github, you can disable mail notification about each comment in your
>>> profile configuration (at least for you personal email address -- I
>>> guess it still goes over the mailing list)
>>>
>>> Profile -> Settings -> Notification Center
>>>
>>> -Matthias
>>>
>>> On 09/22/2015 03:21 AM, Erik Weathers wrote:
>>> > Sure, STORM-*. ;-)
>>> >
>>> > Here's a good example:
>>> >
>>> > - https://issues.apache.org/jira/browse/STORM-329
>>> >
>>> > Compare that to this one:
>>> >
>>> > - https://issues.apache.org/jira/browse/STORM-404
>>> >
>>> > STORM-404 has a bunch of human-created comments, but it's readable
>>> since it
>>> > has no github-generated comments. STORM-329 however intermixes the
>>> human
>>> > comments with the github ones. It's really hard to read through.
>>> >
>>> > To be clear, it's not that it's *confusing* per se -- it's that the
>>> > behavior is *cluttering* the comments, making it harder to see any
>>> > human-created comments since any JIRA issue with a PR will usually end
>>> up
>>> > with many automated comments.
>>> >
>>> > BTW, I totally agree that linking from the JIRA issue to the github PR
>>> is
>>> > important! Would be even nicer if the github PRs also directly linked
>>> back
>>> > to the JIRA issue with a clickable link.
>>> >
>>> > - Erik
>>> >
>>> > On Mon, Sep 21, 2015 at 6:03 PM, 임정택 <ka...@gmail.com> wrote:
>>> >
>>> >> Hi Erik,
>>> >>
>>> >> I think verbose logging of PR comments could be OK. I didn't
>>> experience any
>>> >> confusing.
>>> >> Maybe referring sample JIRA issues could help us to understand.
>>> >>
>>> >> But I'm also open to change cause other projects already have been
>>> doing.
>>> >> (for example, https://issues.apache.org/jira/browse/SPARK-10474)
>>> >>
>>> >> In addition to SPARK has been doing, I'd like to still leave some
>>> events on
>>> >> github PR to JIRA issue, too.
>>> >>
>>> >> Btw, the thing I'm really annoyed is multiple mail notifications on
>>> each
>>> >> github comment.
>>> >>
>>> >> Thanks,
>>> >> Jungtaek Lim (HeartSaVioR)
>>> >>
>>> >> 2015-09-22 9:15 GMT+09:00 Erik Weathers <ew...@groupon.com>:
>>> >>
>>> >>> I find that these comments majorly distract from any discussion that
>>> may
>>> >>> occur in the JIRA issues themselves. What value are these
>>> providing? I
>>> >>> guess just insurance against GitHub being unavailable or going
>>> away? But
>>> >>> that doesn't seem worth the distraction cost. Is there any
>>> possibility
>>> >> of
>>> >>> removing this spamminess, or somehow putting them into attachments
>>> within
>>> >>> the JIRA issues so that they aren't directly in the comments?
>>> >>>
>>> >>> - Erik
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Name : 임 정택
>>> >> Blog : http://www.heartsavior.net / http://dev.heartsavior.net
>>> >> Twitter : http://twitter.com/heartsavior
>>> >> LinkedIn : http://www.linkedin.com/in/heartsavior
>>> >>
>>> >
>>>
>>>
>>
>>
>> --
>> Name : 임 정택
>> Blog : http://www.heartsavior.net / http://dev.heartsavior.net
>> Twitter : http://twitter.com/heartsavior
>> LinkedIn : http://www.linkedin.com/in/heartsavior
>>
>
Re: does anyone else hate the verbose logging of all PR comments in
the Storm JIRAs?
Posted by Jungtaek Lim <ka...@gmail.com>.
This thread was forgotten, and I think I was wrong since I also hate the
verbose logging now :)
I'm clicking two mails for one new comment from github, which is really bad.
I strongly agree with Erik, and linking github PR with JIRA is enough for
me.
2015년 9월 22일 (화) 오후 6:06, 임정택 <ka...@gmail.com>님이 작성:
> Matthias,
> Personally I can't turn off github notification because of I'm also
> collaborator of Jedis, which repository is belong to Github. ;(
>
> I just wish to reduce notifications via same event (Github event &
> JIRA automatic posting) from dev. mailing list.
> Actually I don't have strong opinion about this. Just a wish. :)
>
>
> 2015-09-22 17:23 GMT+09:00 Matthias J. Sax <mj...@apache.org>:
>
>> On Github, you can disable mail notification about each comment in your
>> profile configuration (at least for you personal email address -- I
>> guess it still goes over the mailing list)
>>
>> Profile -> Settings -> Notification Center
>>
>> -Matthias
>>
>> On 09/22/2015 03:21 AM, Erik Weathers wrote:
>> > Sure, STORM-*. ;-)
>> >
>> > Here's a good example:
>> >
>> > - https://issues.apache.org/jira/browse/STORM-329
>> >
>> > Compare that to this one:
>> >
>> > - https://issues.apache.org/jira/browse/STORM-404
>> >
>> > STORM-404 has a bunch of human-created comments, but it's readable
>> since it
>> > has no github-generated comments. STORM-329 however intermixes the
>> human
>> > comments with the github ones. It's really hard to read through.
>> >
>> > To be clear, it's not that it's *confusing* per se -- it's that the
>> > behavior is *cluttering* the comments, making it harder to see any
>> > human-created comments since any JIRA issue with a PR will usually end
>> up
>> > with many automated comments.
>> >
>> > BTW, I totally agree that linking from the JIRA issue to the github PR
>> is
>> > important! Would be even nicer if the github PRs also directly linked
>> back
>> > to the JIRA issue with a clickable link.
>> >
>> > - Erik
>> >
>> > On Mon, Sep 21, 2015 at 6:03 PM, 임정택 <ka...@gmail.com> wrote:
>> >
>> >> Hi Erik,
>> >>
>> >> I think verbose logging of PR comments could be OK. I didn't
>> experience any
>> >> confusing.
>> >> Maybe referring sample JIRA issues could help us to understand.
>> >>
>> >> But I'm also open to change cause other projects already have been
>> doing.
>> >> (for example, https://issues.apache.org/jira/browse/SPARK-10474)
>> >>
>> >> In addition to SPARK has been doing, I'd like to still leave some
>> events on
>> >> github PR to JIRA issue, too.
>> >>
>> >> Btw, the thing I'm really annoyed is multiple mail notifications on
>> each
>> >> github comment.
>> >>
>> >> Thanks,
>> >> Jungtaek Lim (HeartSaVioR)
>> >>
>> >> 2015-09-22 9:15 GMT+09:00 Erik Weathers <ew...@groupon.com>:
>> >>
>> >>> I find that these comments majorly distract from any discussion that
>> may
>> >>> occur in the JIRA issues themselves. What value are these
>> providing? I
>> >>> guess just insurance against GitHub being unavailable or going away?
>> But
>> >>> that doesn't seem worth the distraction cost. Is there any
>> possibility
>> >> of
>> >>> removing this spamminess, or somehow putting them into attachments
>> within
>> >>> the JIRA issues so that they aren't directly in the comments?
>> >>>
>> >>> - Erik
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Name : 임 정택
>> >> Blog : http://www.heartsavior.net / http://dev.heartsavior.net
>> >> Twitter : http://twitter.com/heartsavior
>> >> LinkedIn : http://www.linkedin.com/in/heartsavior
>> >>
>> >
>>
>>
>
>
> --
> Name : 임 정택
> Blog : http://www.heartsavior.net / http://dev.heartsavior.net
> Twitter : http://twitter.com/heartsavior
> LinkedIn : http://www.linkedin.com/in/heartsavior
>
Re: does anyone else hate the verbose logging of all PR comments in
the Storm JIRAs?
Posted by 임정택 <ka...@gmail.com>.
Matthias,
Personally I can't turn off github notification because of I'm also
collaborator of Jedis, which repository is belong to Github. ;(
I just wish to reduce notifications via same event (Github event &
JIRA automatic posting) from dev. mailing list.
Actually I don't have strong opinion about this. Just a wish. :)
2015-09-22 17:23 GMT+09:00 Matthias J. Sax <mj...@apache.org>:
> On Github, you can disable mail notification about each comment in your
> profile configuration (at least for you personal email address -- I
> guess it still goes over the mailing list)
>
> Profile -> Settings -> Notification Center
>
> -Matthias
>
> On 09/22/2015 03:21 AM, Erik Weathers wrote:
> > Sure, STORM-*. ;-)
> >
> > Here's a good example:
> >
> > - https://issues.apache.org/jira/browse/STORM-329
> >
> > Compare that to this one:
> >
> > - https://issues.apache.org/jira/browse/STORM-404
> >
> > STORM-404 has a bunch of human-created comments, but it's readable since
> it
> > has no github-generated comments. STORM-329 however intermixes the human
> > comments with the github ones. It's really hard to read through.
> >
> > To be clear, it's not that it's *confusing* per se -- it's that the
> > behavior is *cluttering* the comments, making it harder to see any
> > human-created comments since any JIRA issue with a PR will usually end up
> > with many automated comments.
> >
> > BTW, I totally agree that linking from the JIRA issue to the github PR is
> > important! Would be even nicer if the github PRs also directly linked
> back
> > to the JIRA issue with a clickable link.
> >
> > - Erik
> >
> > On Mon, Sep 21, 2015 at 6:03 PM, 임정택 <ka...@gmail.com> wrote:
> >
> >> Hi Erik,
> >>
> >> I think verbose logging of PR comments could be OK. I didn't experience
> any
> >> confusing.
> >> Maybe referring sample JIRA issues could help us to understand.
> >>
> >> But I'm also open to change cause other projects already have been
> doing.
> >> (for example, https://issues.apache.org/jira/browse/SPARK-10474)
> >>
> >> In addition to SPARK has been doing, I'd like to still leave some
> events on
> >> github PR to JIRA issue, too.
> >>
> >> Btw, the thing I'm really annoyed is multiple mail notifications on each
> >> github comment.
> >>
> >> Thanks,
> >> Jungtaek Lim (HeartSaVioR)
> >>
> >> 2015-09-22 9:15 GMT+09:00 Erik Weathers <ew...@groupon.com>:
> >>
> >>> I find that these comments majorly distract from any discussion that
> may
> >>> occur in the JIRA issues themselves. What value are these
> providing? I
> >>> guess just insurance against GitHub being unavailable or going away?
> But
> >>> that doesn't seem worth the distraction cost. Is there any possibility
> >> of
> >>> removing this spamminess, or somehow putting them into attachments
> within
> >>> the JIRA issues so that they aren't directly in the comments?
> >>>
> >>> - Erik
> >>>
> >>
> >>
> >>
> >> --
> >> Name : 임 정택
> >> Blog : http://www.heartsavior.net / http://dev.heartsavior.net
> >> Twitter : http://twitter.com/heartsavior
> >> LinkedIn : http://www.linkedin.com/in/heartsavior
> >>
> >
>
>
--
Name : 임 정택
Blog : http://www.heartsavior.net / http://dev.heartsavior.net
Twitter : http://twitter.com/heartsavior
LinkedIn : http://www.linkedin.com/in/heartsavior
Re: does anyone else hate the verbose logging of all PR comments
in the Storm JIRAs?
Posted by "Matthias J. Sax" <mj...@apache.org>.
On Github, you can disable mail notification about each comment in your
profile configuration (at least for you personal email address -- I
guess it still goes over the mailing list)
Profile -> Settings -> Notification Center
-Matthias
On 09/22/2015 03:21 AM, Erik Weathers wrote:
> Sure, STORM-*. ;-)
>
> Here's a good example:
>
> - https://issues.apache.org/jira/browse/STORM-329
>
> Compare that to this one:
>
> - https://issues.apache.org/jira/browse/STORM-404
>
> STORM-404 has a bunch of human-created comments, but it's readable since it
> has no github-generated comments. STORM-329 however intermixes the human
> comments with the github ones. It's really hard to read through.
>
> To be clear, it's not that it's *confusing* per se -- it's that the
> behavior is *cluttering* the comments, making it harder to see any
> human-created comments since any JIRA issue with a PR will usually end up
> with many automated comments.
>
> BTW, I totally agree that linking from the JIRA issue to the github PR is
> important! Would be even nicer if the github PRs also directly linked back
> to the JIRA issue with a clickable link.
>
> - Erik
>
> On Mon, Sep 21, 2015 at 6:03 PM, 임정택 <ka...@gmail.com> wrote:
>
>> Hi Erik,
>>
>> I think verbose logging of PR comments could be OK. I didn't experience any
>> confusing.
>> Maybe referring sample JIRA issues could help us to understand.
>>
>> But I'm also open to change cause other projects already have been doing.
>> (for example, https://issues.apache.org/jira/browse/SPARK-10474)
>>
>> In addition to SPARK has been doing, I'd like to still leave some events on
>> github PR to JIRA issue, too.
>>
>> Btw, the thing I'm really annoyed is multiple mail notifications on each
>> github comment.
>>
>> Thanks,
>> Jungtaek Lim (HeartSaVioR)
>>
>> 2015-09-22 9:15 GMT+09:00 Erik Weathers <ew...@groupon.com>:
>>
>>> I find that these comments majorly distract from any discussion that may
>>> occur in the JIRA issues themselves. What value are these providing? I
>>> guess just insurance against GitHub being unavailable or going away? But
>>> that doesn't seem worth the distraction cost. Is there any possibility
>> of
>>> removing this spamminess, or somehow putting them into attachments within
>>> the JIRA issues so that they aren't directly in the comments?
>>>
>>> - Erik
>>>
>>
>>
>>
>> --
>> Name : 임 정택
>> Blog : http://www.heartsavior.net / http://dev.heartsavior.net
>> Twitter : http://twitter.com/heartsavior
>> LinkedIn : http://www.linkedin.com/in/heartsavior
>>
>
Re: does anyone else hate the verbose logging of all PR comments in
the Storm JIRAs?
Posted by Erik Weathers <ew...@groupon.com>.
Sure, STORM-*. ;-)
Here's a good example:
- https://issues.apache.org/jira/browse/STORM-329
Compare that to this one:
- https://issues.apache.org/jira/browse/STORM-404
STORM-404 has a bunch of human-created comments, but it's readable since it
has no github-generated comments. STORM-329 however intermixes the human
comments with the github ones. It's really hard to read through.
To be clear, it's not that it's *confusing* per se -- it's that the
behavior is *cluttering* the comments, making it harder to see any
human-created comments since any JIRA issue with a PR will usually end up
with many automated comments.
BTW, I totally agree that linking from the JIRA issue to the github PR is
important! Would be even nicer if the github PRs also directly linked back
to the JIRA issue with a clickable link.
- Erik
On Mon, Sep 21, 2015 at 6:03 PM, 임정택 <ka...@gmail.com> wrote:
> Hi Erik,
>
> I think verbose logging of PR comments could be OK. I didn't experience any
> confusing.
> Maybe referring sample JIRA issues could help us to understand.
>
> But I'm also open to change cause other projects already have been doing.
> (for example, https://issues.apache.org/jira/browse/SPARK-10474)
>
> In addition to SPARK has been doing, I'd like to still leave some events on
> github PR to JIRA issue, too.
>
> Btw, the thing I'm really annoyed is multiple mail notifications on each
> github comment.
>
> Thanks,
> Jungtaek Lim (HeartSaVioR)
>
> 2015-09-22 9:15 GMT+09:00 Erik Weathers <ew...@groupon.com>:
>
> > I find that these comments majorly distract from any discussion that may
> > occur in the JIRA issues themselves. What value are these providing? I
> > guess just insurance against GitHub being unavailable or going away? But
> > that doesn't seem worth the distraction cost. Is there any possibility
> of
> > removing this spamminess, or somehow putting them into attachments within
> > the JIRA issues so that they aren't directly in the comments?
> >
> > - Erik
> >
>
>
>
> --
> Name : 임 정택
> Blog : http://www.heartsavior.net / http://dev.heartsavior.net
> Twitter : http://twitter.com/heartsavior
> LinkedIn : http://www.linkedin.com/in/heartsavior
>
Re: does anyone else hate the verbose logging of all PR comments in
the Storm JIRAs?
Posted by 임정택 <ka...@gmail.com>.
Hi Erik,
I think verbose logging of PR comments could be OK. I didn't experience any
confusing.
Maybe referring sample JIRA issues could help us to understand.
But I'm also open to change cause other projects already have been doing.
(for example, https://issues.apache.org/jira/browse/SPARK-10474)
In addition to SPARK has been doing, I'd like to still leave some events on
github PR to JIRA issue, too.
Btw, the thing I'm really annoyed is multiple mail notifications on each
github comment.
Thanks,
Jungtaek Lim (HeartSaVioR)
2015-09-22 9:15 GMT+09:00 Erik Weathers <ew...@groupon.com>:
> I find that these comments majorly distract from any discussion that may
> occur in the JIRA issues themselves. What value are these providing? I
> guess just insurance against GitHub being unavailable or going away? But
> that doesn't seem worth the distraction cost. Is there any possibility of
> removing this spamminess, or somehow putting them into attachments within
> the JIRA issues so that they aren't directly in the comments?
>
> - Erik
>
--
Name : 임 정택
Blog : http://www.heartsavior.net / http://dev.heartsavior.net
Twitter : http://twitter.com/heartsavior
LinkedIn : http://www.linkedin.com/in/heartsavior