--On Friday, April 8, 2005 2:12 AM -1000 Aaron Kagawa <[EMAIL PROTECTED]> wrote:
This improvement sends issues like < http://hackydev.ics.hawaii.edu:8080/browse/HACK-2> to a default user. HACK-2 is assigned to Dan Port, who is not part of the hacky2004-all project and is not in the usermap.xml file on hackydev. Therefore, HACK-2 has never been collected by Hackystat. With the addition of the default user in the Jira sensor, HACK-2 will now be sent to the default user, which will probably be hackystat-l. Note: I have not yet upgraded the sensor.jira.jar and build.utils.xml to fully finish this new feature. I will do so soon.
I'm not sure about this default user approach, at least in this situation, because it appears to me to result in sending misleading and/or wrong data to Hackystat. The real problem here is that Dan Port needs to be made a member of hacky2004-all and added to the usermap.xml file, not that we need a default user.
Let me propose the following alternative:
* Add an "admin email address" to the Jira sensor ant task, who will be sent an email notification when issues are discovered that are assigned to a user in Jira but for which there is no entry in usermap.xml. That helps immediately identify configuration problems like this one.
* If a development group needs the effect of a 'default user', then then you first need to define an account for an 'agent' (just like we have for [EMAIL PROTECTED]) and associate that with the Project.
* If you create an issue in Jira and don't assign it to anyone, that would be a situation where sending the data to the default user would be appropriate. In this case, the usermap.xml file would have an attribute called something like "UnassignedIssueOwner", which more clearly specifies the intent than "DefaultUser".
How does this sound?
Cheers, Philip
