# How should participants manage third-party plugin reports on Meta

**URL:** https://meta.discourse.org/t/how-should-participants-manage-third-party-plugin-reports-on-meta/362946
**Category:** Site feedback
**Created:** [April 22, 2025, 10:25am UTC](https://meta.discourse.org/t/how-should-participants-manage-third-party-plugin-reports-on-meta/362946 "2025-04-22T10:25:10Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [April 23, 2025, 10:59pm UTC](https://meta.discourse.org/t/how-should-participants-manage-third-party-plugin-reports-on-meta/362946/3 "2025-04-23T22:59:16Z")

</div>

I think in this case it was right to post it to #Contribute > Bug because the cause was not known at first. Then it should have been merged into the theme component topic. Until then I think it could have stayed in #Contribute > Bug, perhaps with a tag indicating that a component was the culprit?

I’m not fond of the #General category which has become a catchall for all manner of topics. I can see a world where people post to #General because they don’t know where it belongs but moderators move those posts to the appropriate place if it exists already or perhaps create a new category if enough similar topics are landing in #General.

Sam, feel free to use the flag too if you are feeling lazy in cases like these. Then moderators can take care of it.

---

_[View the full topic](https://meta.discourse.org/t/how-should-participants-manage-third-party-plugin-reports-on-meta/362946)._