I understand the -1, but you have to understand that to a user the choice is sometimes between:

1. Create crappy bug report and move on quickly to get things done or:

2. Do not create a bug report and move on immediately, to get things done

I try to file whenever I can but when it's getting late and I want to go to bed I choose option 1 sometimes. Maybe I should choose option 2?

For example, take the Nextcloud bug filing template on GitHub [0]. It's quite a long read but sure, worth the effort for free software I agree (Nextcloud is my favorite project, my life is in there, on my server)! However, I may not know exactly where these things are:

    ```
    #### Web server error log
    <details>
    <summary>Web server error log</summary>

    ```
    Insert your webserver log here
    ```
    </details>
    
    #### Nextcloud log (data/nextcloud.log)
    <details>
    <summary>Nextcloud log</summary>
    
    ```
    Insert your Nextcloud log here
    ```
    </details>
    
    #### Browser log
    <details>
    <summary>Browser log</summary>
    
    ```

    Insert your browser log here, this could for example include:
    
    a) The javascript console log
    b) The network log
    c) ...
    ```

They also want config.php, contents of `sudo -u www-data php occ app:list`, ask you to do this:

    Login as admin user into your Nextcloud and access 
    http://example.com/index.php/settings/integrity/failed

Also all versions:

    ### Server configuration
    
    \*Operating system:\*
    
    \*Web server:\*
    
    \*Database:\*
    
    \*PHP version:\*
    
    \*Nextcloud version:\* (see Nextcloud admin page)
    
    \*Updated from an older Nextcloud/ownCloud or fresh install:\*

Moreover, I'm quite afraid to put my domain names or even more sensitive info onto a public website if I just copy and paste. All I'm saying is that a big button that generates everything a dev needs with sensitive stuff redacted (which should be doable here and yes maybe I should make a PR for that) will make the experience a lot nicer for the reporter and the dev.

As said, the Geyser MC project [1] can do exactly this and to me it is a game changer, the whole process was fast and pleasant and it was easy to test the automated builds they made in the branch based on my issue and report back in context on GitHub. Pasting the JSON their report feature generates into their Discord channel together with your question and their ability to just !docs/something point you to relevant docs with a small command feels like magic. I found the whole process inspirational.

I love all FOSS devs. You are my heroes.

[0]: https://github.com/nextcloud/server/issues/new?assignees=&la...

[1] https://github.com/GeyserMC/Geyser