TICKET_EDIT_CC apply to new ticket

[knavero@…]

Can TICKET_EDIT_CC apply to creation of a new ticket also? In other words, it would be nice to limit the control of how a user submitting a ticket can send a lot of emails

[Jun Omae]

Sounds good. I've considered the same when a spammer cloned old tickets which have many entries in the cc field.

[Peter Suter]

Since Trac 1.3.3 (#12947) you can presumably do this by disabling the DefaultTicketPolicy component. When that component is enabled four rules are enabled:

• Users with MILESTONE_VIEW can edit the ticket milestone field.
• Authenticated users with TICKET_APPEND or TICKET_CHGPROP can edit the description of a ticket they reported.
• Authenticated users with TICKET_APPEND can edit their own ticket comments.
• The CC field can be edited when creating a ticket even if the user doesn't have TICKET_EDIT_CC.

Disabling the component will disable all four rules. To disable only the last rule, I guess you can replace the component in a single-file-plugin (untested):

from trac.core import *
from trac.ticket.web_ui import DefaultTicketPolicy

class DefaultTicketPolicyWithoutNewTicketEditCc(DefaultTicketPolicy):

    def check_permission(self, action, username, resource, perm):
        # Skip DefaultTicketPolicy rule for TICKET_EDIT_CC
        if action == 'TICKET_EDIT_CC':
            return
        super(DefaultTicketPolicyWithoutNewTicketEditCc, self) \
            .check_permission(action, username, resource, perm)

This could be added to wiki:CookBook/PermissionPolicies.

(But I don't mind if this is changed in Trac itself anyway. Then a cookbook recipe could show how to get the old behavior.)

[Ryan J Ollos]

Proposed changes in [78a9731d7/rjollos.git].

[Jun Omae]

The changes look good to me.

[Ryan J Ollos]

Thanks for review. Committed to trunk in r17063.