Edgewall Software

Ticket #5878 (closed enhancement: duplicate)

Opened 17 months ago

Last modified 17 months ago

Ticket-Permissions

Reported by: buchtala@… Owned by: jonas
Priority: normal Milestone:
Component: ticket system Version: devel
Severity: normal Keywords:
Cc:

Description

On the way to finer grained permission and multiple projects(single env) it may be helpful to transfer the policy concept to ticket queries as well. Then, one can implement some kind of ticket policy which checks whether a user should see the ticket (e.g., using an authzfile)

Attachments

TicketPermissionPatch.patch (16.0 KB) - added by buchtala@… 17 months ago.

Change History

Changed 17 months ago by buchtala@…

Changed 17 months ago by buchtala@…

I attached a patch which I implemented for my local trac.

  • (Unfortunately) I had to make some changes to the ticket api.
  • Tried to give TicketSystem more control over ticket access (I think the direct access to the ticket db in other places is bad).
  • Introduced an ITicketPermissionPolicy and implemented a dummy standard Policy

Bye, Oli

Changed 17 months ago by cboos

  • status changed from new to closed
  • resolution set to duplicate
  • milestone 0.12 deleted

See #1316. The changes actually required are much less invasive than what you propose in your patch. See how it's done in the Wiki module for example. The sample authz policy plugin should also work unmodified for tickets, once the ticket module changes are in place.

Add/Change #5878 (Ticket-Permissions)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
to The owner will change from jonas. Next status will be 'closed'
 
Note: See TracTickets for help on using tickets.