• placatedmayhem@lemmy.world
    link
    fedilink
    English
    arrow-up
    38
    ·
    edit-2
    2 months ago

    Yes. I’m not sure what you think makes you bad at writing bug reports, but here are tips I give to everyone (my day job involves working with bug reports).

    Nominally, a decent bug report should have:

    • the steps that got you the bug
    • whether you can reproduce the bug
    • what you expected to happen instead of the bug

    Doing any of these things makes bug reports so much more actionable. You can do it. I believe in you!

    Edit: Including a contact method so the software developer can have a conversation with you can also be helpful but not strictly required. Some bug reporting methods do this implicitly, like email bug reports and GitHub issues.