A documentation about components should be added

[dcarter@…]

I'm trying to update the list of components for my ticket system, but I've been unable to find any way in either the gui or configuration that will allow me to do this.

[mgood]

Components can be managed with trac-admin or with the WebAdmin plugin.

In the future please use the MailingList to ask for help.

[neokilly]

In fact, no information about components is given through the default wiki pages (those available after the installation)

I guess the purpose of the original ticket was to point out this fact and to ask if information about components (how to manage them) could be added to the Wiki documentation, as a new chapter for TracGuide, for example

Hoping you would consider this as useful, I've reopened the ticket

[cboos]

Sorry, at this point pushing something into the 0.10 release means it's either a bug fix, or that you have a non-controversial patch ready to apply ;)

So I'm post-poning this. The suggestion in itself is worthwhile though. Maybe you can start by editing TracTickets and perhaps TicketComponent? Though I don't think that at this point components deserve a chapter on their own. Not until they become Trac "resources" themselves, if this happens one day.

[neokilly]

Oops (for the wrong milestone), sure, I do understand

I'll take a look at the wiki pages, thanks

[neokilly]

Done!

See TracTickets and its diff

Please correct any mistakes or faults-due-to-a-french-translation. Hope it can help

[neokilly]

Oh, and thanks for such a great software!

[sid@…]

Okay, I updated those pages as well, building on neokilly's work.

• TracTickets diff
• TicketComponent diff

Looks done to me.

[cboos]

Thanks for the contribution to the documentation. I'll integrate the TicketComponent page in the repos, in a few days. I'll close the ticket at that time.

[sid]

Perhaps TicketComponent should also be renamed to TracTicketComponent??

[cboos]

Probably worth it when we have "real" components.

[Ivan G Shevchenko <linuxadmin@…>]

is #7411 (currently "closed wontfix") a duplicate ticket of this one?

@cbos what are "real" components? is there a proposal? thanx!

[cboos]

Replying to Ivan G Shevchenko <linuxadmin@yandex.ru>:

is #7411 (currently "closed wontfix") a duplicate ticket of this one?

I don't think so, no. This ticket is about the documentation of the usage of components in Trac ("documentation about components should be added").

@cbos what are "real" components? is there a proposal? thanx!

As for now there's really nothing special about components (it's just a list, could as well be a custom field among others), there's IMO nothing special needed in the documentation about them. What's written in TracTicket#TicketFields? should be enough (of course, the information or the wording itself in that page can always be improved).

I think a special, separate page (like the proposed TicketComponent page) would be worth including in the documentation iff the component acquire the status of a first-class object (a.k.a. resource) in the Trac system (see #1233, #1678, #3991), otherwise it's just overkill IMO.

[cboos]

Sorry, read #3911 in the above list of related tickets.