Personal tools
You are here: Home Development trac
Document Actions

trac

by Luis Bermudez last modified 2008-01-31 15:41

Summary of TRAC features and issues

TRAC

TRAC model is presented in the figure above. A ticket is associated to 1 component, 1 milestone and 1 version. Only milestones have due date and completed date. Tasks due not have associated date.

TODOs

  • Create list of components (architecture components and documentation items)
  • Add milestones ( every week )
  • Create list of keywords ( use cases)
  • Create uniform pattern for user id ( e.g. LuisB), so we can re/assign tasks easily.
  • Have a public list of user ids
  • Create useful reports (like report by component). For example to see the status of catalog version X

TRAC issues

  • tasks are not linked together (predecessors, hierarchies, etc..)
  • Not able to manage use cases
  • Not able to manage effort for each task: % complete, estimate effort (time), etc..
  • No drop down to assign or cc users
  • No management user interface ( all is done manually: adding users, assigning permissions, editing components, versions, etc..)

Links


OOSTethys.org: hosted by GoMOOS | powered by Plone