Actually, even for "closed shop" software teams this would be very helpful when dealing with many different projects... Either that or having the notion of a "project" which can have multiple "reviews"... Currently, if multiple teams do frequent reviews on different projects, it's almost impossible to use codestriker in a reasonable fashion.
--------------------------- Its true, you can enter anything you like in this field. At the moment, Codestriker doesn't authenticate "users" or even really have the notion of a user. Something on our list of things to do eventually. In practice however, for closed-shop software teams, this rarely seems to be a real issue. > Also is it possible to restrict topic state modification only to > reviewer of the > topic? Again - this would require user authentication/authorisation - something on our list of things to do. Cheers, David ------------------------------ ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE V ------------------------------ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Codestriker-user mailing list Codestriker-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/codestriker-user
