Comment by neilv

Yes, disappointing handling of the bug reports, discouraging that person from doing bug reports again for anyone.

As a submitter, you can decide to invest in someone's detailed bug report form, including attaching screenshots, etc., maybe taking an hour or more, and derailing the work mental mode you were in.

After that work, what you learn most likely happens next is one of the following:

* Silence.

* "Yes, that's a problem." Then silence.

* 6 months later, automated email saying that this bug is automatically closed, due to inactivity.

* 2 years later, automated email that they've done a new release, so they've decided to throw away all open bug reports. But if you still find the bug in the new version, you can file a new bug report, they graciously offer.

* "We know about that bug, but we aren't going to fix it." For reasons you don't understand. And if there's a cultural mismatch, the tone can come across as hostile or disingenuous, besides.

* "This is a duplicate of bug X." It is not.

* Closes the bug report suspiciously, perhaps for optics or metrics.

* (Silence FAANG Special Edition: A high-profile bug report, on which tens or hundreds of knowledgeable people are adding on, for years, all saying this bug is a huge problem, and many asking in the bug report comments why is nobody from the FAANG even acknowledging this bug report in their own bug system.)

Suggested practice: If you ask others to invest in reporting bugs (by having that bug report form there), then follow through in good faith on the bug reports you receive. (At least on the bug reports that seemed reasonable, and that invested effort in your process.)