This is a great plugin to help with organizing the data rather than it just being lines of code in the trac.ini file. Thanks a lot for this Ryan! I wasn't able to get the diagram to display but it's ok. I was able to make my own based off of this chart. Also I realize now I was trying to be extremely linear with this project when in actuality everything is just a giant web. Thanks again for the help!
-Richard On Wednesday, November 2, 2016 at 3:26:03 PM UTC-5, RjOllos wrote: > > > > On Wednesday, November 2, 2016 at 1:22:45 PM UTC-7, RjOllos wrote: >> >> >> >> On Tuesday, November 1, 2016 at 9:43:17 AM UTC-7, Richard Smith wrote: >>> >>> Hello all, >>> >>> I am trying to setup a new workflow within TRAC but I am having some >>> trouble just with the logic. I attached an image with the process that we >>> are looking to implement. >>> In the current trac.ini for my TestRepo I have the default flow. >>> >>> >>>> proposed=pending,need info,valid,invalid,testing -> active, closed >>>> accept=new,assigned,accepted,reopened,testing -> accepted >>>> accept.operations=set_owner_to_self >>>> accept.permissions=TICKET_MODIFY >>>> leave=* -> * >>>> leave.default=1 >>>> leave.operations=leave_status >>>> reassign=new,assigned,accepted,reopened,testing -> assigned >>>> reassign.operations=set_owner >>>> reassign.permissions=TICKET_MODIFY >>>> reopen=closed -> reopened >>>> reopen.operations=del_resolution >>>> reopen.permissions=TICKET_CREATE >>>> resolve=new,assigned,accepted,reopened -> closed >>>> resolve.operations=set_resolution >>>> resolve.permissions=TICKET_MODIFY >>>> >>> >>> >>> From what I have found online relating to Ticket Workflow was this. I >>> tried implementing it but the ticket would always display as the default >>> ticket. Do I have to change anything else outside of the Ticket workflow >>> when trying to change the workflow? I am very green in regards to TRAC so I >>> apologize for not knowing to much about this software. If there is anything >>> else that I may have left out don't hesitate to let me know. Thank you so >>> much! >>> >>> >>> Source: >>> http://www.gorges.us/blog/customizing-the-trac-ticket-workflow >>> >>> [ticket-workflow] >>>> leave = * -> *leave.name = No status change - leave >>>> leave.operations = leave_status >>>> leave.default = 0 >>>> >>>> assign = new -> assigned >>>> assign.permissions = TICKET_MODIFY >>>> assign.operations = set_ownerassign.name = Assign >>>> assign.default = -1 >>>> >>>> implement = assigned,rejected -> implemented >>>> implement.permissions = TICKET_MODIFYimplement.name = Implemented >>>> implement.default = -2 >>>> >>>> deploy = assigned,implemented,rejected -> reviewing >>>> deploy.permissions = TICKET_MODIFYdeploy.name = Deployed for review >>>> deploy.default = -3 >>>> >>>> accept = reviewing -> closed >>>> accept.permissions = TICKET_MODIFY >>>> accept.operations = set_resolution >>>> accept.set_resolution = fixedaccept.name = Accept >>>> accept.default = -4 >>>> >>>> reject = reviewing -> rejected >>>> reject.permissions = TICKET_MODIFYreject.name = Rejected (needs more work) >>>> reject.default = -5 >>>> >>>> close = new,assigned,implemented,reviewing,rejected -> closed >>>> close.permissions = TICKET_MODIFY >>>> close.operations = set_resolutionclose.name = Close >>>> close.default = -6 >>>> >>>> reassign = assigned,implemented,reviewing,rejected -> assigned >>>> reassign.permissions = TICKET_MODIFY >>>> reassign.operations = set_ownerreassign.name = Re-assign >>>> reassign.default = -7 >>>> >>>> reopen = closed -> assigned >>>> reopen.permissions = TICKET_CREATE >>>> reopen.operations = set_ownerreopen.name = Re-open and Assign >>>> reopen.default = -8 >>>> >>>> >>> >> >> >> You have states such as "testing" for which there is no action to >> transition into the state. You can use the [[Workflow]] macro (1) to >> visualize your workflow. >> >> >> >> <https://lh3.googleusercontent.com/-gkm0zFmRewA/WBpKdMmwEZI/AAAAAAAAD1Q/f3YBKj1orXEDWjC40-95lMsXQFI-i4oqgCLcB/s1600/Screen%2BShot%2B2016-11-02%2Bat%2B13.19.49.png> >> >> It also looks like you might be mixing up the concepts of a workflow >> state, and a resolution (2). "invalid" and "valid" sound more like >> resolutions for the "closed" state, rather than workflow states. >> >> - Ryan >> >> (1) https://trac.edgewall.org/wiki/WikiMacros#Workflow-macro >> (2) https://trac.edgewall.org/wiki/TracTickets#TicketFields >> >> > > Also, note that you can expirement with the workflow using the Workflow > macro/wikiprocessor in a wik page: > > {{{#!workflow > proposed=pending,need info,valid,invalid,testing -> active, closed > accept=new,assigned,accepted,reopened,testing -> accepted > accept.operations=set_owner_to_self > accept.permissions=TICKET_MODIFY > leave=* -> * > leave.default=1 > leave.operations=leave_status > reassign=new,assigned,accepted,reopened,testing -> assigned > reassign.operations=set_owner > reassign.permissions=TICKET_MODIFY > reopen=closed -> reopened > reopen.operations=del_resolution > reopen.permissions=TICKET_CREATE > resolve=new,assigned,accepted,reopened -> closed > resolve.operations=set_resolution > resolve.permissions=TICKET_MODIFY > }}} > > You may also be interested in this plugin: > https://trac-hacks.org/wiki/TracWorkflowAdminPlugin > > - 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.
