Christian Boos wrote: > On 10/7/2012 8:06 PM, Christian Boos wrote: >> Therefore I suggest the following, adapted from basic-workflow.ini: >> >> [ticket-workflow] >> leave = * -> * >> leave.operations = leave_status >> leave.default = 1 >> >> assign = new,assigned,reopened -> assigned >> assign.permissions = TICKET_MODIFY >> assign.operations = set_owner_to_self >> >> resolve = new,assigned,reopened -> closed >> resolve.permissions = TICKET_MODIFY >> resolve.operations = set_resolution >> >> reopen = closed -> reopened >> reopen.permissions = TICKET_CREATE >> reopen.operations = del_resolution >> >> + keeping the change_owner and change_resolution we already have. >> >> The [milestone-groups] would be the one from basic-workflow.ini, >> resulting in "assigned" tickets being shown in yellow. > > This workflow is now in place.
The workflow has the somewhat funny property that it shows the following entry for tickets assigned to me: o assign Next status will be 'assigned'. I know why this is so, the worklow system doesn't check with all operations to see if any of them would actually do something. But maybe someone has an idea how we could fix this. Also, I miss being able to assign tickets to someone else. There's nothing like offloading a big piece of work on somebody else :) -- Remy
signature.asc
Description: OpenPGP digital signature
