On 27 July 2013 12:10, janI <j...@apache.org> wrote: > On 27 July 2013 12:54, sebb <seb...@gmail.com> wrote: > >> On 27 July 2013 11:47, janI <j...@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 "iss...@openoffice.apache.org", and then > use this report as basis for a script (or what its called in BZ) that > assigns the issues to "iss...@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-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
