The HACK212 issue would be cool. However, As for the HACK211: > hacky2004-all:JavaMap > Clew2-UH:Books
I am not sure this would be better way because hacky2004-all:JavaMap csdl2004-all:JavaMap would be the same review id. this wouldn't be useful for the user perspective because both are the exactly same analysis. Since project is just to be concerned to filter out the set of review ID the user can see, I would just eliminate the project name from the combo list, I will make <module_name> - <review_id> by filtering them by project. The list elements would be something like: hackyStdExt-JavaMap hackyJira-IssueStd On Sun, 06 Mar 2005 08:16:33 -1000 Philip Johnson <[EMAIL PROTECTED]> wrote: > --On Saturday, March 5, 2005 1:05 AM -1000 Aaron Kagawa > <[EMAIL PROTECTED]> wrote: > > > I would personally, like a single drop down selector that provides the > > Project and Review Id. Therefore, I wouldn't have to know what Project the > > Review Id is in. So, for my selector it would have the following entries: > > - Project:hacky2004-all ReviewId:JavaMap > > Great idea! Takuya and I discussed this issue as well, but we didn't come > up with this solution. > > I think we could even abbreviate it more: > > hacky2004-all:JavaMap > Clew2-UH:Books > > We can just document that this selector uses <Project>:<ReviewID> format. > > <http://hackydev.ics.hawaii.edu:8080/browse/HACK-211> > > > This is pretty cool. but, It is a little hard to quickly understand what > > happened and I would like to see more details. The details i would like to > > see are as follows: > > 1) Three Sections (different tables): (1) a summary, (2) a drill down > > section for Review Active Time, and (3) a drill down section for Review > > Issues. > > Also excellent and very congruent with our other analyses. Takuya, do you > see any problems with making these changes? > > <http://hackydev.ics.hawaii.edu:8080/browse/HACK-212> > > Cheers, > Philip ================================ Takuya Yamashita E-mail: [EMAIL PROTECTED] ================================
