I also disagree. I reckon the best way is to assign the maintainer (however, this word seems rather loaded in Jenkins world). If the assignee doesn’t want to work on it for whatever reason they could free it up by unassigning and labelling the issue appropriately.
This seems like a separate discussion though. > On 14 Aug 2018, at 16:59, Slide <[email protected]> wrote: > > I somewhat disagree with this, as I generally only see emails about issues if > I am assigned to it (maybe my settings are setup incorrectly somewhere?). If > I don't get emails, the issue will sit without me looking at it for a fairly > long period of time, which means the person could get discouraged in that > case as well since no one sees the issue. > >> On Tue, Aug 14, 2018 at 8:56 AM Baptiste Mathus <[email protected]> wrote: >> >> >>> Le jeu. 9 août 2018 à 23:47, Jesse Glick <[email protected]> a écrit : >>> On Thu, Aug 9, 2018 at 12:57 PM Oleg Nenashev <[email protected]> >>> wrote: >>> > Should I also change the default assignee in JIRA? >>> >>> I have no opinion about that. Generally I find the default assignee >>> option to be a bad idea—you should assign an issue to yourself if and >>> when you plan to actually work on it, or someone has a specific reason >>> to think you are the one who _should_ work on it (for example because >>> you introduced a regression). If a plugin has only ever had one >>> maintainer, maybe it makes sense to just assume that any newly filed >>> issue is going to be handled by them or not at all. >> >> >> +1. I think there should not be a default assignee. It conveys the wrong >> message: >> * That the assignee is going to look into the issue >> * It probably hence discourages some people to try and propose a fix when >> they see someone is already working on it (they think) >> >>> >>> -- >>> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2hAyfHmpmJZwv_EAJoECZM8HxYx17eAvJJgcQ10A%3Dscw%40mail.gmail.com. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6W3t%2BEdqVY%3Dz3gvwMkq1LYk%3DXDoEM6gmW5mVGGGnSfhA%40mail.gmail.com. >> For more options, visit https://groups.google.com/d/optout. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcqpRRwP9_XCA%2B8KMBmPmRErS5ZgErYPd5s6OBhESrhDw%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5C1DA500-5BDC-4516-802B-5915D55A139C%40gmail.com. For more options, visit https://groups.google.com/d/optout.
