Descriptions of Components

[Matthew Harrison]

One annoying problem we have with our existing bug-tracking system is that users often don't know what component to select for a ticket. They often end up choosing an inappropriate one.

One could argue that better component names would minimise this, but I've often found users to be endlessly creative in their quest to misunderstand the (seemingly) obvious ;-) A nice feature of bugzilla is that the component selector label is a link to a page listing the components for the project, along with owner and description. (If you prefer the link could be a separate item, like a '?' icon.)

(Currently I'm conducting a trial of trac, and I quite like it!)

[cboos]

A component could be a specific Trac object. Clicking on a component would go to its page, which would contain a wiki description.

See other suggested use for a Component object in TracMultipleProjects/SingleEnvironment#UsingComponentobjects.

[cmlenz]

Components now have a "description" column in the table. It's not being used yet, but it will be in the future for this purpose.

[cboos]

(changing the status, as I've not actually started to work on that yet)

[cboos]

Can be done in GenericTrac, as a second step, in order to validate the steps needed to create of a new kind of resource.

[cboos]

#5860 closed as duplicate (was asking to actually make use of the component description that one can already set in the component admin panel).

[cboos]

Replying to cmlenz:

Components now have a "description" column in the table. It's not being used yet, but it will be in the future for this purpose.

Re-focusing this ticket for this goal. For the idea of having components as first-class object in the Trac system, see #3911. #7411 closed as duplicate of this ticket.