-
Notifications
You must be signed in to change notification settings - Fork 10
Description
Is there an existing issue for this feature request?
- I have searched the existing issues
Is your feature request related to a problem?
Filing a bug should be built into Snapmaker OrcaSlicer as a menu option that automatically fills out most relevant fields and includes log files and project files to optionally be uploaded (pending confirmation from the user). Filing a bug this way would bypass a lot of the very tedious steps of filing a bug right now in Snapmaker OrcaSlicer and ultimately help find more issues because the current process is detering people from filing bugs.
The current procedure for filing a bug is extremely tedious. It required manually going to the github page then having to fill out many fields of information, which are often not relevant to the current problem. While this data is always good to have, it is far too difficult to file a bug with Snapmaker Orcaslicer, so people will not file bugs at all.
It also requires you to manually go to the logs and upload them, and they aren't even provided in a format that can be uploaded to Github so you first need to zip them and then upload them.
You then also have to save the project file and upload that.
And you need to manually check the current Snapmaker version, which is not immediately displayed anywhere so you need to go into the top menu, go to help, then click the about button to open a popup that shows the version. Even still, that pop up doesn't let you select and copy text so you still have to manually type out the version!
You also need to manually write out the procedural steps, expected results, and actual results instead of being able to provide all of the relevant info in one box.
This difficulty just means that people will give up on filing bugs with Snapmaker Orcaslicer. Automatically filling out program and OS version data, and automatically linking log and project files (optionally by user input) will drastically help improve the bug filing process. Removing the different paragraph fields for steps, expected results, actual results, etc and just having one main text field which guides people to provide that information will also help people to choose what information is actually relevant. There is a reason that bug tracking in software giants is done this way rather than having separate fields for every piece of detail.
Which printers will be beneficial to this feature?
All
Describe the solution you'd like
Filing a bug should be built into Snapmaker OrcaSlicer as a menu option that automatically fills out most relevant fields and includes log files and project files to optionally be uploaded (pending confirmation from the user). Filing a bug this way would bypass a lot of the very tedious steps of filing a bug right now in Snapmaker OrcaSlicer and ultimately help find more issues because the current process is detering people from filing bugs.
Describe alternatives you've considered
No response
Additional context
No response