By Date: <-- -->
By Thread: <-- -->

Requirements Managements Tool

Sorry for removing extra line to keep text short.

In my case, RDs release alpha/beta version every week, then PM put bug
report as ticket in Trac. For adding Version in tickets, we have to
authoring PM to use trac-admin as administrator. I don't think it's a
standard operation. It could be better if there was
VERSION_ADMIN/VERSION_CREATE/VERSION_MODIFY permission or VERSION can be
imported automatically from SVN tags.
Besides, can ticket add a Date Type field? I can only add a field as Text
instead of Date. This Date field is used as dead-line, who was assigned this
ticket must close ticket before it.

Please take there two suggestions as reference.

Regards,
Alex Lee

> we are using trac too for requirements management. versioning of
> tickets is "solved" by doing a report/query and copy-paste into
> excel/word and save it like that. ticket dependencies somehow lacking:
> * depending
> * duplicate
> * maybe: related to
> * and we do not feel we'd need a "blocks", isn't it the inverse of
"depending"?

> we'd use custom fields for the dependencies, but they are not
> "wikified" for the moment. but we think intertrac, trac dependencies
> will solve the problem in a general way superiour of every other
> approach i know of.

> a feature like "give everything at a certain point in time" is a
> little missing. with wiki it would be possible, with the attached
> source code it should be easy, but with the tickets?

> -solo


_______________________________________________
Trac mailing list
Trac (at) lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac