Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

[Daniel Beck]

> On 7. Sep 2019, at 03:52, Jesse Glick  wrote:
> 
> I tried this, but it does not do what I need: it just sends, say, a
> daily list of all issues matching that filter. To replace the
> notification function of default assignee, I would want something that
> only send me _changes_ in issues matching the filter.

`createdDate > -1d` (or updatedDate) might work for daily notifications from 
subscriptions, perhaps in conjunction with `watcher != currentUser()`. But 
still not a great replacement (and misses issues whose component gets changed 
to yours).

FWIW I like being default assignee for matrix-auth-plugin and being informed of 
new issues quickly. Granted, it's a very low volume of notifications, but I 
expect that to apply to most plugins in the "long tail". It's the top 10-20% of 
plugins that presumably have a very high volume of new and updated issues, 
making having a default assignee impractical.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/FE5691A6-2F90-4311-8439-D5FB060C92AE%40beckweb.net.

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

[Jesse Glick]

On Thu, Sep 5, 2019 at 7:01 PM Oleg Nenashev  wrote:
> create a filter (or to use a public one), go to "Details" and then to 
> subscribe to notifications there.

I tried this, but it does not do what I need: it just sends, say, a
daily list of all issues matching that filter. To replace the
notification function of default assignee, I would want something that
only send me _changes_ in issues matching the filter.

I suppose a workaround would be to create a filter matching all issues
from some component which I am not watching, and then send a digest of
that; then I would need to click on everything newly appearing and
watch it, and rely on the watches for notifications. Seems pretty
clumsy though.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2kBsSjX50OWKTX1P6EwWPj-KQ_QiufssxjBzi-%3DX3XWg%40mail.gmail.com.

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

[Gavin]

Filterers can be saved and shared, and so a default search could be setup
with
https://confluence.atlassian.com/jira063/advanced-searching-functions-683542527.html#AdvancedSearchingFunctions-componentsLeadByUser()
and then any custom requirements could be forked and tweaked per user.


On Fri., Sep. 6, 2019, 1:35 a.m. Olblak,  wrote:

> I totally agree with the general opinion that an issue should only be
> assigned to someone if that person is effectively ready to work on it
> otherwise it just bring confusion about either the assignee will
> effectively works on it or not.
> And I also understand that people use default assignee to get notify when
> a new issue is created.
>
> What I propose is to set 'default assignee' to 'unassigned' by default and
> add a notification rule saying each time a ticket is (re)-open, or close,
> we notify component lead. (btw I just created that rule now :p)
>
> Regarding filters, I think it really depends how much time we spend on
> Jira, personally I heavily rely on them but I don't expect every
> contributor to configure their own filters
>
> ---
> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
>
>
>
>
> On Fri, Sep 6, 2019, at 7:38 AM, domi wrote:
>
> My first thought was that I would like to keep the default assignee - but
> after reading all the comments, I have to agree, that my only reason for
> this is so that I get notified by new issues. Although Oleg shoed it is
> possible to create a filter and get notified about this things, It seems
> quite complicated and many maintainers will not do it and therefore not get
> any info about new issues. So I think there should be some kind of easy way
> to at least inform the official maintainer - maybe we can even create these
> filters automatically…
> /Domi
>
>
> On 6 Sep 2019, at 01:37, Ullrich Hafner  wrote:
>
> Making it an optional field in the HOSTING report seems to be a good
> compromise, so +1 from me for such a change.
>
> (I understand that developers do not want to be assignee for issues they
> are never going to fix. On the other hands, for a user that reports an
> issue it is somewhat disappointing that no one actually cares about his new
> issue. This will indicate that it is not worth to report an issue at all.)
>
>
> Am 05.09.2019 um 20:40 schrieb Slide :
>
> We should add a field in the HOSTING Jira that allows people to specify if
> they want to be set as the default assignee, then the bot can check that
> field before setting up the default assignee for the component. We would
> need someone with admin access on Jira to add the field. I can create a PR
> for the bot once the field is setup.
>
> On Thu, Sep 5, 2019, 11:35 Matt Sicker  wrote:
>
> That makes tons of sense to me. You should only assign tickets to
> yourself that you're currently working on or at least intend to work
> on in the near future.
>
> On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus  wrote:
> >
> > I fully agree with Jesse's take. IMO for most plugins where the
> maintainer is not going to have time to jump on new reports right away,
> this sends a wrong message that issues will be analyzed and fixed by the
> assignee.
> > This sends a second bad message: that an issue being already assigned,
> this is not necessary that someone steps up to work on a fix proposal.
> >
> > AIUI, the default assignee is often used by maintainers as a nice way to
> be notified when a new issue arises, but on average not meaning that that
> given maintainer will commit to address in a timely manner anything new
> that comes in.
> >
> > IOW, my main point is that I think we should allow maintainers to be
> made default assignee, but we should default to having no default assignee.
> >
> > Le mar. 27 août 2019 à 15:14, Jesse Glick  a
> écrit :
> >>
> >> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev 
> wrote:
> >> > a default assignee for the component
> >>
> >> As always, I prefer there to be no default assignee for a JIRA
> >> component. It is not a helpful concept IMO. If and when I decide to
> >> tackle an issue, I will assign it to myself.
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
> >> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com
> .
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com
> .
>
>
>
> --
> Matt Sicker
> Senior Software Engineer, CloudBees
>

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

[Olblak]

I totally agree with the general opinion that an issue should only be assigned 
to someone if that person is effectively ready to work on it otherwise it just 
bring confusion about either the assignee will effectively works on it or not.
And I also understand that people use default assignee to get notify when a new 
issue is created. 

What I propose is to set 'default assignee' to 'unassigned' by default and add 
a notification rule saying each time a ticket is (re)-open, or close, we notify 
component lead. (btw I just created that rule now :p)

Regarding filters, I think it really depends how much time we spend on Jira, 
personally I heavily rely on them but I don't expect every contributor to 
configure their own filters

---
-> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---




On Fri, Sep 6, 2019, at 7:38 AM, domi wrote:
> My first thought was that I would like to keep the default assignee - but 
> after reading all the comments, I have to agree, that my only reason for this 
> is so that I get notified by new issues. Although Oleg shoed it is possible 
> to create a filter and get notified about this things, It seems quite 
> complicated and many maintainers will not do it and therefore not get any 
> info about new issues. So I think there should be some kind of easy way to at 
> least inform the official maintainer - maybe we can even create these filters 
> automatically…
> /Domi
> 
> 
>> On 6 Sep 2019, at 01:37, Ullrich Hafner  wrote:
>> 
>> Making it an optional field in the HOSTING report seems to be a good 
>> compromise, so +1 from me for such a change.
>> 
>> (I understand that developers do not want to be assignee for issues they are 
>> never going to fix. On the other hands, for a user that reports an issue it 
>> is somewhat disappointing that no one actually cares about his new issue. 
>> This will indicate that it is not worth to report an issue at all.)
>> 
>> 
>>> Am 05.09.2019 um 20:40 schrieb Slide :
>>> 
>>> We should add a field in the HOSTING Jira that allows people to specify if 
>>> they want to be set as the default assignee, then the bot can check that 
>>> field before setting up the default assignee for the component. We would 
>>> need someone with admin access on Jira to add the field. I can create a PR 
>>> for the bot once the field is setup.
>>> 
>>> On Thu, Sep 5, 2019, 11:35 Matt Sicker  wrote:
 That makes tons of sense to me. You should only assign tickets to
  yourself that you're currently working on or at least intend to work
  on in the near future.
 
  On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus  wrote:
  >
  > I fully agree with Jesse's take. IMO for most plugins where the 
 maintainer is not going to have time to jump on new reports right away, 
 this sends a wrong message that issues will be analyzed and fixed by the 
 assignee.
  > This sends a second bad message: that an issue being already assigned, 
 this is not necessary that someone steps up to work on a fix proposal.
  >
  > AIUI, the default assignee is often used by maintainers as a nice way 
 to be notified when a new issue arises, but on average not meaning that 
 that given maintainer will commit to address in a timely manner anything 
 new that comes in.
  >
  > IOW, my main point is that I think we should allow maintainers to be 
 made default assignee, but we should default to having no default assignee.
  >
  > Le mar. 27 août 2019 à 15:14, Jesse Glick  a 
 écrit :
  >>
  >> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev  
 wrote:
  >> > a default assignee for the component
  >>
  >> As always, I prefer there to be no default assignee for a JIRA
  >> component. It is not a helpful concept IMO. If and when I decide to
  >> tackle an issue, I will assign it to myself.
  >>
  >> --
  >> You received this message because you are subscribed to the Google 
 Groups "Jenkins Developers" group.
  >> To unsubscribe from this group and stop receiving emails from it, send 
 an email to jenkinsci-dev+unsubscr...@googlegroups.com 
 .
  >> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com.
  >
  > --
  > You received this message because you are subscribed to the Google 
 Groups "Jenkins Developers" group.
  > To unsubscribe from this group and stop receiving emails from it, send 
 an email to jenkinsci-dev+unsubscr...@googlegroups.com 
 .
  > To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com.
 
 
 
  -- 
  Matt Sicker
  Senior Software Engineer, 

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

