On Sunday, July 10, 2016 at 11:15:00 PM UTC-7, Cooke, Mark wrote:
>
> Please note: this list prefers plain text and to post in-line or at the 
> bottom (it helps people pick up a thread later on)... 
>
> > -----Original Message----- 
> > From: [email protected] [mailto:[email protected]] 
> On 
> > Behalf Of Walter Hart 
> > 
> > That was indeed the issue.  I had modified the ticket workflow to match 
> our 
> > previous status indicators (actually only changing the new to open), and 
> that 
> > made it very unhappy.  Next I will figure out how to resolve the 
> imported 
> > tickets status indicators, as I have imported several thousand tickets 
> and 
> > probably will have several thousand more once the configuration is 
> happy. 
>
> The Trac workflow is fairly flexible but _must_ have a "new" and "closed" 
> state.  You can either re-implement your old workflow states or add in new 
> "get out of jail" state transitions from the old states to sensible new 
> ones.  I find the [[Workflow]] macro quite useful for its visualisation [1] 
> (assuming you have GraphViz installed).
>

Those are some good points.  Regarding the "get out of jail" state, that's 
the reset_workflow action, documented here:
https://trac.edgewall.org/wiki/TracWorkflow#BasicTicketWorkflowCustomization

For future reference, in Trac 1.2 the requirement to have a new state has 
been eliminated, but you must still have a closed state:
https://trac.edgewall.org/wiki/1.1/TracWorkflow?version=7

Finally, while graphviz is needed for rendering workflows with the old 
workflow_parser.py script, it's not needed for rendering workflows with the 
Workflow macro. The former precedes the workflow macro and is obsoleted by 
the workflow macro for most use-cases.
https://trac.edgewall.org/wiki/TracWorkflow#WorkflowVisualization
 

> [1] https://trac.edgewall.org/wiki/TracWorkflow#WorkflowVisualization 
>
> Also do not forget you can inherit the workflow via shared configuration 
> file(s) [2]. 
>
> [2] https://trac.edgewall.org/wiki/TracIni#GlobalConfiguration 
>
> I hope that helps, 
>
> ~ Mark C 
>
> > Thanks for your help 
> > 
> > 
> > On Fri, Jul 8, 2016 at 2:11 PM, RjOllos <[email protected]> wrote: 
> > 
> > 
> > 
> > 
> >         On Friday, July 8, 2016 at 11:48:02 AM UTC-7, whartlists wrote: 
> > 
> >                 Ryan, 
> > 
> >                 Thanks.  I was logged in as admin while testing, so my 
> guess is 
> > it may not be a permissions issue, but I'll create a test user and try 
> that. 
> > 
> > 
> >         After verifying permissions, I would compare the 
> [ticket-worflow] 
> > sections in trac.ini for the two environments. 
> > 
> >         - Ryan 
>
>

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to