Project Management Stack Exchange is a question and answer site for project managers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In order to better track issues and plan development of an ever-expanding web application, I am setting up an instance of Trac. As developer, I will use this system primarily, along with the department coordinator and a few end-users.

Most of the Trac configuration is relatively self-explanatory, however I am a little unsure how to use the components option (on the ticket form).

Should I include components of the application itself (ie, product page, user administration, reports, ect) or is this field designed for higher level objects (such as users, coordinators, developers) or something else entirely?

I will be using Trac to keep track of bugs, regular maintenance, server maintenance, and new development among other things.

share|improve this question
up vote 5 down vote accepted

Well based on Trac's website docs... "Component — The project module or subsystem this ticket concerns."

The Trac Ticket System

Hope that helps.

share|improve this answer
That's what I assumed, but I wanted to make sure I'm using the field correctly - in a project management sense. – a coder Oct 4 '12 at 18:31
from a PM point of view? their definition makes sense. As a PM I can compare fixes vs. new dev on the component in case some prioritization is needed. – edgaralgernon Oct 4 '12 at 18:35

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.