Opened 19 years ago
Closed 19 years ago
#2214 closed task (invalid)
Trac as a POW system
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | low | Milestone: | |
Component: | wiki system | Version: | 0.8.4 |
Severity: | normal | Keywords: | POW trac cvs |
Cc: | graeme.christie@…; gary.liney@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
TRAC doesn't quite have the feature set to satisfy the requirements for the POW. While it does integrate code repositories (subversion, which we don't use, cvs support coming … one day), bug submissions and a wiki really nicely, it's not strong on resource (ie developers) allocation, project prioritisation and project governance (submitting, justify and approving projects etc) which is the main focus of the POW tool.
This is really a developers tool for developing. The POW is mostly a managers tool for managing … and it's scope has blown right out beyond development/systems .. All sorts of teams across IP services want access to the POW tool for managing all sorts of projects.
I would love to see something like TRAC "hooked into" a POW tool.
E.g. Assigned POW projects/tasks automatically become TRAC tasks, which can be updated through TRAC and on completion update the POW etc. Activity on a POW task can be guaged by examing the TRAC activity (frequency of code submissions etc).
Not likely we would get the dev resources to do something like this though.
Cheers,
Graeme
Attachments (0)
Change History (4)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 19 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Please don't close tickets as "fixed" unless an actual fix in Trac was required.
comment:4 by , 19 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
Oh, I thought I was posting to our internal test trac system, but the link was for edgewalls trac system. You can probably ignore this