On Wed, May 2, 2012 at 8:10 AM, Marcel de Rooy <M.de.Rooy@rijksmuseum.nl>wrote:
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?
Like Owen, I try to address most label/card related bugs of which I am the default assignee. I am not convinced that blanking the default assignee would result in much good. Probably a better move would be to encourage developers who decide to work on a bug to do two things: 1. Click the "take" link next to the assignee field. 2. Set the status to "Assigned." Probably any current confusion is due to one of two things: 1. Bugs currently being worked on, but the developer doing the work has failed to do the two things mentioned above. 2. Lack of understanding on the "unaware Bugzilla user's" part which is better remedied by becoming "aware" of how bugzilla works rather than trying to build a better mouse trap. If things were really this difficult, I suspect that Bugzilla would be swamped with enhancement requests or out of business, one. Kind Regards, Chris
Perhaps the answer is to blank only those modules, where the default assignee does not say he/she wants to keep it? This way we will start again from a clean state and can add new module maintainers later on if someone volunteers. Katrin From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Chris Nighswonger Sent: Wednesday, May 02, 2012 3:45 PM To: koha-devel@lists.koha-community.org Subject: [Koha-devel] Bugzilla component categories On Wed, May 2, 2012 at 8:10 AM, Marcel de Rooy <M.de.Rooy@rijksmuseum.nl> wrote: 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? Like Owen, I try to address most label/card related bugs of which I am the default assignee. I am not convinced that blanking the default assignee would result in much good. Probably a better move would be to encourage developers who decide to work on a bug to do two things: 1. Click the "take" link next to the assignee field. 2. Set the status to "Assigned." Probably any current confusion is due to one of two things: 1. Bugs currently being worked on, but the developer doing the work has failed to do the two things mentioned above. 2. Lack of understanding on the "unaware Bugzilla user's" part which is better remedied by becoming "aware" of how bugzilla works rather than trying to build a better mouse trap. If things were really this difficult, I suspect that Bugzilla would be swamped with enhancement requests or out of business, one. Kind Regards, Chris
It is great that some of the default assignees already stood up for their categories! Probably we can still wait a while and then ask the other ones if they still want to remain listed as assignees or be moved to CC? ________________________________ Van: koha-devel-bounces@lists.koha-community.org [koha-devel-bounces@lists.koha-community.org] namens Fischer, Katrin [Katrin.Fischer@bsz-bw.de] Verzonden: woensdag 2 mei 2012 16:51 To: Chris Nighswonger; koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] Bugzilla component categories Perhaps the answer is to blank only those modules, where the default assignee does not say he/she wants to keep it? This way we will start again from a clean state and can add new module maintainers later on if someone volunteers. Katrin From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Chris Nighswonger Sent: Wednesday, May 02, 2012 3:45 PM To: koha-devel@lists.koha-community.org Subject: [Koha-devel] Bugzilla component categories On Wed, May 2, 2012 at 8:10 AM, Marcel de Rooy <M.de.Rooy@rijksmuseum.nl<mailto:M.de.Rooy@rijksmuseum.nl>> wrote: 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? Like Owen, I try to address most label/card related bugs of which I am the default assignee. I am not convinced that blanking the default assignee would result in much good. Probably a better move would be to encourage developers who decide to work on a bug to do two things: 1. Click the "take" link next to the assignee field. 2. Set the status to "Assigned." Probably any current confusion is due to one of two things: 1. Bugs currently being worked on, but the developer doing the work has failed to do the two things mentioned above. 2. Lack of understanding on the "unaware Bugzilla user's" part which is better remedied by becoming "aware" of how bugzilla works rather than trying to build a better mouse trap. If things were really this difficult, I suspect that Bugzilla would be swamped with enhancement requests or out of business, one. Kind Regards, Chris
participants (4)
-
Chris Nighswonger -
Fischer, Katrin -
Frédéric Demians -
Marcel de Rooy