Edgewall Software
Modify

Opened 15 years ago

Last modified 6 years ago

#3251 new enhancement

A documentation about components should be added

Reported by: dcarter@… Owned by:
Priority: normal Milestone: next-major-releases
Component: wiki system Version: 0.9.6
Severity: minor Keywords: component wiki documentation
Cc: linuxadmin@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description

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.

Attachments (0)

Change History (17)

comment:1 by Matthew Good, 15 years ago

Resolution: worksforme
Status: newclosed

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

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

comment:2 by neokilly, 15 years ago

Component: ticket systemwiki
Keywords: component wiki added
Milestone: 0.10
Resolution: worksforme
Status: closedreopened
Summary: No documented means of changing the components in the ticket systemA documentation about components should be added
Type: defecttask
Version: 0.9.50.9.6

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

comment:3 by Christian Boos, 15 years ago

Milestone: 0.100.10.1

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.

comment:4 by neokilly, 15 years ago

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

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

comment:5 by neokilly, 15 years ago

Done!

See TracTickets and its diff

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

comment:6 by neokilly, 15 years ago

Oh, and thanks for such a great software!

in reply to:  1 comment:7 by sid@…, 15 years ago

Resolution: fixed
Status: reopenedclosed

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

Looks done to me.

comment:8 by Christian Boos, 15 years ago

Resolution: fixed
Status: closedreopened

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.

comment:9 by sid, 15 years ago

Perhaps TicketComponent should also be renamed to TracTicketComponent?

comment:10 by Christian Boos, 14 years ago

Milestone: 0.10.50.12

Probably worth it when we have "real" components.

comment:11 by Ivan G Shevchenko <linuxadmin@…>, 13 years ago

Cc: linuxadmin@… added

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

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

in reply to:  11 comment:12 by Christian Boos, 13 years ago

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.

comment:13 by Christian Boos, 13 years ago

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

comment:14 by Christian Boos, 13 years ago

Keywords: documentation added
Milestone: 0.130.12
Severity: normalminor
Type: taskenhancement

Moving alongside #1233.

comment:15 by Remy Blank, 12 years ago

Milestone: 0.12next-minor-0.12.x

comment:16 by Christian Boos, 11 years ago

Milestone: next-minor-0.12.xnext-major-0.1X

comment:17 by Ryan J Ollos, 6 years ago

Owner: Jonas Borgström removed
Status: reopenednew

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.