Updated bug report template: moved Context to the top #20429
Conversation
The idea of this change is that people can write tickets the way they naturally do (starting with the context) and then answering the point-blank questions like expected behaviour more concisely. After a few weeks of triaging hundreds of reports, I noticed people often start off their bug reports with a story on what went wrong, where they were etc. This is all context that is currently often put into other sections (such as "Expected behaviour" which was on the top).
|
@Stan-vw Guess that makes sense. As a further improvement we actually could consider to move that to using forms instead, to make it easier for a reporter to fill it in. The comment stuff we currently have is not that much usable. |
|
That's pretty fancy! |
|
@Stan-vw That was just an example. The forms can be designed using yml files. We don't need to add any checkboxes. I think a form would make it more clear what to fill in. And it might maybe even avoid some issue where people simply remove the whole template in order to place a question they actually should ask on the forum. |
There was a problem hiding this comment.
- Functional review done
- Potential edge cases thought about (behavior of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
- Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
- n/a Security review done
- Looks good 👍 Wording review done
- Code review done
- n/a Tests were added if useful/possible
- none Reviewed for breaking changes
- n/a Developer changelog updated if needed
- n/a Documentation added if needed
- n/a Existing documentation updated if needed
The idea of this change is that people can write tickets the way they naturally do (starting with the context) and then answering the point-blank questions like expected behaviour more concisely. After a few weeks of triaging hundreds of reports, I noticed people often start off their bug reports with a story on what went wrong, where they were etc. This is all context that is currently often put into other sections (such as "Expected behaviour" which was on the top).
Note: I also updated the shop@matomo.org email address, which is now the preferred email address.