> Date: Fri, 27 May 2011 12:41:43 +0200 > Subject: Re: [Trac] closed tickets are not stricked > From: [email protected] > To: [email protected] > > On Fri, May 27, 2011 at 11:41 AM, Pascal Graf > <[email protected]> wrote: > > > here is my workflow: > > [ticket-workflow] > newtosubmitted = new -> Submitted > open = Submitted -> Open > open.operations = set_owner_to_self > open.permissions = TICKET_CREATE > leave = * -> * > leave.default = 1 > leave.operations = leave_status, set_owner > toreview = Open -> In_Review > toreview.permissions = TICKET_MODIFY > toreview.operations = set_owner > resolve = In_Review -> Resolved > resolve.operations = set_resolution, set_owner > resolve.permissions = TICKET_MODIFY > integrate = Resolved -> Integrated > integrate.permissions = TICKET_MODIFY > integrate.operations = set_owner > dev_close = Integrated -> Dev_Closed > dev_close.permissions = TICKET_MODIFY > dev_close.operations = set_owner > close = Dev_Closed, Rejected, Integrated, Open -> Closed > close.permissions = TICKET_MODIFY > close.operations = set_resolution, set_owner > reject = Submitted, Open -> Rejected > reject.permissions = TICKET_MODIFY > re_open = In_Review, Resolved, Integrated, Rejected, > Closed -> Open > re_open.permissions = TICKET_CREATE > re_open.operations = del_resolution, set_owner > > > in the state "close" tickets should be stricked. > there i have the set_resolution operation. > > i think the mistake has to be in the workflow, cause > it's the only thing different. > > > > What about case sensitivity? closed != Closed? > > Cheers / Erik > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Pascal Graf > Sent: 27 May 2011 12:12 > To: Trac Mailinglist > Subject: RE: [Trac] closed tickets are not stricked > > that should not be a problem cause there are two different things. > close is the transaction from one state to the other and > Close is a state. > haven't ever had problems with that. > > best, > pascal
...well spotted Erik, I think I agree. Pascal, if you read http://trac.edgewall.org/wiki/TracWorkflow#BasicTicketWorkflowCustomizat ion ...near the end of that section is the following: {{{ There are a couple of hard-coded constraints to the workflow. In particular, tickets are created with status "new", and tickets are expected to have a "closed" state. Further, the default reports/queries treat any state other than closed as an open state. }}} ...so you just need to rename your `Closed` state to `closed` (and possibly update your backend dB tables, check out http://trac.edgewall.org/wiki/TracDev/DatabaseSchema) to UPDATE the status value. Then Trac will recognise your tickets as closed and should show them crossed out. ~ Mark C > > > Subject: RE: [Trac] closed tickets are not stricked > > Date: Fri, 27 May 2011 10:18:26 +0100 > > From: [email protected] > > To: [email protected] > > > > > > -----Original Message----- > > > From: [email protected] On Behalf Of Pascal Graf > > > Sent: 27 May 2011 08:37 > > > To: Trac Mailinglist > > > Subject: [Trac] closed tickets are not stricked > > > > > > hi all > > > > > > i have two trac projects and in one of them closed tickets > > > are not stricked. > > > in this one i customized the workflow, maybe cause of that. > > > > > > i found the following resolution but it don't work > > > http://trac.edgewall.org/ticket/991 > > > > > > has someone any other ideas? > > > > > > thanks for your help > > > > > > best, > > > pascal > > > > Make sure that your customised 'close' state > transitions include: > > <transition>.operations = set_resolution > > > > Can you post your customised workflow? > > > > ~ mark c > > > > -- > > 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] > <mailto:trac-users%[email protected]> . > > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. > > > > > -- > 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] > <mailto:trac-users%[email protected]> . > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. > > > > > -- > 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. > > > -- > 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. > > -- 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.
