You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As read here on TRF, some users have trouble reporting bugs. We should try to improve the ease of bug-reporting (e.g. send the bug report to a mail or server somewhere, from which we can put it on GitHub, or find some way to automate GitHub issue creation).
One thing I can think of is to createa a separate text box for users to write the steps to reproduce the error, and another one that displays the bug information. I think users are often confused by all the error text and don't see that you're supposed to report the steps to reproduce the bug. The lack of reproduction information is hard to top in terms of frustration.
I've also been wondering about the idea to add a 'survey' feature to OR. So that after e.g. the 15th time you open OpenRocket, you get a pop-up saying something like "Hey, do you like OpenRocket so far? Do you have suggestions to make it better?".
The text was updated successfully, but these errors were encountered:
Source Forge 2022-07-30:
Version 22.02 beta 04
Please let the bug report dialog info be copied so we can send an email. The linkages force a use of mail programs thru windows which none of my students have or are allowed to use and we do not allow them access to github or other outside systems.
Source Forge 2022-07-30: Version 22.02 beta 04 Please let the bug report dialog info be copied so we can send an email. The linkages force a use of mail programs thru windows which none of my students have or are allowed to use and we do not allow them access to github or other outside systems.
I don't really understand, you can just select and copy the text from the bug report?
It's a little hard to read... I think the requester is probably in a school environment, and the students aren't allowed access to email clients or off-campus web sites, so they want OR to include some rudimentary MUA that sends an email from within the program. While firing off a bug report from within OR seems like a good idea, I don't really like a one-way bug reporting channel that we can't respond to and try to get more details on.
As read here on TRF, some users have trouble reporting bugs. We should try to improve the ease of bug-reporting (e.g. send the bug report to a mail or server somewhere, from which we can put it on GitHub, or find some way to automate GitHub issue creation).
One thing I can think of is to createa a separate text box for users to write the steps to reproduce the error, and another one that displays the bug information. I think users are often confused by all the error text and don't see that you're supposed to report the steps to reproduce the bug. The lack of reproduction information is hard to top in terms of frustration.
I've also been wondering about the idea to add a 'survey' feature to OR. So that after e.g. the 15th time you open OpenRocket, you get a pop-up saying something like "Hey, do you like OpenRocket so far? Do you have suggestions to make it better?".
The text was updated successfully, but these errors were encountered: