Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

12

I don't really understand why this got so many votes. The question is not "how to write a decent bug report?" but "how to get users to write a decent bug report".

Tamás Szelei
– Tamás Szelei

2012-05-18 08:45:29 +00:00
Commented May 18, 2012 at 8:45
8

Those resources are mostly targeted at technical people. Also Mozilla is the organization that brought us Bugzilla. I'm not saying that Bugzilla is bad, but it's been made by engineers for engineers: It's really not an end-user tool at all.

Joachim Sauer
– Joachim Sauer

2012-05-18 08:45:57 +00:00
Commented May 18, 2012 at 8:45
3

Have to agree with @fish. We can give our testers all the guidelines in the world - doesn't make them actually produce useful bug reports. And I'm talking about people who's job it is to report bugs - if we can't motivate them with guidelines we've got no hope at all with actual users. The only thing we found effective was actively closing "useless" bug reports as "not enough information" - they got the the message pretty quickly then. I don't advise it for external users though :-)

Arjailer
– Arjailer

2012-05-18 11:36:12 +00:00
Commented May 18, 2012 at 11:36
3

I'm not debating the usefulness of the post at all (quite good resources there, really) but this does not answer the question, and I think the voting policy is based on that (I might be wrong).

Tamás Szelei
– Tamás Szelei

2012-05-18 13:26:15 +00:00
Commented May 18, 2012 at 13:26
1

I'm the sort of person this was aimed at and even I couldn't sit through reading the whole thing. What makes you think users are going to?

Tacroy
– Tacroy

2012-05-18 17:08:29 +00:00
Commented May 18, 2012 at 17:08

| Show 6 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »