How could I deny operations on closed tickets

[adriano.vieira@…]

I want to deny operations on closed tickets. I mean if a ticket is closed then this ticket couldn't be modified (reopened or anyting else).

How could I do this?

Thx a lot in advance.

Adriano Vieira

[Christian Boos]

Customize the WorkFlow. Should be as simple as removing the available operations available on the closed state (i.e. reopen), in the [ticket-status] section.

Note however that the old WorkFlow branch is based on a 0.10dev Trac version, and that the new WorkFlow was recently rebased on 0.11dev (and doesn't have much features right now… work in progress).

So for pure 0.10 installations, WorkFlow is not really usable. Hopefully 0.11 won't take that long ;)

[Christian Boos]

This issue should probably be examined in the light of the recent/future changes concerning workflow and security.

[Eli Carter]

WorkFlow now allows you to customize the state transitions, so you can make 'closed' be a dead end, or only allow TICKET_ADMIN to re-open, or whatever.

Preventing modification of all fields, however, is more than WorkFlow will do for you.

[osimons <simon-code@…>]

See TracWorkflow for workflow docs. As ecarter says, it should be quite easy to prevent reopening closed tickets with 0.11 (or require a higher permission).

The other alternative for 0.11 that also solves this for fields and all changes, is making simple, custom security policy (TracDev/SecurityBranch). On permission check to see if the user has permission to modify or append this resource (ticket), if ticket is closed then only allow if the user has TICKET_ADMIN (or some other variation along these lines). See trunk/sample-plugins for examples.

Closing as 'fixed' in recognition of the major efforts that went into 0.11 to make the requested enhancement possible.