5

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.

jmort253
  • 9,537
  • 7
  • 42
  • 88
a coder
  • 153
  • 4

1 Answers1

5

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

The Trac Ticket System

Hope that helps.

Bill the Lizard
  • 1,533
  • 11
  • 21
edgaralgernon
  • 414
  • 2
  • 5
  • 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 04 '12 at 18:31
  • 2
    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 04 '12 at 18:35