Hi, Just noticed that when I created an issue this morning it was assigned by default to Jeremi. Is that the behavior we want? Thanks -Vincent ___________________________________________________________________________ Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire. http://fr.mail.yahoo.com
yes, it was wanted. do you want to suggest something else? jeremi On 11/18/06, Vincent Massol <[email protected]> wrote:
Hi,
Just noticed that when I created an issue this morning it was assigned by default to Jeremi. Is that the behavior we want?
Thanks -Vincent
___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com
-- You receive this message as a subscriber of the [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
-- jeremi
I think this depends on the component it was added to If you add to WYSIWYG it will go to Nam Ludovic Vincent Massol a écrit :
Hi,
Just noticed that when I created an issue this morning it was assigned by default to Jeremi. Is that the behavior we want?
Thanks -Vincent
___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com
------------------------------------------------------------------------
-- You receive this message as a subscriber of the [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
-- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic
While I understand the rationale with default assignee, the reason I'm pointing this out is because I've also seen drawbacks of this strategy on other projects and in the end we've removed the default assignee for those projects. The reasons: 1) Assignee means: ok I'll handle that issue. If it's a patch it means I'll apply this patch. The problem is the default assignee may be doing something else and will not handle it before a long time, thus misleading the issue reporter. In practice we often see huge number of issues assigned to someone who doesn't have time to handle them all. So JIRA says they are assigned when in practice they're not really... 2) Even more important, it also means that it doesn't provide free room for someone to work on an issue because it's already assigned. Yes I know anyone could reassign an issue to himself but it's bad practice without asking the first assignee. Thus it takes more time and in practice I doubt lots of people are going to do it as everyone is all too happy to see someone is already assigned! 3) We don't have statistics of issues who are being assigned vs others who are not being managed. Same we don't really know what issues Jeremi (and the component leads in generam) are really working on. It's not a big deal but I was just surprised and I know perfectly well Jeremi is not going to work anytime soon (if ever actually!) on the issue I created and which was assigned automatically to him. It just looked strange. If the idea is for the component lead to notice the issues then this can be done in 2 ways: * by sending all jira issues to the commit list. We really NEED this. * by changing the notification (if it's not already like this) so that component lead receive notifications for all issues for their component. I personally think it's much better for someone to say explicitely: I'm assigning these issues to me as I'm going to work on them rather than them being assigned by default. In this manner this person will commit himself. WDYT? Thanks -Vincent
-----Original Message----- From: Ludovic Dubost [mailto:[email protected]] Sent: mardi 21 novembre 2006 00:31 To: [email protected] Subject: Re: [xwiki-dev] [JIRA] Assignee by default?
I think this depends on the component it was added to If you add to WYSIWYG it will go to Nam
Ludovic
Vincent Massol a écrit :
Hi,
Just noticed that when I created an issue this morning it was assigned by default to Jeremi. Is that the behavior we want?
Thanks -Vincent
_____ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com
---------------------------------------------------------------------
______________________________________________________________________ -
--
-- You receive this message as a subscriber of the xwiki- [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
-- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic
___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
+1 On 11/21/06, Vincent Massol <[email protected]> wrote:
While I understand the rationale with default assignee, the reason I'm pointing this out is because I've also seen drawbacks of this strategy on other projects and in the end we've removed the default assignee for those projects. The reasons:
1) Assignee means: ok I'll handle that issue. If it's a patch it means I'll apply this patch. The problem is the default assignee may be doing something else and will not handle it before a long time, thus misleading the issue reporter. In practice we often see huge number of issues assigned to someone who doesn't have time to handle them all. So JIRA says they are assigned when in practice they're not really...
2) Even more important, it also means that it doesn't provide free room for someone to work on an issue because it's already assigned. Yes I know anyone could reassign an issue to himself but it's bad practice without asking the first assignee. Thus it takes more time and in practice I doubt lots of people are going to do it as everyone is all too happy to see someone is already assigned!
3) We don't have statistics of issues who are being assigned vs others who are not being managed. Same we don't really know what issues Jeremi (and the component leads in generam) are really working on.
It's not a big deal but I was just surprised and I know perfectly well Jeremi is not going to work anytime soon (if ever actually!) on the issue I created and which was assigned automatically to him. It just looked strange.
If the idea is for the component lead to notice the issues then this can be done in 2 ways: * by sending all jira issues to the commit list. We really NEED this. * by changing the notification (if it's not already like this) so that component lead receive notifications for all issues for their component.
I personally think it's much better for someone to say explicitely: I'm assigning these issues to me as I'm going to work on them rather than them being assigned by default. In this manner this person will commit himself.
WDYT?
Thanks -Vincent
participants (4)
-
jeremi joslin -
Ludovic Dubost -
Sergiu Dumitriu -
Vincent Massol