You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I've tried multiple times to reply to the question of our app user, and it disappears each time. Can you please help me out there?
This is a question about our product, and I really need to provide guidance here
This is the discussion: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/For-OBoard-OKR-can-you-link-sprints-instead-of-issues-epics-to/qaq-p/2532406#U2539396
Hi @Margo Sakova,
The Community's spam filter is sometimes a bit strict, especially when it detects content being posted multiple times. The bots sometimes take over.
I recovered your last attempt from the quarantine for you, as it did seem a quite legit post.
Hope this helps!
That's what it said in the quarantine as well. While I can see that it was auto-flagged, I don't have access to the backend, so can't confidently tell you why.
Maybe you had a delay when you tried to post the first time and posted again. I know from previous conversations that the bots are pretty strict when they detect the same content being posted multiple times.
Let's assume it was a glitch this time of an overcommitting virtual agent in the background. Should it happen again, I'd be happy to ping the Community team to investigate a bit deeper. For now, let's say/hope the problem's solved!
Thanks for that information.
I find the bot / blocking behavior puzzling: I often see marketplace vendors (or virtual agents?) using boilerplate answers in rapid succession (even to very old posts), apparently not being blocked, and yet when I use a template paragraph to ask a poster for more information on a question too often, it hits the "you already posted this...please wait" message.
Seems like an opportunity for more transparency in this aspect of the community management behavior.