Add a possibility to remove a ticket

[actarus]

There is no possibility other than going through the db to remove a ticket. Having a web interface to do this would be useful.

[jon@…]

Should tickets *be* removable?

The best policy in most enviroments is to have invalid tickets closed as such, rather than deleted, which will allow you to get information on things that get reported regularly.

[daniel]

No, tickets shouldn't be easily removable.

Possibly, trac-admin could have a command to do it, but that too seems not worth it.

It's easy to use SQL if you absolutely must delete a ticket, otherwise just close the ticket as invalid.

[public@…]

I have a ticket in my Trac that I need to delete. For some reason, any time it's clicked on, tracd crashes. So, in that case, yes deleting a ticket is necessary.

[Christian Boos]

It could be interesting to report the error you got, maybe that can be fixed…

[anonymous]

Why don't You let this thing (delete ticket's) to trac-admin. I hope it's easy to implement, and gives further functionality. For example: someone add stupid ticket specially - What shold I do? Waste time learning SQL tables infrastrukture?

Pleas, think about this. It's very unprofesional to decide for user :) (sorry for my English)

[anonymous]

I agree there should be some straightforward administrative route to utterly deleting or at least censoring a ticket. You have to understand that we must deal with people, often superiors, who may obsess over sometimes (but not always) trivial details.

For example: Suppose somebody puts a racist comment in a ticket. Merely marking it "invalid" isn't going to appease HR. They'll want it expunged completely.

Hacking the DB is not straightforward and not documented. There should be an option in trac-admin. If you like, it could leave behind a marker that indicates the ticket was deleted/censored and optionally why.

[Christian Boos]

If you like, it could leave behind a marker that indicates the ticket was deleted/censored and optionally why.

The admin can already alter the description, and remove any offending content if needed, and the motivation for closing the ticket as invalid can be explained in a ticket comment associated with the status change.

The only thing that can't be done right now is deleting/modifying the ticket comments (see #454), but once this feature is available, I don't think it's worth to introduce a special case.

[anonymous]

cboos wrote:

closing the ticket as invalid can be explained in a ticket comment associated with the status change.

You must be joking :)

I'm using Trac for few days, and I understand difference between closing and deleting ticket. I strongly recommend closing ticket, but still in some cases I just HAVE to delet some ticket.

For example: We are testing TRAC and add some stupid tests ticket :) Now I have to reinstall TRAC to delete them. There are meny more examples.

As someone seys. I'm a big boy and have TRAC_ADMIN. Let me do What I want.

I don't believe that it is hard to add this feature :)

[anonymous]

Agree with adding delete ticket to trac-admin. I just started using trac for a project, and entered an item for another project from a different account. It entered for the same project. After the fact, I now know from reading FAQ that special setup is required to manage more than one project, but I need to delete the ticked since it contains sensitive information inappropriate for the first project. Otherwise, I'm recreating from scratch or learning SQL. Having the delete ticket and reset ticket number (back to one previous) right now would be very convenient as I noticed the problem immediately. I need to eliminate any record of this ticket entry for this project.

I suspect little issues crop up like this all the time when people are trying to get work done, and admins need to fix them.

2c. Thanks for great tracking system.

[criss@…]

I agree with people that sometimes you just need to delete a ticket.

I'm using a 0.8 version of Trac, recently set-up, and sent test emails into the system when setting up email ticket reporting. I had customized a lot, and did not realize why new ticket were not showing up when I thought the email side was working properly.

Turned out that the report lists I was looking at to check whether the emails were accepted into the system depended on a valid "priority" name to list the tickets. I have duplicated test email tickets in the system, closed as invalid. Now they show up in reports. Just not looking too good there. Nice to have proof that I did my job, but very sloppy.

You don't want users frivolously deleting tickets, but if spam makes it to the system, the ticket database may get pretty messy.

[anonymous]

Can you tell me how to remove ticket?

[Christian Boos]

Add a ticket remove <number> command to trac-admin.

[Christian Boos]

There's a patch on r2410 for this feature.

[Manuzhai]

I don't see this in r2410??

[Matthew Good]

Manuzhai: I think that cboos meant that the patch was written when the trunk was at r2410. The file is attached to this ticket.

[anonymous]

works like a charm! thanks cboos! someone basically filed a ticket under the wrong trac (we have three deployed here)

[anonymous]

sorry, that last anonymous (And this one :P) is seemant from #trac

[robin-trac@…]

Did this not make it into 0.9.2?

Ah, I see the milestone has been move out again to 0.9.3.

[Christian Boos]

Implemented in r2634.

[anonymous]

The patch didn't work in the Latest Stable Release - 0.9.4

[Christian Boos]

Well, that patch is now in trunk and the feature will be available for 0.10.

Anyway, the feature itself was an enhancement request, so I'm reverting the type change.

Notice that there's also a plugin ​TracHacks:TicketDeletePlugin you might find interesting if you want to stick with 0.9.

[bjorn at linpro dot no]

For cleaning up after spammer attacks, it should also be possible to revert a change to a ticket.

[anonymous]

Replying to bjorn at linpro dot no:

For cleaning up after spammer attacks, it should also be possible to revert a change to a ticket.

I always just deleted revisions to vandalized wiki pages. Today was my first onslaught of defect reports that I need to buy medicine or something, and I can't delete them. :(

[jyoshimi@…]

Replying to anonymous:

Replying to bjorn at linpro dot no:

For cleaning up after spammer attacks, it should also be possible to revert a change to a ticket.

I always just deleted revisions to vandalized wiki pages. Today was my first onslaught of defect reports that I need to buy medicine or something, and I can't delete them. :(

I get about one spam attack per week. Isn't there a way to require a password to create new tickets? But maybe that should be a new ticket….

[Martijn Pieters <mj@…>]

Replying to jyoshimi@ucmerced.edu:

I get about one spam attack per week. Isn't there a way to require a password to create new tickets? But maybe that should be a new ticket….

Yes, just remove the TICKET_CREATE permission from 'anonymous', and assign it to 'authenticated' instead. See TracPermissions for more info.

[evan.s@…]

Replying to Martijn Pieters <mj@zopatista.com>:

Replying to jyoshimi@ucmerced.edu:

I get about one spam attack per week. Isn't there a way to require a password to create new tickets? But maybe that should be a new ticket….

Yes, just remove the TICKET_CREATE permission from 'anonymous', and assign it to 'authenticated' instead. See TracPermissions for more info.

In 0.10svn, anyways, authenticated users can change the reporter field, though, so far as I can tell.

[marius@…]

In case someone else needs to delete a ticket in a trac 0.9 instance without installing extra plugins, here's the SQL:

$ sqlite trac.db
delete from ticket_change where ticket = 1234;
delete from ticket_custom where ticket = 1234;
delete from ticket where id = 1234;