Once an issue type is picked, I think you can still select multiple applicable components.
For example, if issue type is a "Bug", you can specify that it is a bug relating to the CORBA component *and* the OpenEJB component. Or if the issue type is an "Improvement", you can specify that it is relating to the kernel and Tomcat components. If the above is correct, then issue type of "Usability" would work quite well; allowing the user to specify the related components (if she/he is able to determine it), or Unknown otherwise. - Sing --- Jacek Laskowski <[EMAIL PROTECTED]> wrote: > Dain Sundstrom wrote: > > Interesting idea. I see two ways to handle this. > We could add a new > > "Component" which is currently used for things > like connector, CORBA, > > kernel, OpenEJB etc. Alternatively we could add > another "Issue Type" > > which is currently used for types such as Bug, > Feature, Imporvement, > > Test, and Wish. > > > > I'm leaning towards a new Issue Type, but what > does everyone else thing? > > I think that adding a new Component would let us > mark a "compound" task > appropriately that would otherwise fall into two or > more areas - kernel, > corba, openejb, etc. and pollute JIRA a little. > > With a new Issue Type it would not be possible to > select a appropriate > component. Besides, if it doesn't work, we could > change it and fall back > to an issue type. > > [X] Add a new "Usability" component. > > > -dain > > Jacek > >
