Project

General

Profile

Actions

Task #2350

open

Clean deletionrequest component

Added by Xisco Fauli Tarazona almost 5 years ago. Updated 4 months ago.

Status:
In Progress
Priority:
Normal
Target version:
Team - Recurring
Start date:
Due date:
% Done:

0%


Description

Steps:
1. Enable allowbugdeletion in Administration -> Parameters -> Administrative Policies.
2. Once you have added all the soon to be deleted bugs to your trash component go back to the component list in the administration page (Administration -> Products -> LibreOffice -> Edit Components). You should see an “Action” column on the far right of the table with all your components with a Delete link. Find the deletionrequest component and click the associated “Delete” link.
3. Confirm the deletion.
4. Disable allowbugdeletion in Administration -> Parameters -> Administrative Policies

More Information: https://devzing.com/blog/index.php/how-to-delete-bugs-from-bugzilla/

Actions #1

Updated by Xisco Fauli Tarazona almost 5 years ago

  • Description updated (diff)
Actions #2

Updated by Xisco Fauli Tarazona almost 5 years ago

Cleaned today

Actions #3

Updated by Florian Effenberger over 4 years ago

How often should this take place?

Actions #4

Updated by Xisco Fauli Tarazona over 4 years ago

Normally I do it every month but I don't update the ticket, should i do it every time I perform the task?

Actions #5

Updated by Florian Effenberger over 4 years ago

No, no need to for the moment - just was curious :)

Actions #6

Updated by Xisco Fauli Tarazona about 4 years ago

Cleaned today!

Actions #7

Updated by Florian Effenberger over 3 years ago

  • Status changed from New to In Progress
Actions #8

Updated by Florian Effenberger about 3 years ago

Xisco Fauli Tarazona wrote:

Cleaned today!

Is that still done regularly? :)

Actions #9

Updated by Xisco Fauli Tarazona about 3 years ago

Florian Effenberger wrote:

Xisco Fauli Tarazona wrote:

Cleaned today!

Is that still done regularly? :)

Yes, it's enough to do it once or twice a year. I've just done it. 70 bugs deleted Thanks for the reminder.

Actions #10

Updated by Xisco Fauli Tarazona over 1 year ago

updated

Actions #11

Updated by Xisco Fauli Tarazona 11 months ago

updated

Actions #12

Updated by Adolfo Jayme Barrientos 11 months ago

Is it possible to also delete all comments with the “spam” tag?

Actions #13

Updated by Xisco Fauli Tarazona 11 months ago

Adolfo Jayme Barrientos wrote in #note-12:

Is it possible to also delete all comments with the “spam” tag?

Do you mean comments tagged with 'spam' ? No, it's not possible, Bugzilla doesn't allow to remove comment as far as I know

Actions #14

Updated by Adolfo Jayme Barrientos 11 months ago

Oh, that’s a bummer. Then, how feasible it would be to restrict comments on old bugs (say, 1 month after they’re closed), for people not in “contributors”? This is to avoid getting spam comments.

Actions #15

Updated by Adolfo Jayme Barrientos 5 months ago

Got no response to the above proposal, and the spam still gets in my inbox in e.g. https://bugs.documentfoundation.org/show_bug.cgi?id=97341
Do I really have to un-CC myself from the whole site?

Actions #16

Updated by Xisco Fauli Tarazona 5 months ago

Adolfo Jayme Barrientos wrote in #note-14:

Oh, that’s a bummer. Then, how feasible it would be to restrict comments on old bugs (say, 1 month after they’re closed), for people not in “contributors”? This is to avoid getting spam comments.

I guess we could automatically close the issues after X days the same way we already automate some actions in Bugzilla. Once the bugs are closed, comments with links are blocked

Actions #17

Updated by Adolfo Jayme Barrientos 5 months ago

That’s not enough; the URL fields etc. also need to be locked down. Hence, my proposal to restrict to non-contributors

Actions #18

Updated by Xisco Fauli Tarazona 5 months ago

I think when an issue is closed we can change the fields to read-only to non-contributors users. I'll explore that idea

Actions #19

Updated by Xisco Fauli Tarazona 5 months ago

Xisco Fauli Tarazona wrote in #note-18:

I think when an issue is closed we can change the fields to read-only to non-contributors users. I'll explore that idea

The situation should be improved after https://gerrit.libreoffice.org/c/infra/bugzilla/+/132269

Actions #20

Updated by Xisco Fauli Tarazona 4 months ago

Xisco Fauli Tarazona wrote in #note-19:

Xisco Fauli Tarazona wrote in #note-18:

I think when an issue is closed we can change the fields to read-only to non-contributors users. I'll explore that idea

The situation should be improved after https://gerrit.libreoffice.org/c/infra/bugzilla/+/132269

Xisco Fauli Tarazona wrote in #note-19:

Xisco Fauli Tarazona wrote in #note-18:

I think when an issue is closed we can change the fields to read-only to non-contributors users. I'll explore that idea

The situation should be improved after https://gerrit.libreoffice.org/c/infra/bugzilla/+/132269

Xisco Fauli Tarazona wrote in #note-19:

Xisco Fauli Tarazona wrote in #note-18:

I think when an issue is closed we can change the fields to read-only to non-contributors users. I'll explore that idea

The situation should be improved after https://gerrit.libreoffice.org/c/infra/bugzilla/+/132269

I had to submit a second patch < https://gerrit.libreoffice.org/c/infra/bugzilla/+/133505 > since the first one broke the antispam extension. With the new patch in place, all fields are read-only in closed bugs for non-contributors users except the status field

Actions

Also available in: Atom PDF