Bugzilla component categories
Hi all, Recently we discussed in the QA team to make the default QA contact empty. (Ian cleared this field for all components now [for new reports].) In the process the QA team member that starts QA on a report now, enters his name in the QA contact field. This informs reporter, patch writer, etc. that QA started and is also helpful for other QA team members in order to prevent duplication of work. My question now is: Should we do something similar with the default Assignee per component? In practice, the current default assignees will (most of the time) not be working on reports entered by someone else. Having someone in the Assignee field who is not working on that report, could be a misleading signal for an unaware Bugzilla user. If the default assignee wants to be informed on reports of that category, moving him/her to the default CC list of that component would perhaps be better? The current default assignees are (for one or more components): nengard@gmail.com<mailto:nengard@gmail.com> henridamien@koha-fr.org<mailto:henridamien@koha-fr.org> gmcharlt@gmail.com<mailto:gmcharlt@gmail.com> oleonard@myacpl.org<mailto:oleonard@myacpl.org> chris@bigballofwax.co.nz<mailto:chris@bigballofwax.co.nz> kyle.m.hall@gmail.com<mailto:kyle.m.hall@gmail.com> koha.sekjal@gmail.com<mailto:koha.sekjal@gmail.com> frederic@tamil.fr<mailto:frederic@tamil.fr> cnighswonger@foundations.edu<mailto:cnighswonger@foundations.edu> robin@catalyst.net.nz<mailto:robin@catalyst.net.nz> colin.campbell@ptfs-europe.com<mailto:colin.campbell@ptfs-europe.com> paul.poulain@biblibre.com<mailto:paul.poulain@biblibre.com> wizzyrea@gmail.com<mailto:wizzyrea@gmail.com> Would you agree with this move? (We need of course consensus before doing so.) Would you like to be added as default CC for one or more components? Please respond. Thanks, Marcel
Having someone in the Assignee field who is not working on that report, could be a misleading signal for an unaware Bugzilla user.
I like being the default assignee for OPAC, browser compatibility, and template bugs, and I make every effort to try to address those bugs. What might be nice is if it was understood that if I remove myself from the bug assignment it means it's *not* something I'm going to work on. I find it difficult to track bugs based on whether I'm CC'ed because that's often not a meaningful indicator of my involvement with the bug. I'm subscribed to the bugs mailing list because I like to read new bug reports, but I'm not subscribed to any Bugzilla emails (in Bugzilla preferences) because I don't like getting duplicate notices. I'm assuming that would have to change if I wanted to know when I was automatically CC'ed on a new bug? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
Thanks. Your case could be the exception proving the rule ;) Since you address such bugs, I think you should stay default assignee. ________________________________________ Van: Owen Leonard [oleonard@myacpl.org] Verzonden: woensdag 2 mei 2012 14:25 To: Marcel de Rooy Cc: koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] Bugzilla component categories
Having someone in the Assignee field who is not working on that report, could be a misleading signal for an unaware Bugzilla user.
I like being the default assignee for OPAC, browser compatibility, and template bugs, and I make every effort to try to address those bugs. What might be nice is if it was understood that if I remove myself from the bug assignment it means it's *not* something I'm going to work on. I find it difficult to track bugs based on whether I'm CC'ed because that's often not a meaningful indicator of my involvement with the bug. I'm subscribed to the bugs mailing list because I like to read new bug reports, but I'm not subscribed to any Bugzilla emails (in Bugzilla preferences) because I don't like getting duplicate notices. I'm assuming that would have to change if I wanted to know when I was automatically CC'ed on a new bug? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
Hi Marcel, +1 I was going to propose something similar at the next IRC meeting. I think our current system of default assignees does not really work (with a few exceptions) and your idea to leave the field empty will end a lot of confusion. I was also wondering how bug wranglers could be involved here. We can not 'assign' bugs to someone, but perhaps we could try to improve the bug reports so it's easier to work on them? Confirming the problem, asking questions where information is missing and add/correct information given by the bug reporter. Katrin
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Marcel de Rooy Sent: Wednesday, May 02, 2012 2:36 PM To: Owen Leonard Cc: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Bugzilla component categories
Thanks. Your case could be the exception proving the rule ;) Since you address such bugs, I think you should stay default assignee. ________________________________________ Van: Owen Leonard [oleonard@myacpl.org] Verzonden: woensdag 2 mei 2012 14:25 To: Marcel de Rooy Cc: koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] Bugzilla component categories
Having someone in the Assignee field who is not working on that report, could be a misleading signal for an unaware Bugzilla user.
I like being the default assignee for OPAC, browser compatibility, and template bugs, and I make every effort to try to address those bugs. What might be nice is if it was understood that if I remove myself from the bug assignment it means it's *not* something I'm going to work on.
I find it difficult to track bugs based on whether I'm CC'ed because that's often not a meaningful indicator of my involvement with the bug. I'm subscribed to the bugs mailing list because I like to read new bug reports, but I'm not subscribed to any Bugzilla emails (in Bugzilla preferences) because I don't like getting duplicate notices. I'm assuming that would have to change if I wanted to know when I was automatically CC'ed on a new bug?
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha- community.org/ bugs : http://bugs.koha-community.org/
I'll keep my default assignment for Website issues. :) Liz Rea lrea@nekls.org On May 2, 2012, at 7:10 AM, Marcel de Rooy wrote:
Hi all,
Recently we discussed in the QA team to make the default QA contact empty. (Ian cleared this field for all components now [for new reports].) In the process the QA team member that starts QA on a report now, enters his name in the QA contact field. This informs reporter, patch writer, etc. that QA started and is also helpful for other QA team members in order to prevent duplication of work.
My question now is: Should we do something similar with the default Assignee per component? In practice, the current default assignees will (most of the time) not be working on reports entered by someone else. Having someone in the Assignee field who is not working on that report, could be a misleading signal for an unaware Bugzilla user. If the default assignee wants to be informed on reports of that category, moving him/her to the default CC list of that component would perhaps be better?
The current default assignees are (for one or more components): nengard@gmail.com henridamien@koha-fr.org gmcharlt@gmail.com oleonard@myacpl.org chris@bigballofwax.co.nz kyle.m.hall@gmail.com koha.sekjal@gmail.com frederic@tamil.fr cnighswonger@foundations.edu robin@catalyst.net.nz colin.campbell@ptfs-europe.com paul.poulain@biblibre.com wizzyrea@gmail.com Would you agree with this move? (We need of course consensus before doing so.) Would you like to be added as default CC for one or more components? Please respond. Thanks,
Marcel _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Marcel de Rooy schreef op wo 02-05-2012 om 12:10 [+0000]:
If the default assignee wants to be informed on reports of that category, moving him/her to the default CC list of that component would perhaps be better?
I'd like to remain on the packages. It doesn't bother me whether it's CC or default assignee, but seeing them would be useful. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
participants (5)
-
Fischer, Katrin -
Liz Rea -
Marcel de Rooy -
Owen Leonard -
Robin Sheat