# איך על המשתתפים לנהל דיווחי תוספים מ сторонних יישומים ב-Meta
**URL:** https://meta.discourse.org/t/how-should-participants-manage-third-party-plugin-reports-on-meta/362946
**Category:** Site feedback
**Created:** [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:** 4
**Page:** 1
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [22 באפריל, 2025, 10:25am UTC](https://meta.discourse.org/t/how-should-participants-manage-third-party-plugin-reports-on-meta/362946/1 "2025-04-22T10:25:10Z")
Continuing the discussion from [Featured Badges breaks user profile page](https://meta.discourse.org/t/featured-badges-breaks-user-profile-page/361981/11):
> [@Featured Badges breaks user profile page](https://meta.discourse.org/t/featured-badges-breaks-user-profile-page/361981/11):
>
> Note: bug tracking for third party themes/components or plugins should all be done in the dedicated plugin/theme/component topic or on a 3rd party bug tracker.
I’m wondering: who is this instruction mainly directed at? Since you posted it in the topic itself, I assume it’s meant for the participants of the discussion. But how is this supposed to be handled in practice?
In many cases, when someone opens a topic due to a problem they’re experiencing, it’s not immediately clear to them whether a third-party plugin, theme, or component is involved. That often only becomes apparent as the discussion progresses. At that point, most of us can’t move posts into the dedicated topic — so your idea of how this should be handled must be different.
Do you expect users to already know the cause of their issue before posting? I agree that starting a topic in #Support instead of #Contribute > Bug could make sense if you’re unsure, but since you didn’t move this one to #Support either, that doesn’t seem to be what you’re suggesting.
I’m trying to understand what we as regular participants should have done differently here.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [22 באפריל, 2025, 10:34am UTC](https://meta.discourse.org/t/how-should-participants-manage-third-party-plugin-reports-on-meta/362946/2 "2025-04-22T10:34:32Z")
> [@Moin](#):
>
> I’m wondering: who is this instruction mainly directed at?
I guess in cases like this I can think of 2 options the community can help with
- recategorize out of bug into general if you have permission
- Flag so mods move it to dedicated topic
In the case linked I concede I was a bit lazy, I should have hunted for the main topic and moved the discussion there
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [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")
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.
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [25 באפריל, 2025, 12:34pm UTC](https://meta.discourse.org/t/how-should-participants-manage-third-party-plugin-reports-on-meta/362946/4 "2025-04-25T12:34:49Z")
> [@tobiaseigen](#):
>
> with a tag indicating that a component was the culprit
This makes me think that a new #3rd-party tag could be created and used, similar to how we use #unsupported-install. For example, in the case of [Dashboard New Posts statistics broken](https://meta.discourse.org/t/dashboard-new-posts-statistics-broken/352599?silent=true), there’s much to learn about debugging Discourse in general, but only a small part of the conversation is about the specific plugin causing the issue. I don’t think it would be ideal to move the entire conversation into the plugin’s topic, as this isn’t the place where I would look for examples on how to narrow down problems.
Therefore, I think keeping it in its own topic with a #3rd-party tag would make more sense. It might be better to place this in the support category rather than the bug category. That way, users can select a solution, and the topic will automatically close. In the bug category, a staff member would have to manually close it.
So, a topic could be created, replies would contain the steps to identify the cause. The post identifying it selected as the solution, the topic would be tagged with #3rd-party, and moved to another category if needed. Then the OP could notify the plugin/theme/component author by posting in the dedicated plugin/theme/component topic if they don’t already know. Though maybe even in that case, a post in the topic would be helpful for others having the same issue.