Hi Yoheeb, Thanks for the response.
I was hoping there would already be plugins/scripts to assist this process .. but so far, my search has come up empty. I will try appending the version tag to all my URLs .. though, I expect this brute-force approach will become cumbersome over time, and be subject to operator errors .. still .. it's worth a shot. i'm also concerned about managing attachments. once i stabilize version 1.0 of the wiki spec, any future update of the attached graphics will no longer be Overwritten .. meaning my list of attachments may easily become longer than the wiki page itself. We can live with simple and featured-limited .. as long as we can have some semblance of version control. I will run some tests and report back. If anyone has plugin suggestions, please let me know .. a preliminary search of trac-hacks came up empty. cheers, -jeremy On Apr 3, 12:07 pm, yoheeb <[email protected]> wrote: > On Apr 3, 10:49 am, Jeremy Kerr <[email protected]> wrote: > > > > > Hello, > > > We are currently writing all of our feature specifications directly in Trac > > Wiki. > > > We will be using Trac to assign tickets that point directly to the > > applicable page of the spec. > > > Since the Specs will be constantly evolving, how do we go about pointing a > > specific Trac ticket to a specific Wiki page revision? > > > In other words. We need pointer to the wiki in a trac ticket to go to the > > version of the spec at the time the ticket was created. We don't want the > > trac tickets to point to the latest version. > > > Possible? > > > Thanks! > > > -jeremy > > append > ?version=NN to link. if you need to know the "current" version of a > page, you can view the history link in the lower meta-nav > i.e.: > [wiki:FeatureReqPageX?version=11] > > I haven tried a sublink there, so not sure how it works, or if. I > would think it would be [wiki:FeatureReqPageX#ReqX-Y?version=11] or > whatever ymmv. > > Also, > > I would like very much to know how this works out for you, tips, and > tricks/plugins/etc/ used to do this. We are looking at something > similiar, as a "desire" but not sure how to get there. What we can't > see is a way to generate a traceability matrix up/down to different > level of requirements, and test cases (assuming a test case is NOT a > ticket, or maybe it is, or both...) I am thinking that might be an > external tool that parses wiki pages via xmlrpc or something. In your > case, how do you plan to manage traceability from your feature > requirement(s) to the system requirement "document" (wiki page > entries) > > Maybe some macros plus the graphviz plugin could work...hmmm. > > Anyway, good luck, keep us posted.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
