This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 20867 - The component list could be better organized
Summary: The component list could be better organized
Status: RESOLVED INVALID
Alias: None
Product: obsolete
Classification: Unclassified
Component: collabnet (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: support
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-25 21:45 UTC by Jing Xue
Modified: 2009-11-08 02:29 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jing Xue 2002-02-25 21:45:11 UTC 
When a user chooses to enter a new ticket, a list of components is presented 
for the user to choose the component that the ticket is about.  It would be a 
lot nicer if these components could be organized into a few categories, or even 
a tree structure, instead of simply listed alphabetically.  With an 
alphabetically sorted list, one would have to know the name of the component to 
actually find it.  It's not very easy some times, especially for people that 
are not part of the NB development team.
Comment 1 jcatchpoole 2002-03-26 14:48:56 UTC 
I guess this should be filed as an enhancement request for
Scarab, the issue tracking system that Collab will replace
IZ with.
Comment 2 Taska 2002-03-28 22:35:30 UTC 
Hmm.  Well, that's the reason we have components and subcomponents;
there's essentially a tree structure implied there.  Do you want an
extra level of tree structure?

Assigning to Jack; if you want to assign to J. Xue for more info,
that's fine.
Comment 3 jcatchpoole 2002-03-29 11:41:42 UTC 
Erm - I think all we need is already here.

At http://openide.netbeans.org/issues/enter_bug.cgi there
is a single long list of modules.  It would be nice if
this list was broken up into categories, each with their
own set of modules.  SourceCast already has modules
broken out into categories - thecore, experimental, etc in
our case - so an obvious choice would be to use that setup.
If not that then some other, user-configurable grouping of
modules.
Comment 4 Taska 2002-03-29 16:19:31 UTC 
Okay, I see what you mean.
Comment 5 jcatchpoole 2002-05-17 13:20:43 UTC 
*** Issue 23547 has been marked as a duplicate of this issue. ***
Comment 6 kat 2002-05-29 00:12:44 UTC 
This has been filed as pcn9801 for evaluation by our product
management team. I will keep you updated on its progress.
Comment 7 kat 2002-05-30 20:05:10 UTC 
Scarab will address this issue in the following way:
You enter defects from a specific project which is categorized via
SourceCast (the core, experimental, etc.), and can query across
projects to retrieve all the issues
that you care about.
Comment 8 Unknown 2002-08-22 02:13:14 UTC 
This has been addressed in Scarab. We can verify or reopen 
if necessary when Scarab is set up for you.
Comment 9 jcatchpoole 2002-10-02 08:13:04 UTC 
*** Issue 27339 has been marked as a duplicate of this issue. ***
Comment 10 jcatchpoole 2002-11-13 11:28:24 UTC 
*** Issue 20010 has been marked as a duplicate of this issue. ***
Comment 11 padmar 2006-11-01 12:57:15 UTC 
This has been implemented in Scarab. While defining lists it is possible to
categrize the various options.

Marking as verified
Comment 12 Marian Mirilovic 2009-11-08 02:29:42 UTC 
We recently moved out from Collabnet's infrastructure