You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by janI <ja...@apache.org> on 2013/07/27 12:47:36 UTC
unassign BZ issues.
Hi
@rob, you are the BZ expert, is it possible to automate a BZ process, that
unassigns BZ issues, assigned to a person but untouched for a year ?
see
https://issues.apache.org/ooo/show_bug.cgi?id=122035
I think its important, that issues not being worked on are kept in the
global pool so it is obvious that anyone can work on it.
rgds
jan I.
Re: unassign BZ issues.
Posted by janI <ja...@apache.org>.
On 27 July 2013 14:00, Rob Weir <ro...@apache.org> wrote:
> On Sat, Jul 27, 2013 at 6:47 AM, janI <ja...@apache.org> wrote:
> > Hi
> >
> > @rob, you are the BZ expert, is it possible to automate a BZ process,
> that
> > unassigns BZ issues, assigned to a person but untouched for a year ?
> >
>
> It is possible to do bulk operations on the result sets of a Bugzilla
> query. This includes resetting the assigned developer. So if we can
> query for it, we can change it.
>
> In fact, last year I did quite a bit of this, resetting the assignee
> for all bugs assigned to *.sun.com or *.openoffice.org email
> addresses.
>
> There is also a way for BZ admins to disable temporarily the email
> notifications while doing such changes, to avoid sending 1,000 email
> notifications. I did that, for example, when rearranging the BZ
> products and components.
>
> thx for the explanation.
@regina: thx for the precise sef of instructions.
I suggest we wait for lazy consensus, and then when a BZ-admin has spare
cycles get it done (I am not a BZ-admin and would not like to cause a mail
flood). It would be nice out of interest to know how many issues it hit.
Then we can repeat every half year or so, like I do on mwiki with old user
accounts.
rgds
jan I.
> -Rob
>
> > see
> > https://issues.apache.org/ooo/show_bug.cgi?id=122035
> >
> > I think its important, that issues not being worked on are kept in the
> > global pool so it is obvious that anyone can work on it.
> >
> > rgds
> > jan I.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
Re: unassign BZ issues.
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
Am 07/27/2013 03:21 PM, schrieb Rob Weir:
> On Sat, Jul 27, 2013 at 9:02 AM, Marcus (OOo)<ma...@wtnet.de> wrote:
>> Am 07/27/2013 02:00 PM, schrieb Rob Weir:
>>>
>>> On Sat, Jul 27, 2013 at 6:47 AM, janI<ja...@apache.org> wrote:
>>>>
>>>>
>>> There is also a way for BZ admins to disable temporarily the email
>>> notifications while doing such changes, to avoid sending 1,000 email
>>> notifications. I did that, for example, when rearranging the BZ
>>> products and components.
>>
>>
>> Is this a feature for BZ admins only or is it also useable for normal BZ
>> users resp. can be made accessible to them?
>>
>
> No, it is deeper in the configuration. It disables email
> notifications in general, not just for the given transaction. So it
> must be used very carefully. When I do it I do it on weekends,
> off-hours, and send a note to the dev/qa list first, so we know that
> this is happening.
OK, just wanted to know if this could be used by accident by any user.
JIRA, for example, provides an option for every user to disable mail
notifications when doing bulk changes. Very easy and comfortable but at
the same time also very dangerous.
Marcus
>>>> see
>>>> https://issues.apache.org/ooo/show_bug.cgi?id=122035
>>>>
>>>> I think its important, that issues not being worked on are kept in the
>>>> global pool so it is obvious that anyone can work on it.
>>>>
>>>> rgds
>>>> jan I.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: unassign BZ issues.
Posted by Rob Weir <ro...@apache.org>.
On Sat, Jul 27, 2013 at 9:02 AM, Marcus (OOo) <ma...@wtnet.de> wrote:
> Am 07/27/2013 02:00 PM, schrieb Rob Weir:
>>
>> On Sat, Jul 27, 2013 at 6:47 AM, janI<ja...@apache.org> wrote:
>>>
>>>
>> There is also a way for BZ admins to disable temporarily the email
>> notifications while doing such changes, to avoid sending 1,000 email
>> notifications. I did that, for example, when rearranging the BZ
>> products and components.
>
>
> Is this a feature for BZ admins only or is it also useable for normal BZ
> users resp. can be made accessible to them?
>
No, it is deeper in the configuration. It disables email
notifications in general, not just for the given transaction. So it
must be used very carefully. When I do it I do it on weekends,
off-hours, and send a note to the dev/qa list first, so we know that
this is happening.
-Rob
> Thanks
>
> Marcus
>
>
>
>
>>> see
>>> https://issues.apache.org/ooo/show_bug.cgi?id=122035
>>>
>>> I think its important, that issues not being worked on are kept in the
>>> global pool so it is obvious that anyone can work on it.
>>>
>>> rgds
>>> jan I.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: unassign BZ issues.
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
Am 07/27/2013 02:00 PM, schrieb Rob Weir:
> On Sat, Jul 27, 2013 at 6:47 AM, janI<ja...@apache.org> wrote:
>>
> There is also a way for BZ admins to disable temporarily the email
> notifications while doing such changes, to avoid sending 1,000 email
> notifications. I did that, for example, when rearranging the BZ
> products and components.
Is this a feature for BZ admins only or is it also useable for normal BZ
users resp. can be made accessible to them?
Thanks
Marcus
>> see
>> https://issues.apache.org/ooo/show_bug.cgi?id=122035
>>
>> I think its important, that issues not being worked on are kept in the
>> global pool so it is obvious that anyone can work on it.
>>
>> rgds
>> jan I.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: unassign BZ issues.
Posted by Rob Weir <ro...@apache.org>.
On Sat, Jul 27, 2013 at 6:47 AM, janI <ja...@apache.org> wrote:
> Hi
>
> @rob, you are the BZ expert, is it possible to automate a BZ process, that
> unassigns BZ issues, assigned to a person but untouched for a year ?
>
It is possible to do bulk operations on the result sets of a Bugzilla
query. This includes resetting the assigned developer. So if we can
query for it, we can change it.
In fact, last year I did quite a bit of this, resetting the assignee
for all bugs assigned to *.sun.com or *.openoffice.org email
addresses.
There is also a way for BZ admins to disable temporarily the email
notifications while doing such changes, to avoid sending 1,000 email
notifications. I did that, for example, when rearranging the BZ
products and components.
-Rob
> see
> https://issues.apache.org/ooo/show_bug.cgi?id=122035
>
> I think its important, that issues not being worked on are kept in the
> global pool so it is obvious that anyone can work on it.
>
> rgds
> jan I.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: unassign BZ issues.
Posted by sebb <se...@gmail.com>.
On 27 July 2013 13:56, Marcus (OOo) <ma...@wtnet.de> wrote:
> Am 07/27/2013 02:16 PM, schrieb sebb:
>
>> On 27 July 2013 12:10, janI<ja...@apache.org> wrote:
>>>
>>> On 27 July 2013 12:54, sebb<se...@gmail.com> wrote:
>>>
>>>> On 27 July 2013 11:47, janI<ja...@apache.org> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> @rob, you are the BZ expert, is it possible to automate a BZ process,
>>>>
>>>> that
>>>>>
>>>>> unassigns BZ issues, assigned to a person but untouched for a year ?
>>>>>
>>>>> see
>>>>> https://issues.apache.org/ooo/show_bug.cgi?id=122035
>>>>>
>>>>> I think its important, that issues not being worked on are kept in the
>>>>> global pool so it is obvious that anyone can work on it.
>>>>
>>>>
>>>> In the main instance, it's not possible to assign issues, because once
>>>> they have been assigned, Bugzilla only sends change notifications to
>>>> the new assignee.
>>>>
>>>
>>> I thought it was possible to make a report containing all issues not
>>> touched a year and not assigned to "issues@openoffice.apache.org", and
>>> then
>>> use this report as basis for a script (or what its called in BZ) that
>>> assigns the issues to "issues@openoffice.apache.org"
>>>
>>> It was not a question of where the mails get sent to, but more to have an
>>> updated list of "who works on what".
>>
>>
>> Yes, I realise that.
>>
>> But should you be allowing issues to be assigned away from the
>> devloper list at all?
>
>
> We have a dedicated mailing list only for BZ issues. That should be enough.
> Everybody who is interested in these mails can subscribe there.
Yes.
>
>> Does it not matter that changes to such issues are no longer reported
>> to the developer list?
>
>
> They were never reported to dev@. And, to be honest, I would not prefer it.
> We have sometimes more than 200 mails from issues per day. Do you want to
> have them all on a dev@ mailing list? ;-)
Yes - by that I mean a mailing list that devs can subscribe to; does
not have to be the dev discussion list.
> At least here in this dev@ not everybody is a developer and works on code.
> I'm sure that is different with other Apache projects.
Sorry, I was a bit lax: when I wrote "the devloper list", I meant "the
developer list used for BZ mails"
> Marcus
>
>
>
>
>>>> Or maybe that particular Bugzilla 'feature' has been fixed in your
>>>> Bugzilla?
>>>>
>>>> Easy enough to check - create a dummy issue and assign it; make some
>>>> changes and see where the mails get sent.
>>>>
>>>
>>>
>>>>
>>>>> rgds
>>>>> jan I.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: unassign BZ issues.
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
Am 07/27/2013 02:16 PM, schrieb sebb:
> On 27 July 2013 12:10, janI<ja...@apache.org> wrote:
>> On 27 July 2013 12:54, sebb<se...@gmail.com> wrote:
>>
>>> On 27 July 2013 11:47, janI<ja...@apache.org> wrote:
>>>> Hi
>>>>
>>>> @rob, you are the BZ expert, is it possible to automate a BZ process,
>>> that
>>>> unassigns BZ issues, assigned to a person but untouched for a year ?
>>>>
>>>> see
>>>> https://issues.apache.org/ooo/show_bug.cgi?id=122035
>>>>
>>>> I think its important, that issues not being worked on are kept in the
>>>> global pool so it is obvious that anyone can work on it.
>>>
>>> In the main instance, it's not possible to assign issues, because once
>>> they have been assigned, Bugzilla only sends change notifications to
>>> the new assignee.
>>>
>>
>> I thought it was possible to make a report containing all issues not
>> touched a year and not assigned to "issues@openoffice.apache.org", and then
>> use this report as basis for a script (or what its called in BZ) that
>> assigns the issues to "issues@openoffice.apache.org"
>>
>> It was not a question of where the mails get sent to, but more to have an
>> updated list of "who works on what".
>
> Yes, I realise that.
>
> But should you be allowing issues to be assigned away from the
> devloper list at all?
We have a dedicated mailing list only for BZ issues. That should be
enough. Everybody who is interested in these mails can subscribe there.
> Does it not matter that changes to such issues are no longer reported
> to the developer list?
They were never reported to dev@. And, to be honest, I would not prefer
it. We have sometimes more than 200 mails from issues per day. Do you
want to have them all on a dev@ mailing list? ;-)
At least here in this dev@ not everybody is a developer and works on
code. I'm sure that is different with other Apache projects.
Marcus
>>> Or maybe that particular Bugzilla 'feature' has been fixed in your
>>> Bugzilla?
>>>
>>> Easy enough to check - create a dummy issue and assign it; make some
>>> changes and see where the mails get sent.
>>>
>>
>>
>>>
>>>> rgds
>>>> jan I.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: unassign BZ issues.
Posted by sebb <se...@gmail.com>.
On 27 July 2013 12:10, janI <ja...@apache.org> wrote:
> On 27 July 2013 12:54, sebb <se...@gmail.com> wrote:
>
>> On 27 July 2013 11:47, janI <ja...@apache.org> wrote:
>> > Hi
>> >
>> > @rob, you are the BZ expert, is it possible to automate a BZ process,
>> that
>> > unassigns BZ issues, assigned to a person but untouched for a year ?
>> >
>> > see
>> > https://issues.apache.org/ooo/show_bug.cgi?id=122035
>> >
>> > I think its important, that issues not being worked on are kept in the
>> > global pool so it is obvious that anyone can work on it.
>>
>> In the main instance, it's not possible to assign issues, because once
>> they have been assigned, Bugzilla only sends change notifications to
>> the new assignee.
>>
>
> I thought it was possible to make a report containing all issues not
> touched a year and not assigned to "issues@openoffice.apache.org", and then
> use this report as basis for a script (or what its called in BZ) that
> assigns the issues to "issues@openoffice.apache.org"
>
> It was not a question of where the mails get sent to, but more to have an
> updated list of "who works on what".
Yes, I realise that.
But should you be allowing issues to be assigned away from the
devloper list at all?
Does it not matter that changes to such issues are no longer reported
to the developer list?
> rgds
> jan I.
>
>
>
>> Or maybe that particular Bugzilla 'feature' has been fixed in your
>> Bugzilla?
>>
>> Easy enough to check - create a dummy issue and assign it; make some
>> changes and see where the mails get sent.
>>
>
>
>>
>> > rgds
>> > jan I.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: unassign BZ issues.
Posted by Regina Henschel <rb...@t-online.de>.
Hi Jan,
janI schrieb:
> On 27 July 2013 12:54, sebb <se...@gmail.com> wrote:
>
>> On 27 July 2013 11:47, janI <ja...@apache.org> wrote:
>>> Hi
>>>
>>> @rob, you are the BZ expert, is it possible to automate a BZ process,
>> that
>>> unassigns BZ issues, assigned to a person but untouched for a year ?
>>>
>>> see
>>> https://issues.apache.org/ooo/show_bug.cgi?id=122035
>>>
>>> I think its important, that issues not being worked on are kept in the
>>> global pool so it is obvious that anyone can work on it.
>>
>> In the main instance, it's not possible to assign issues, because once
>> they have been assigned, Bugzilla only sends change notifications to
>> the new assignee.
>>
>
> I thought it was possible to make a report containing all issues not
> touched a year and not assigned to "issues@openoffice.apache.org", and then
> use this report as basis for a script (or what its called in BZ) that
> assigns the issues to "issues@openoffice.apache.org"
>
> It was not a question of where the mails get sent to, but more to have an
> updated list of "who works on what".
Use the section "Custom search". There you can set for example:
Time Since Assignee Touched is greater then 1200d
AND
Assignee is not equal to
issues@openoffice.apache.org
Of cause in the upper part restrict it to those issues not already fixed
or closed.
1200d results in more than 900 bugs.
Perhaps you want to restrict it to a range of BugID or to special Products.
There are some false positive, but perhaps it is a start.
Before setting back assignee make sure, that no notification mails where
sent, to not spam.
Kind regards
Regina
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: unassign BZ issues.
Posted by janI <ja...@apache.org>.
On 27 July 2013 12:54, sebb <se...@gmail.com> wrote:
> On 27 July 2013 11:47, janI <ja...@apache.org> wrote:
> > Hi
> >
> > @rob, you are the BZ expert, is it possible to automate a BZ process,
> that
> > unassigns BZ issues, assigned to a person but untouched for a year ?
> >
> > see
> > https://issues.apache.org/ooo/show_bug.cgi?id=122035
> >
> > I think its important, that issues not being worked on are kept in the
> > global pool so it is obvious that anyone can work on it.
>
> In the main instance, it's not possible to assign issues, because once
> they have been assigned, Bugzilla only sends change notifications to
> the new assignee.
>
I thought it was possible to make a report containing all issues not
touched a year and not assigned to "issues@openoffice.apache.org", and then
use this report as basis for a script (or what its called in BZ) that
assigns the issues to "issues@openoffice.apache.org"
It was not a question of where the mails get sent to, but more to have an
updated list of "who works on what".
rgds
jan I.
> Or maybe that particular Bugzilla 'feature' has been fixed in your
> Bugzilla?
>
> Easy enough to check - create a dummy issue and assign it; make some
> changes and see where the mails get sent.
>
>
> > rgds
> > jan I.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
Re: unassign BZ issues.
Posted by sebb <se...@gmail.com>.
On 27 July 2013 11:47, janI <ja...@apache.org> wrote:
> Hi
>
> @rob, you are the BZ expert, is it possible to automate a BZ process, that
> unassigns BZ issues, assigned to a person but untouched for a year ?
>
> see
> https://issues.apache.org/ooo/show_bug.cgi?id=122035
>
> I think its important, that issues not being worked on are kept in the
> global pool so it is obvious that anyone can work on it.
In the main instance, it's not possible to assign issues, because once
they have been assigned, Bugzilla only sends change notifications to
the new assignee.
Or maybe that particular Bugzilla 'feature' has been fixed in your Bugzilla?
Easy enough to check - create a dummy issue and assign it; make some
changes and see where the mails get sent.
> rgds
> jan I.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org