Exact position of link Delete Ticket and Delete Changes.

[lborz@…]

Hi,

I'm an user of Trac. My Trac version is 0.12.5dev-r11463. Plugin installed are:

• BlackMagicTicketTweaks 0.11r1
• privatereports 0.3
• TicketReminderPlugin 0.1.1
• TracAccountManager 0.3.2
• TracTicketChainedFields 0.1

I enabled the component adding in the trac.ini file at the end of section [components] the line: tracopt.ticket.deleter = enabled
To be sure that the modification is active, I gave the command: /etc/init.d/apache2 restart
Maybe I didn't understand very well where the links Delete Ticket and Delete Changes will appear. After reading your help page of plugin, I suppose that when I open the Admin page, that links will appear in the Administration left menu. That's doesn't happen. I'm looking in the wrong place or what?

Thank you in advance for your reply, Luca.

[Ryan J Ollos]

Hi, The tracopt.ticket.deleter is part of the Trac core and different from this plugin. The plugin here is obsolete for Trac >= 0.12.

The documentation for tracopt.ticket.deleter can be found on the WebAdmin panel, IIRC. There might be a TICKET_DELETE permission you need to grant. You might also want to try as a user with TICKET_ADMIN. I can't recall the details.

[lborz@…]

I use the default admin user of Trac, that has the permission TICKET_ADMIN. From Trac help I see that the permission TICKET_DELETE is not available.
What I got when I open the Admin section of Trac is this menu:

Administration

• General
• Basic settings
• Logging
• Permissions
• Plugins

Accounts

• Configuration
• Users

PrivateReports

• PrivateReports

Ticket System

• Chained Fields

Ticket system

• Components
• Milestones
• Priorities
• Resolutions
• Severities
• Ticket types
• Versions

Version control

• Repositories

I suppose that the link "Ticket delete" will be available in this menu, but there isn't. To be sure, is this menù that you mean when you wrote "WebAdmin panel, IIRC"?

Cheers, Luca.

[Ryan J Ollos]

I'm happy to help you work to resolve the issue, but it is not an issue with the plugin, so let's keep the ticket closed. I'll do some investigation and report back shortly.