Modify ↓
Opened 18 years ago
Closed 18 years ago
#3746 closed enhancement (duplicate)
Groupable components
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | ticket system | Version: | none |
| Severity: | normal | Keywords: | component |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Could it be possible to add a group attribute to a component, so that it can be rendered in an <optgroup> tag?
On a project with a lot of components I think it is a benefit to have this feature. Clearly arranged components can help to increase the acceptence by users/reporters. Also if you use Trac not for software projects only…
Sample: GUIs
Administration Management User
Hardware
DB Server Webserver Workstation foo
…
Attachments (0)
Change History (1)
comment:1 by , 18 years ago
| Keywords: | component added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Actually, it might be better to use hierarchical component names to achieve this, as the queries could easily take benefit from this.
Now, on the UI side, we could transform that hierarchy into a selection field using <optgroup> elements, so that the common prefix is not repeated.
See rather #548.