Hello,

We're looking at moving our bugbase, currently giving Trac a trial
run, and in the process considering what possibilities it may offer
us.  We've been using Rational RequisitePro for tracking requirements,
specifications, and even defects.  That last one is quite a stretch I
must say.

Now I'm curious about moving our requirements and specifications into
Trac as well.  Basically what RequisitePro gives you is the ability to
tag and track items in a document.  Our typical usage is to write a
document, review it, and then tag it.  Tagging is done quite easily by
highlighting the text, entering attributes (field values) to use, and
having it automatically make a database item of each paragraph (how it
determines where one spec ends and the next begins is configurable).
Now you've got a document that can be read as a document, plus
trackable items in a database.

I can imagine doing something similar with Trac but with my limited
knowledge it seems like it would be very tedious to set up - writing
up individual tickets for each spec and filling out fields for each
(could at least be done all at once with BatchModify), then collecting
them into one or more wiki pages using macros to include the
description text (TicketQuery?).

Any suggestions for doing it the other way - by writing and reviewing
a wiki page first and then without a lot of manual effort making
tickets of items on the page?  Could this be done with a custom plug-
in?  Perhaps something that adds a button at the bottom of a wiki page
that when pressed would process the page content, creating tickets,
and replacing the current wiki content with macros to include the new
tickets' text?

- jevans

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to