[domi]

My first thought was that I would like to keep the default assignee - but after 
reading all the comments, I have to agree, that my only reason for this is so 
that I get notified by new issues. Although Oleg shoed it is possible to create 
a filter and get notified about this things, It seems quite complicated and 
many maintainers will not do it and therefore not get any info about new 
issues. So I think there should be some kind of easy way to at least inform the 
official maintainer - maybe we can even create these filters automatically…
/Domi


> On 6 Sep 2019, at 01:37, Ullrich Hafner  wrote:
> 
> Making it an optional field in the HOSTING report seems to be a good 
> compromise, so +1 from me for such a change.
> 
> (I understand that developers do not want to be assignee for issues they are 
> never going to fix. On the other hands, for a user that reports an issue it 
> is somewhat disappointing that no one actually cares about his new issue. 
> This will indicate that it is not worth to report an issue at all.)
>  
> 
>> Am 05.09.2019 um 20:40 schrieb Slide > >:
>> 
>> We should add a field in the HOSTING Jira that allows people to specify if 
>> they want to be set as the default assignee, then the bot can check that 
>> field before setting up the default assignee for the component. We would 
>> need someone with admin access on Jira to add the field. I can create a PR 
>> for the bot once the field is setup.
>> 
>> On Thu, Sep 5, 2019, 11:35 Matt Sicker > > wrote:
>> That makes tons of sense to me. You should only assign tickets to
>> yourself that you're currently working on or at least intend to work
>> on in the near future.
>> 
>> On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus > > wrote:
>> >
>> > I fully agree with Jesse's take. IMO for most plugins where the maintainer 
>> > is not going to have time to jump on new reports right away, this sends a 
>> > wrong message that issues will be analyzed and fixed by the assignee.
>> > This sends a second bad message: that an issue being already assigned, 
>> > this is not necessary that someone steps up to work on a fix proposal.
>> >
>> > AIUI, the default assignee is often used by maintainers as a nice way to 
>> > be notified when a new issue arises, but on average not meaning that that 
>> > given maintainer will commit to address in a timely manner anything new 
>> > that comes in.
>> >
>> > IOW, my main point is that I think we should allow maintainers to be made 
>> > default assignee, but we should default to having no default assignee.
>> >
>> > Le mar. 27 août 2019 à 15:14, Jesse Glick > > > a écrit :
>> >>
>> >> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev > >> > wrote:
>> >> > a default assignee for the component
>> >>
>> >> As always, I prefer there to be no default assignee for a JIRA
>> >> component. It is not a helpful concept IMO. If and when I decide to
>> >> tackle an issue, I will assign it to myself.
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google Groups 
>> >> "Jenkins Developers" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send an 
>> >> email to jenkinsci-dev+unsubscr...@googlegroups.com 
>> >> .
>> >> To view this discussion on the web visit 
>> >> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com
>> >>  
>> >> .
>> >
>> > --
>> > You received this message because you are subscribed to the Google Groups 
>> > "Jenkins Developers" group.
>> > To unsubscribe from this group and stop receiving emails from it, send an 
>> > email to jenkinsci-dev+unsubscr...@googlegroups.com 
>> > .
>> > To view this discussion on the web visit 
>> > https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com
>> >  
>> > .
>> 
>> 
>> 
>> -- 
>> Matt Sicker
>> Senior Software Engineer, CloudBees
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-dev+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox7Xqp9gzdht-R7GYHjs%2B%3DUdw2Yk32H91pnvyUw9axRZw%40mail.gmail.com
>>  
>> 

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

