groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Laforge <glafo...@gmail.com>
Subject Re: Disable auto-assignment of jira issues?
Date Wed, 20 Jan 2016 19:16:38 GMT
Okie dokie, thanks Pascal.


On Wed, Jan 20, 2016 at 7:51 PM, Pascal Schumacher
<pascalschumacher@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+

Mime
View raw message