Spam on issue tracker
Asked by ecoRoland:

Same problem here: <https://bitbucket.org/ecoRoland/gasfluxes/issues>

I don't have time to take care of this. So here is hoping that Atlassian will resolve this on their end or at least provide a tool, which allows mass deletion without having to go through each issue.


Answers:
author: Suhas Sundararaju
body: Hi [@ecoRoland](/t5/user/viewprofilepage/user-id/2893278) ,   

We have deleted the spam issues from issue ID 16 to 182. We hope this helps. Apologies for any inconvenience this may have caused you.

Regards,

Suhas

comments: author: ecoRoland
body: [@Suhas Sundararaju](/t5/user/viewprofilepage/user-id/4427897), thank you!


author: Bryce Kinseth
body: More spam here: [https://bitbucket.org/atlassian/update-all-the-things/issues?status=new\&status=open](https://bitbucket.org/atlassian/update-all-the-things/issues?status=new&status=open)

comments: author: ecoRoland
body: You should probably open a new question to improve visibility and reaction time. I'm sure there is tons of issue spam that won't even be reported because repo maintainers aren't active anymore. Atlassian needs to tackle this from their end. The spam should be rather easily identified.


author: jestar_jokin
body: I had a simlar problem, where someone added 191 spam issues to a repository.

I wrote a NodeJS CLI tool to delete them all. It will delete all issues where:

* Reporter is null
* Assignee is null
* Status is new

This was enough for me. You might need to adjust the criteria.

<https://bitbucket.org/jestar_jokin/bitbucket-cleanup/>


author: Patrik S
body: Hi [@ecoRoland](/t5/user/viewprofilepage/user-id/2893278) ,

Thanks for reaching out to the Community!

I've moved your post to a new question for easier tracking.

Our engineering team can help with either:

* flag issues as Spam
* completely remove issues

**Please keep in mind that there is a possibility for false positives to be included in the flagging or removal.** If you are concerned about irreversible loss, we would suggest requesting flagging, so that you can review the issues.

Before we proceed, ++please make your issue tracker private++ (*Repository Settings \> Issue Tracker \> Private issue tracker*) to prevent the creation of new spam issues. I will post an update here once our engineering team has mitigated the issue and when it's safe to make your issue tracker public again.

Afterward, please let us know whether you would like us to proceed with flagging issues as spam in your issue tracker or removing them :

* **Removal**: If you would like us to proceed with the removal, please provide a range of issue IDs to remove. You could also include issues that you want to be excepted from this range. E.g. for the range "200-3700 EXCEPT 3256-3260" we will remove issues with id from 200 until 3700, except for the issues in the range 3256-3260. Ranges should be fully inclusive, meaning the number on both ends will be removed.
* **Flagging as Spam:**If you would prefer to mark the issues as Spam, so you can review them later, please provide an Issue ID as a starting point. All the issues after the starting point ID will be marked as Spam.

Let me know in case you have any questions.

Thank you, [@ecoRoland](/t5/user/viewprofilepage/user-id/2893278) !

Patrik S

comments: author: ecoRoland
body: Disabling issue submission by anonymous users was sufficient to stop the spam. I won't make the issue tracker private because it is given as the official support channel for my R package on CRAN. That is the main reason why I maintain the repository on bitbucket. In fact, I would like you to implement measures against spamming, so that I can allow issue submission by anonymuous users again.

Please remove all issues with **number \>=16**.


author: Ruslan Osmanov
body: I have over 30 spam issues created by both anonymous and registered users: <https://bitbucket.org/osmanov/pecl-eio/issues>

Disabling anonymous issues didn't help. How we are supposed to deal with this?

Are there any plans to solve this problem? One of the simplest ways would be adding a re-CAPTCHA. I think it should not be a problem for Atlassian.