[Ullrich Hafner]

Making it an optional field in the HOSTING report seems to be a good 
compromise, so +1 from me for such a change.

(I understand that developers do not want to be assignee for issues they are 
never going to fix. On the other hands, for a user that reports an issue it is 
somewhat disappointing that no one actually cares about his new issue. This 
will indicate that it is not worth to report an issue at all.)
 

> Am 05.09.2019 um 20:40 schrieb Slide :
> 
> We should add a field in the HOSTING Jira that allows people to specify if 
> they want to be set as the default assignee, then the bot can check that 
> field before setting up the default assignee for the component. We would need 
> someone with admin access on Jira to add the field. I can create a PR for the 
> bot once the field is setup.
> 
> On Thu, Sep 5, 2019, 11:35 Matt Sicker  > wrote:
> That makes tons of sense to me. You should only assign tickets to
> yourself that you're currently working on or at least intend to work
> on in the near future.
> 
> On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus  > wrote:
> >
> > I fully agree with Jesse's take. IMO for most plugins where the maintainer 
> > is not going to have time to jump on new reports right away, this sends a 
> > wrong message that issues will be analyzed and fixed by the assignee.
> > This sends a second bad message: that an issue being already assigned, this 
> > is not necessary that someone steps up to work on a fix proposal.
> >
> > AIUI, the default assignee is often used by maintainers as a nice way to be 
> > notified when a new issue arises, but on average not meaning that that 
> > given maintainer will commit to address in a timely manner anything new 
> > that comes in.
> >
> > IOW, my main point is that I think we should allow maintainers to be made 
> > default assignee, but we should default to having no default assignee.
> >
> > Le mar. 27 août 2019 à 15:14, Jesse Glick  > > a écrit :
> >>
> >> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev  >> > wrote:
> >> > a default assignee for the component
> >>
> >> As always, I prefer there to be no default assignee for a JIRA
> >> component. It is not a helpful concept IMO. If and when I decide to
> >> tackle an issue, I will assign it to myself.
> >>
> >> --
> >> You received this message because you are subscribed to the Google Groups 
> >> "Jenkins Developers" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an 
> >> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> >> .
> >> To view this discussion on the web visit 
> >> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com
> >>  
> >> .
> >
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to jenkinsci-dev+unsubscr...@googlegroups.com 
> > .
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com
> >  
> > .
> 
> 
> 
> -- 
> Matt Sicker
> Senior Software Engineer, CloudBees
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox7Xqp9gzdht-R7GYHjs%2B%3DUdw2Yk32H91pnvyUw9axRZw%40mail.gmail.com
>  
> .
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVduNcw%3DWYb6%2BHNebzarAoQCt%2Bg6bQuFgitVP%3DuC3O2Bww%40mail.gmail.com
>  
> .

-- 
You received this message because you are subscribed to the 

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

[Jesse Glick]

On Thu, Sep 5, 2019 at 2:36 PM Gavin  wrote:
> Does jira have a concept of auto watch like GitHub does? So an issue could 
> still notify people but not be claimed?

Good question. That would be very useful.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3SkUwcr4D4mDfqgF2axjWFv42J-2_zRcBgF%2BNOXsK%3DLQ%40mail.gmail.com.

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

[Gavin]

Does jira have a concept of auto watch like GitHub does? So an issue could
still notify people but not be claimed?

