Edgewall Software
Modify ↓

Opened 17 years ago

Closed 17 years ago

#5878 closed enhancement (duplicate)

Ticket-Permissions

Reported by: buchtala@… Owned by: Jonas Borgström
Priority: normal Milestone:
Component: ticket system Version: devel
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal 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 (1)

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

Download all attachments as: .zip

Change History (3)

by buchtala@…, 17 years ago

Attachment: TicketPermissionPatch.patch​ added

comment:1 by buchtala@…, 17 years ago

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 by Christian Boos, 17 years ago

Milestone: 0.12
Resolution: → duplicate
Status: new → 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.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Jonas Borgström to the specified user.

Add Comment
E-mail address and name can be saved in the Preferences .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.