Edgewall Software
Modify

Ticket #5878 (closed enhancement: duplicate)

Opened 5 years ago

Last modified 5 years ago

Ticket-Permissions

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

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@… 5 years ago.

Download all attachments as: .zip

Change History

Changed 5 years ago by buchtala@…

comment:1 Changed 5 years 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

comment:2 Changed 5 years ago by cboos

  • Milestone 0.12 deleted
  • Resolution set to duplicate
  • Status changed from new to closed

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.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
to The owner will be changed from jonas. Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.