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 <slide.o....@gmail.com>:
> 
> 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 <msic...@cloudbees.com 
> <mailto:msic...@cloudbees.com>> 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 <m...@batmat.net 
> <mailto:m...@batmat.net>> 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 <jgl...@cloudbees.com 
> > <mailto:jgl...@cloudbees.com>> a écrit :
> >>
> >> On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev <o.v.nenas...@gmail.com 
> >> <mailto:o.v.nenas...@gmail.com>> 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 
> >> <mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>.
> >> To view this discussion on the web visit 
> >> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2MLHtwCNgQhbLCBjV78NVPSCUs0zUs2_zDChw6Aad5bw%40mail.gmail.com
> >>  
> >> <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 
> > <mailto:jenkinsci-dev%2bunsubscr...@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
> >  
> > <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 
> <mailto:jenkinsci-dev%2bunsubscr...@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
>  
> <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 
> <mailto: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
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVduNcw%3DWYb6%2BHNebzarAoQCt%2Bg6bQuFgitVP%3DuC3O2Bww%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
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/EA39641E-B166-4453-8D2C-45C841F3D684%40gmail.com.

Reply via email to