You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@groovy.apache.org by Pascal Schumacher <pa...@gmx.net> on 2016/01/15 19:42:34 UTC
Disable auto-assignment of jira issues?
Hello everybody,
I think should disable auto-assignment of jira issues. Dozen of issues
are assigned to people who do not currently work on them. I believe this
stops people from contributing, because they think somebody is already
working on the issue. It also mislead users to expect that the issue
will be fixed soon.
What do you think?
Cheers,
Pascal
Re: Disable auto-assignment of jira issues?
Posted by Cédric Champeau <ce...@gmail.com>.
+1
2016-01-15 19:42 GMT+01:00 Pascal Schumacher <pa...@gmx.net>:
> Hello everybody,
>
> I think should disable auto-assignment of jira issues. Dozen of issues are
> assigned to people who do not currently work on them. I believe this stops
> people from contributing, because they think somebody is already working on
> the issue. It also mislead users to expect that the issue will be fixed
> soon.
>
> What do you think?
>
> Cheers,
> Pascal
>
Re: Disable auto-assignment of jira issues?
Posted by Pascal Schumacher <pa...@gmx.net>.
http://www.groovy-lang.org/contribute.html
Am 16.01.2016 um 09:19 schrieb jim northrop:
> Do we have an up-to-date guidebook on how to contribute to Apache
> Groovy or is the process unclear ?
> thx
>
> On 16 January 2016 at 06:06, Guillaume Laforge <glaforge@gmail.com
> <ma...@gmail.com>> wrote:
>
> I've moved forward and removed all component leads, and set back the
> default assignment to the "default project assignment" which is... "no
> assignment". So we're good now on that front.
>
> Perhaps the next step would be to do a pass on all currently assigned
> issues and remove all assignments?
> The problem with that though is that doing it large and wide might
> remove assignments that are indeed really being worked on...
> What do you think?
>
> Guillaume
>
> On Fri, Jan 15, 2016 at 7:42 PM, Pascal Schumacher
> <pascalschumacher@gmx.net <ma...@gmx.net>> wrote:
> > Hello everybody,
> >
> > I think should disable auto-assignment of jira issues. Dozen of
> issues are
> > assigned to people who do not currently work on them. I believe
> this stops
> > people from contributing, because they think somebody is already
> working on
> > the issue. It also mislead users to expect that the issue will
> be fixed
> > soon.
> >
> > What do you think?
> >
> > Cheers,
> > Pascal
>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer & PMC member
> Product Ninja & Advocate at Restlet
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge / Google+
>
>
Re: Disable auto-assignment of jira issues?
Posted by jim northrop <ja...@googlemail.com>.
Do we have an up-to-date guidebook on how to contribute to Apache Groovy or
is the process unclear ?
thx
On 16 January 2016 at 06:06, Guillaume Laforge <gl...@gmail.com> wrote:
> I've moved forward and removed all component leads, and set back the
> default assignment to the "default project assignment" which is... "no
> assignment". So we're good now on that front.
>
> Perhaps the next step would be to do a pass on all currently assigned
> issues and remove all assignments?
> The problem with that though is that doing it large and wide might
> remove assignments that are indeed really being worked on...
> What do you think?
>
> Guillaume
>
> On Fri, Jan 15, 2016 at 7:42 PM, Pascal Schumacher
> <pa...@gmx.net> wrote:
> > Hello everybody,
> >
> > I think should disable auto-assignment of jira issues. Dozen of issues
> are
> > assigned to people who do not currently work on them. I believe this
> stops
> > people from contributing, because they think somebody is already working
> on
> > the issue. It also mislead users to expect that the issue will be fixed
> > soon.
> >
> > What do you think?
> >
> > Cheers,
> > Pascal
>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer & PMC member
> Product Ninja & Advocate at Restlet
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge / Google+
>
Re: Disable auto-assignment of jira issues?
Posted by Guillaume Laforge <gl...@gmail.com>.
Okie dokie, thanks Pascal.
On Wed, Jan 20, 2016 at 7:51 PM, Pascal Schumacher
<pa...@gmx.net> wrote:
> I went ahead and removed the assignee of all issue which didn't look like
> they were currently worked on.
>
>
> Am 16.01.2016 um 13:11 schrieb Pascal Schumacher:
>>
>> Am 16.01.2016 um 06:06 schrieb Guillaume Laforge:
>>>
>>> I've moved forward and removed all component leads, and set back the
>>> default assignment to the "default project assignment" which is... "no
>>> assignment". So we're good now on that front.
>>
>> Thanks!
>>
>>> Perhaps the next step would be to do a pass on all currently assigned
>>> issues and remove all assignments?
>>> The problem with that though is that doing it large and wide might
>>> remove assignments that are indeed really being worked on...
>>> What do you think?
>>
>>
>> +1 to just removing current assignment
>>
>> Then everybody who is currently working on an issue can reassign it to
>> himself.
>>
>> Only four people currently have assigned issues:
>>
>>
>> https://issues.apache.org/jira/browse/GROOVY/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel
>>
>> Almost all unresolved issues are assigned to Cédric and Paul (I guess
>> these were the remaining default assignees).
>
>
--
Guillaume Laforge
Apache Groovy committer & PMC member
Product Ninja & Advocate at Restlet
Blog: http://glaforge.appspot.com/
Social: @glaforge / Google+
Re: Disable auto-assignment of jira issues?
Posted by Pascal Schumacher <pa...@gmx.net>.
I went ahead and removed the assignee of all issue which didn't look
like they were currently worked on.
Am 16.01.2016 um 13:11 schrieb Pascal Schumacher:
> Am 16.01.2016 um 06:06 schrieb Guillaume Laforge:
>> I've moved forward and removed all component leads, and set back the
>> default assignment to the "default project assignment" which is... "no
>> assignment". So we're good now on that front.
> Thanks!
>
>> Perhaps the next step would be to do a pass on all currently assigned
>> issues and remove all assignments?
>> The problem with that though is that doing it large and wide might
>> remove assignments that are indeed really being worked on...
>> What do you think?
>
> +1 to just removing current assignment
>
> Then everybody who is currently working on an issue can reassign it to
> himself.
>
> Only four people currently have assigned issues:
>
> https://issues.apache.org/jira/browse/GROOVY/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel
>
>
> Almost all unresolved issues are assigned to Cédric and Paul (I guess
> these were the remaining default assignees).
Re: Disable auto-assignment of jira issues?
Posted by Pascal Schumacher <pa...@gmx.net>.
Am 16.01.2016 um 06:06 schrieb Guillaume Laforge:
> I've moved forward and removed all component leads, and set back the
> default assignment to the "default project assignment" which is... "no
> assignment". So we're good now on that front.
Thanks!
> Perhaps the next step would be to do a pass on all currently assigned
> issues and remove all assignments?
> The problem with that though is that doing it large and wide might
> remove assignments that are indeed really being worked on...
> What do you think?
+1 to just removing current assignment
Then everybody who is currently working on an issue can reassign it to
himself.
Only four people currently have assigned issues:
https://issues.apache.org/jira/browse/GROOVY/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel
Almost all unresolved issues are assigned to Cédric and Paul (I guess
these were the remaining default assignees).
Re: Disable auto-assignment of jira issues?
Posted by Guillaume Laforge <gl...@gmail.com>.
Actually 116 with the re-opened ones, or in progress.
On Sat, Jan 16, 2016 at 6:11 AM, Guillaume Laforge <gl...@gmail.com> wrote:
> There's about 113 issues currently assigned (if I performed the right
> JIRA query)
>
> On Sat, Jan 16, 2016 at 6:06 AM, Guillaume Laforge <gl...@gmail.com> wrote:
>> I've moved forward and removed all component leads, and set back the
>> default assignment to the "default project assignment" which is... "no
>> assignment". So we're good now on that front.
>>
>> Perhaps the next step would be to do a pass on all currently assigned
>> issues and remove all assignments?
>> The problem with that though is that doing it large and wide might
>> remove assignments that are indeed really being worked on...
>> What do you think?
>>
>> Guillaume
>>
>> On Fri, Jan 15, 2016 at 7:42 PM, Pascal Schumacher
>> <pa...@gmx.net> wrote:
>>> Hello everybody,
>>>
>>> I think should disable auto-assignment of jira issues. Dozen of issues are
>>> assigned to people who do not currently work on them. I believe this stops
>>> people from contributing, because they think somebody is already working on
>>> the issue. It also mislead users to expect that the issue will be fixed
>>> soon.
>>>
>>> What do you think?
>>>
>>> Cheers,
>>> Pascal
>>
>>
>>
>> --
>> Guillaume Laforge
>> Apache Groovy committer & PMC member
>> Product Ninja & Advocate at Restlet
>>
>> Blog: http://glaforge.appspot.com/
>> Social: @glaforge / Google+
>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer & PMC member
> Product Ninja & Advocate at Restlet
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge / Google+
--
Guillaume Laforge
Apache Groovy committer & PMC member
Product Ninja & Advocate at Restlet
Blog: http://glaforge.appspot.com/
Social: @glaforge / Google+
Re: Disable auto-assignment of jira issues?
Posted by Guillaume Laforge <gl...@gmail.com>.
There's about 113 issues currently assigned (if I performed the right
JIRA query)
On Sat, Jan 16, 2016 at 6:06 AM, Guillaume Laforge <gl...@gmail.com> wrote:
> I've moved forward and removed all component leads, and set back the
> default assignment to the "default project assignment" which is... "no
> assignment". So we're good now on that front.
>
> Perhaps the next step would be to do a pass on all currently assigned
> issues and remove all assignments?
> The problem with that though is that doing it large and wide might
> remove assignments that are indeed really being worked on...
> What do you think?
>
> Guillaume
>
> On Fri, Jan 15, 2016 at 7:42 PM, Pascal Schumacher
> <pa...@gmx.net> wrote:
>> Hello everybody,
>>
>> I think should disable auto-assignment of jira issues. Dozen of issues are
>> assigned to people who do not currently work on them. I believe this stops
>> people from contributing, because they think somebody is already working on
>> the issue. It also mislead users to expect that the issue will be fixed
>> soon.
>>
>> What do you think?
>>
>> Cheers,
>> Pascal
>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer & PMC member
> Product Ninja & Advocate at Restlet
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge / Google+
--
Guillaume Laforge
Apache Groovy committer & PMC member
Product Ninja & Advocate at Restlet
Blog: http://glaforge.appspot.com/
Social: @glaforge / Google+
Re: Disable auto-assignment of jira issues?
Posted by Guillaume Laforge <gl...@gmail.com>.
I've moved forward and removed all component leads, and set back the
default assignment to the "default project assignment" which is... "no
assignment". So we're good now on that front.
Perhaps the next step would be to do a pass on all currently assigned
issues and remove all assignments?
The problem with that though is that doing it large and wide might
remove assignments that are indeed really being worked on...
What do you think?
Guillaume
On Fri, Jan 15, 2016 at 7:42 PM, Pascal Schumacher
<pa...@gmx.net> wrote:
> Hello everybody,
>
> I think should disable auto-assignment of jira issues. Dozen of issues are
> assigned to people who do not currently work on them. I believe this stops
> people from contributing, because they think somebody is already working on
> the issue. It also mislead users to expect that the issue will be fixed
> soon.
>
> What do you think?
>
> Cheers,
> Pascal
--
Guillaume Laforge
Apache Groovy committer & PMC member
Product Ninja & Advocate at Restlet
Blog: http://glaforge.appspot.com/
Social: @glaforge / Google+
Re: Disable auto-assignment of jira issues?
Posted by Jochen Theodorou <bl...@gmx.org>.
On 15.01.2016 19:42, Pascal Schumacher wrote:
> Hello everybody,
>
> I think should disable auto-assignment of jira issues. Dozen of issues
> are assigned to people who do not currently work on them. I believe this
> stops people from contributing, because they think somebody is already
> working on the issue. It also mislead users to expect that the issue
> will be fixed soon.
>
> What do you think?
yes, I think we should do so. For my stuff I did that back in spring already
bye Jochen
Re: Disable auto-assignment of jira issues?
Posted by Konstantin Boudnik <co...@apache.org>.
Second what Pascal said. Many time I've seen when people are hesitant to take
on task because the ticket is assigned to someone. One way around it is to
educate the community to simply grab anything that hasn't been updated for a
while, which is a good sign that ticket isn't getting worked on. But that
requires somewhat constant re-education effort.
Better yet - just sign it to yourself when you start working on it. Everything
else is a fair game for the rest of the community ;)
Cos
On Fri, Jan 15, 2016 at 08:09PM, Guillaume Laforge wrote:
> I'm fine with that too.
> Historically, there was often someone more focused on this or that part,
> and with JIRA components, we could pre-assign an issue so the person could
> handle it or triage it and route it to the right person.
> But it's more because JIRA allowed that that we did it, more than because
> that was the best way to deal with our tickets :-)
> I think we just need to remove JIRA component leads to avoid the auto
> assignment.
>
> Guillaume
>
>
> Le vendredi 15 janvier 2016, John Wagenleitner <jo...@gmail.com>
> a écrit :
>
> > I agree, I think turning off auto-assignment would be a good idea.
> >
> > +1
> >
> > On Fri, Jan 15, 2016 at 10:42 AM, Pascal Schumacher <
> > pascalschumacher@gmx.net
> > <javascript:_e(%7B%7D,'cvml','pascalschumacher@gmx.net');>> wrote:
> >
> >> Hello everybody,
> >>
> >> I think should disable auto-assignment of jira issues. Dozen of issues
> >> are assigned to people who do not currently work on them. I believe this
> >> stops people from contributing, because they think somebody is already
> >> working on the issue. It also mislead users to expect that the issue will
> >> be fixed soon.
> >>
> >> What do you think?
> >>
> >> Cheers,
> >> Pascal
> >>
> >
> >
>
> --
> Guillaume Laforge
> Apache Groovy committer & PMC member
> Product Ninja & Advocate at Restlet <http://restlet.com>
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge <http://twitter.com/glaforge> / Google+
> <https://plus.google.com/u/0/114130972232398734985/posts>
Re: Disable auto-assignment of jira issues?
Posted by Guillaume Laforge <gl...@gmail.com>.
I'm fine with that too.
Historically, there was often someone more focused on this or that part,
and with JIRA components, we could pre-assign an issue so the person could
handle it or triage it and route it to the right person.
But it's more because JIRA allowed that that we did it, more than because
that was the best way to deal with our tickets :-)
I think we just need to remove JIRA component leads to avoid the auto
assignment.
Guillaume
Le vendredi 15 janvier 2016, John Wagenleitner <jo...@gmail.com>
a écrit :
> I agree, I think turning off auto-assignment would be a good idea.
>
> +1
>
> On Fri, Jan 15, 2016 at 10:42 AM, Pascal Schumacher <
> pascalschumacher@gmx.net
> <javascript:_e(%7B%7D,'cvml','pascalschumacher@gmx.net');>> wrote:
>
>> Hello everybody,
>>
>> I think should disable auto-assignment of jira issues. Dozen of issues
>> are assigned to people who do not currently work on them. I believe this
>> stops people from contributing, because they think somebody is already
>> working on the issue. It also mislead users to expect that the issue will
>> be fixed soon.
>>
>> What do you think?
>>
>> Cheers,
>> Pascal
>>
>
>
--
Guillaume Laforge
Apache Groovy committer & PMC member
Product Ninja & Advocate at Restlet <http://restlet.com>
Blog: http://glaforge.appspot.com/
Social: @glaforge <http://twitter.com/glaforge> / Google+
<https://plus.google.com/u/0/114130972232398734985/posts>
Re: Disable auto-assignment of jira issues?
Posted by John Wagenleitner <jo...@gmail.com>.
I agree, I think turning off auto-assignment would be a good idea.
+1
On Fri, Jan 15, 2016 at 10:42 AM, Pascal Schumacher <
pascalschumacher@gmx.net> wrote:
> Hello everybody,
>
> I think should disable auto-assignment of jira issues. Dozen of issues are
> assigned to people who do not currently work on them. I believe this stops
> people from contributing, because they think somebody is already working on
> the issue. It also mislead users to expect that the issue will be fixed
> soon.
>
> What do you think?
>
> Cheers,
> Pascal
>