Hello, guest. We have noticed that you are not registered at this bug tracker. Your experience will be greatly enhanced if you log in. To do so, you first must register by clicking on the Register tab at the top. If you are already registered, you can login at the Login tab.
Syndicate Syndicate Listing Display Search Login/Register
Bug Id ?
Reporter ?
Andreas N.
Product/Version ?
Bugdar / 1.0.1
Status ?
Closed
Severity ?
Enhancement
Duplicate Of ?
- none -
Fixed in Revision ?
932
Mstone ?
Summary ?
Wanted Feature: Remove items
Report Time ?
April 18, 2006 10:12 AM
Assignment ?
- none -
Resolution ?
Fixed
Priority ?
Normal
Dependencies ?
- none -
Mstone (old) ?


Votes
For: 0 (0%)
Against: 0 (0%)
Total: 0

April 18, 2006 10:12 AM Andreas N.
I'd like to be able to remove items from the list as Administrator. Sometimes ppls submit duplicates and crap and its a pain to remove it by using a mysql client ;)

April 18, 2006 02:40 PM Robert
I was debating in 1.0 to have the option to delete bugs and comments. I can see where it could be useful for some things, but generally, all reports (in my opinion) should stay active. If people submit duplicates, simply close it and mark it as a "Duplicate" in the resolution field (you can even put in the duplicate ID in the proper field). I will, however, look at adding this (it was in an early SVN version) simply to remove spam, etc.

April 20, 2006 07:52 AM Willem van Duijn
I agree to Robert: if you remove a report people can't check/follow the status. It's better to mark it as duplicate, and point to the primary bug report. But it would be nice if the duplicates are not shown in the buglist, or somewhere at the bottom. You can then use the future notification-system (e-mail) to notify the user of this action (so it knows the primary bug report).

But you are right for SPAM, it should be possible to delete spam.

April 20, 2006 03:38 PM Robert
In 1.1, you'll be able to filter out certain statuses so you can hide all the duplicate bugs, if you want.

July 22, 2006 05:26 AM Robert
Thank you for your bug report. This issue has been closed and fixed in Subversion. This change will be available in a future release, but you can download the change at any time from the Subversion server.