I've removed the "default assignments" settings in jira. Expect a mass of email as folks start to "unassign" tickets. :)
On Wed, Nov 18, 2015 at 10:22 AM, Stephen Mallette <[email protected]> wrote: > There are "default" assignments in JIRA. When we first got setup with > JIRA I think they were all setup to auto-assign to me. I later set it up > to auto-assign "process" ones to you....something like that. I'm ok with > turning that "feature" off all together. As it stands right now, I think > they only auto-assign to me and you depending on the areas of the code base > we tinker on the most. so it just affects the two of us. our workflow > really doesn't require assigning tickets that aren't being worked on, so > that's another reason we might just drop it. > > Assuming there are no objections here in the next 72 hours (Saturday, > November 21, 2015 at 10:30AM EST) i'll assume lazy consensus and drop the > auto-assignment. > > On Wed, Nov 18, 2015 at 10:12 AM, Marko Rodriguez <[email protected]> > wrote: > >> Hello, >> >> I notice that lots of people (committers and general users) like to >> assign people their submitted tickets. For instance, they find a bug in >> Traversal and then are like "Marko." I think that if you submit a ticket >> and you will take ownership of it, then assign it to yourself and do the >> work. Else, keep it Unassigned and when developers peruse the the list they >> can go "I can knock this out" and will assign it to themselves. I think it >> should be up to people to decide what they want to work on, not the >> submitter to decide who will do the work. >> >> Thoughts?, >> Marko. >> >> http://markorodriguez.com >> >> >
