On Jun 1, 10:36 am, Cliff <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Apparently this is fixed inhttp://trac.edgewall.org/ticket/5572   -   Ticket 
> #5572 (closed
> defect: fixed)
>
> However, I'm not sure if the fix was committed to the actual current
> 0.11 beta release. There certainly is no documentation yet on the
> official wiki.
>
> Would anyone have any advise on how I can go about obtaining the
> support forcustomworkflow inroadmapbased on the files attached in
> the ticket?
>
> Thanks,
> Cliff
>
> On May 31, 12:52 pm, Cliff <[EMAIL PROTECTED]> wrote:
>
> > Greetings,
>
> > I would like to enquire if there is any manner to update theRoadmap
> > view to reflectcustomchanges in the trac workflow (http://
> > trac.edgewall.org/wiki/TracWorkflow).
>
> > Specifically, if I were to add new statuses such as a model similar to
> > that described athttp://trac.edgewall.org/wiki/NewWorkflow, where
> > there are new statuses "resolved" and "verified" in addition to the
> > default "closed", how do I update theRoadmapview to recognise
> > "resolved" and "verified" as part of it's "Closed Tickets" computation
> > (as well as the relevant query generated by theRoadmappage to view
> > tickets for the particular milestone that are still Active and Closed)
>
> > Much thanks in advance, :)
> > Cliff

Yes, I'd love more information on this as well.  I see a
CustomRoadmapPlugin but it appears untouched in a year.
Could someone that knows how to read python document the fix for
http://trac.edgewall.org/ticket/5572?
It'd be much appreciated,
- 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