Do I Make New Bug Reports for Ones I See That are Vague and Long Winded or Don't Really Know What is Going On?

[Anth]

I see bug reports on the forums and see the following at times:

• The title doesn't describe the problem.
• The title is vague.
• The post content sort of points to the problem but not the cause and it's not easily replicated without a lot of testing
• The post content is a long discussion trying to get to what the issue is.
• The post content has long videos that takes forever to get to the point.
• The post content is from a user who describes the problem in text form without any pictures/files/videos/logfiles/computer specs or proof
• The bug is figured out via discussion within the post but the title never reflects the conclusion that was reached.

I have made new bug reports at least a few times based on bug reports on the forums that have some of the points above being a factor.

I spend hours on my bug reports so my fear is that adding to another bug report that my information will be missed.

If my bug report is merged into someone else's bug report I also fear that my information will be missed (hasn't happened yet)

What should I do here? Do I make a new bug report and add a link to the old bug report?

 

 

Edited April 27, 2023 by Anth12

[twich22]

I’ve just been posting all my own bug reports. It’s such a CF right now. The devs will figure it out, I am guessing they have a tracking system.