Repository: stable-diffusion-webui
Issue: [Feature Request]: Putting more responsibility on users for their error-reports
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Hello a1111 Fans, 

I am going through a number of issue reports and many of the issues are not followed up neither by the users filing the issues nor the repo contributors. Do not get me wrong, I am NOT scattering blame, I provide my perspective of how you as users can contribute to a more efficient error handling process:

I would propose that every user that files an issue should be sure to take the responsibility to follow-up up on the issue the she/he filed (provide data, provide feedback, close issues when the issue should be resolved after an upgrade, etc.). 

The a1111 repo has currently 2k open issues, 90% stuck in the status "bug report", i.e. an issue being filed without being reproduced nor being flagged as "to patch". I believe many of the issues are patched in-between without updating the long list of bug-reports (who in the world can literally go through 2k issues??) You users can help greatly by applying the discipline to close outdated issues giving the repo team more overview and guidance on burning issues of the current version.

### Proposed workflow

Provide information: 
It sounds obvious but ALL information is good (and I see many reports where there is less than rudimentary information being provided)
- What is your system (operating system, gpu, vram, ram, python version, starting parameters, did you modify files in your repo, etc.)
- If something does not work anymore and worked in a previous commit, please provide that information (the old commit you'll find in the meta-data of your images before your upgrade). Comparing two commits if they are not too far apart can help narrowing down the issue quicker..
- If something breaks without updating the repo it is probably something on your machine, did you make any changes recently?
- Explain the steps how you got to the problem... it sounds silly but to reproduce an error it is truely helpful to know what exactly you do (somethings users forget to say they clicked a "button x"... the better you provide your exact steps the less time the team will need to reproduce your error and will have more time patching your error, patching other errors, adding features...
>>Any developer will appreciate your effort and will be more likely to help you.

Follow-up
Be aware that only errors that the developers can reproduce can also be identified. 
Not all errors can be patched necessarily as some issues lay beyond the capability of the repo to manage (e.g. python or torch related issues)
Help to follow-up -> be active, make sure the devs have the information that they need, double check that they do. 
Verify if your issues remain in the current version, if they dont: close your issue. If they do and your issue is already 3 months old, get in touch with the devs to understand if you should update your commit on your filing or rather file fresh.

Please dont throw sticks and stones at me :-)

### Additional information

_No response_