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
Change History
Changed 5 years ago by buchtala@…
- Attachment TicketPermissionPatch.patch added
comment:1 Changed 5 years ago by buchtala@…
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.



I attached a patch which I implemented for my local trac.
Bye,
Oli