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> a écrit : > On Tue, Aug 27, 2019 at 8:54 AM Oleg Nenashev <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. > 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.
