Yesterday, I thought about whether a data explorer query that finds topics tagged fixed but where the user did not receive the bug reporter badge, combined with an automation that sends that report to a group, would help catch these cases and ensure the users get the badge they deserve. However this will only catch those where the tag was added 
But I don’t think it makes sense to use all the closed bug topics as a basis, because that would also include the duplicate and non-reproducible ones. That’s why I am not sure if it will really help because someone would still have to check that the topics get closed and tagged. I have chosen a more general title; maybe others have some ideas where reports could help. I think Jammy had some that replaced the automatic bumping of topics.
A report for topics that were moved to the Community wiki or topics in Community wiki where the first post isn’t a wiki (and not an “about the category” topic) could be helpful too. Sometimes topics are moved to the category and making it a wiki is forgotten, or the permissions to make it a wiki are missing. An example for that is Step-by-step Discourse migration with R2 and Cloudflare integration
I like that idea but can’t help but think there must be a better way to make sure topics in Community wiki are wiki topics. I just checked and there is no filter for wiki (or not wiki), and there is also no bulk action to select topics and convert them to wiki (or not wiki). If those two features existed then it would be a no brainer to get caught up on this task.
I made that topic a wiki.
If there are topics you come across that you feel should be wikis, please just flag them as “something else” and let us know they should be wikis. We’ll be happy to make the change.
I cannot imagine how that would work. It’s not the topic that is a wiki but the individual post. If you select topics, the information about which post should become a wiki is missing.
Do you expect that many topics where the first post isn’t a wiki but you want it to be one? I didn’t expect bulk select was needed. Perhaps I am underestimating how many topics are moved to the community wiki. I thought it would be less than one per week.
Would you return topics only when the first post is a wiki or when any post in the topic is a wiki? Are only topics with no wiki posts “not wikis”, or are all topics with posts that aren’t wikis “not wikis”?
I am not a fan of wasting my option to flag a post for unimportant stuff like that. Since I can flag a post only once, I like to keep that for cases where I really need moderator attention. Making something a wiki is not urgent.
But I will be delighted to send a separate PM.
That’s a good point. I was thinking about what I think is the most common case, which is that the first post is a wiki. You’re right this wouldn’t help in cases when another post in the topic is a wiki.
I would be happy with returning topics when the fisrt post is a wiki. Though it would help to return topics that where any post is a wiki.
Is it true that you can only flag a post as something else once? I haven’t tested it. If so that might be worth looking at changing.
Sure! Always welcome a PM or chat to improve meta!
I think the brilliant thing about data explorer is that you can perform these kind of checks ad hoc without the need to wait for any new features to be developed and implemented. 
It’s very helpful when community members do flag (or just reach out) and let you know if something isn’t right, but ideally I think it’s nice to do a bit of checking as well to save them the effort when you can.
FWIW There is a search option for in:wiki, so you could do #community-wiki in:first in:wiki, but that’s no help to find which ones aren’t wikis. 
Another possible feature request could be to make it more like the topic timers, where any topic moved to a category with a default timer inherits that timer. So a category with ‘default wiki’ would apply wiki to the first post of any topics moved into the category as well as topics created there.