Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Spam attack on issue tracker


Hi. I have the same problem on  and could not find a way to do bulk marking or erasing.

I tried to mark 2 of them as spam, but there's more than 200 and bitbucket is slow as hell, so this requires something like 30s here to do that, and the spam is still around, so this have little to no effect.

The spam IDs start from #59 to #281 and I just found out how to disable anonymous people rights to spam me. I do not understand why this "feature" was enabled, though, it's a very terrible default setting, and I'm pretty sure I would not have kept it enabled, so this must be a new "feature" of bitbucket.

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 22, 2023

Hi @bmorel,

Thank you for reaching out.

Just a heads up, I moved your post to a new question for easier tracking.

Before we proceed, please make your issue tracker private to prevent the creation of new spam issues. Let me know once you do that, and I will then ask the development team to mark as spam the issues with id-s #59 to #281 (let me know if the range has changed.)

I will post an update here once this problem is mitigated and when it's safe to make your issue tracker public again.

Kind regards,



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events