> part of a triage team
You have to realize your perspective is very different from the perspective of someone building small-scale open source software.
I don't really know if it effects me in a major way, but if it even effects me at all, it probably would make me less likely to want to fix a bug.
This was in person and in a single company, so is a bit different from issues raised by a stranger over the internet in a bug tracker.
Personally, if I don't know the person I say/write "thanks" because I mean it, especially if it's an open source project.
People are wonderfully complex :)
Since then I always separate and mark specific items in a report, usually with bullet points. It turns out pretty often, the deputy does, in fact, like dots. But it's also important to avoid duplication.
I tend to fill my report with figures having self-contained captions. That is the only thing I expect a busy reader to read. The rest of the text is a note to self.
I, too, would prefer bug reports written in verse.
It won't do what I want when I click it,
So now I will open a ticket.
It should do the right thing
And not be a pain,
Would you please help me out now and fix it?"We use AI to convert inhuman proze into haikus. Our software improves customer service satisfaction by 30%."
That doesn't mean they should write prose in their reports. Bug reports should be precise and should make it obvious what's happening to allow them to be quickly triaged and understood. They should ideally be a bulleted list with configuration, what was done, what happened, and what the user expected to happen. Logs/screenshots/etc. can be attached as necessary. It is incredibly uncommon for anything else to be necessary - and I say this from more than a decade of experience in enterprise and end user-facing software that gets thousands of feedback/bug reports per day.
As part of a triage team, I'm going through bug after bug after bug. I don't want to read paragraphs. I don't want to read your life story. I don't even really want to read your "thank you". I want to read exactly what is necessary to assign the bug to an owner and to understand its priority - no more, no less.