On Thu., Sep. 5, 2019, 11:35 a.m. Matt Sicker, 
wrote:

> That makes tons of sense to me. You should only assign tickets to
> yourself that you're currently working on or at least intend to work
> on in the near future.
>
> On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus  wrote:
> >
> > I fully agree with Jesse's take. IMO for most plugins where the
> maintainer is not going to have time to jump on new reports right away,
> this sends a wrong message that issues will be analyzed and fixed by the
> assignee.
> > This sends a second bad message: that an issue being already assigned,
> this is not necessary that someone steps up to work on a fix proposal.
> >
> > AIUI, the default assignee is often used by maintainers as a nice way to
> be notified when a new issue arises, but on average not meaning that that
> given maintainer will commit to address in a timely manner anything new
> that comes in.
> >
> > IOW, my main point is that I think we should allow maintainers to be
> made default assignee, but we should default to having no default assignee.
> >
> > Le mar. 27 août 2019 à 15:14, Jesse Glick  a
> écrit :
> >>
> >> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev 
> wrote:
> >> > a default assignee for the component
> >>
> >> As always, I prefer there to be no default assignee for a JIRA
> >> component. It is not a helpful concept IMO. If and when I decide to
> >> tackle an issue, I will assign it to myself.
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
> >> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com
> .
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com
> .
>
>
>
> --
> Matt Sicker
> Senior Software Engineer, CloudBees
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox7Xqp9gzdht-R7GYHjs%2B%3DUdw2Yk32H91pnvyUw9axRZw%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuvBB0ye4y%2Bg2_F8MjwgbMPutgUbuiFTA0d0fjVnYX4xcw%40mail.gmail.com.

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

[Matt Sicker]

That makes tons of sense to me. You should only assign tickets to
yourself that you're currently working on or at least intend to work
on in the near future.

On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus  wrote:
>
> I fully agree with Jesse's take. IMO for most plugins where the maintainer is 
> not going to have time to jump on new reports right away, this sends a wrong 
> message that issues will be analyzed and fixed by the assignee.
> This sends a second bad message: that an issue being already assigned, this 
> is not necessary that someone steps up to work on a fix proposal.
>
> AIUI, the default assignee is often used by maintainers as a nice way to be 
> notified when a new issue arises, but on average not meaning that that given 
> maintainer will commit to address in a timely manner anything new that comes 
> in.
>
> IOW, my main point is that I think we should allow maintainers to be made 
> default assignee, but we should default to having no default assignee.
>
> Le mar. 27 août 2019 à 15:14, Jesse Glick  a écrit :
>>
>> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev  wrote:
>> > a default assignee for the component
>>
>> As always, I prefer there to be no default assignee for a JIRA
>> component. It is not a helpful concept IMO. If and when I decide to
>> tackle an issue, I will assign it to myself.
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com.



-- 
Matt Sicker
Senior Software Engineer, CloudBees

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox7Xqp9gzdht-R7GYHjs%2B%3DUdw2Yk32H91pnvyUw9axRZw%40mail.gmail.com.

[DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

[Baptiste Mathus]

I fully agree with Jesse's take. IMO for most plugins where the maintainer
is not going to have time to jump on new reports right away, this sends a
wrong message that issues will be analyzed and fixed by the assignee.
This sends a second bad message: that an issue being already assigned, this
is not necessary that someone steps up to work on a fix proposal.

AIUI, the default assignee is often used by maintainers as a nice way to be
notified when a new issue arises, but on average not meaning that that
given maintainer will commit to address in a timely manner anything new
that comes in.

IOW, my main point is that I think we should allow maintainers to be made
default assignee, but we should default to having no default assignee.

Le mar. 27 août 2019 à 15:14, Jesse Glick  a écrit :

> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev 
> wrote:
> > a default assignee for the component
>
> As always, I prefer there to be no default assignee for a JIRA
> component. It is not a helpful concept IMO. If and when I decide to
> tackle an issue, I will assign it to myself.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7J1661hacPVP9rMN5sK%2Bz_Hsos28Bd8N%2BNbxwxMouWNA%40mail.gmail.com.