Read First!
-
@ubernaut said in Read First!:
@LaFayette maybe make an option to choose between current behavior and rudimentary auto report?
what happens now if someone tries to report a bug and doesn't have a github account?Current behavior in 1.9 is typically "here is a link for reporting bugs".
The auto-report uses the triplea 'bot' account from the backend and does not rely on a personal github account.You can see some examples of what an auto-report looks like when it lands in github issues here:
-
@LaFayette so currently there is an auto report option for people without github accounts? if so im not sure i understand how 1 is different from 2.
-
@ubernaut The auto-report sends data to the TripleA backend which uses its own github account to create the ticket. So yes, no github account required.
Re: 1vs2 - Option 2, currently you have to have a java exception for the auto-report window to show up. Option 1 is in addition to option 2 and would replace the "report a bug" menu item to instead show the auto-report window. Today and with option 2, the 'report a bug' menu item just gives you a link.
-
@LaFayette gotcha thanks seems like 1 would be better unless you figure more people would opt for the auto report even though they have github accounts.
-
@ubernaut I don't think creating a github account is actually a barrier for most people. Those participating on the forum here, I respect that the half dozen do not want to divide their attention just as I don't want to divide my attention between most locations.
The real problem with a free-form auto-report feature is ensuring there is good quality to the bug report. The github bug report gives you a series of optional questions that make it easy to know what to include. Without that, a free-form field becomes very daunting to know what to include. If not daunting, there is no way to track it back to someone, so we can't ask for a save-game, or maybe even which map, which phase of game play.
I tried to create a UI that would help guide a user through that series of questions, it started to seem like a lot. In the end the effort is duplicated some, if creating an account on github is too much, there likely is not going to be enough follow-up for a free-form bug report.
-
Just to contrast, on a game-crash, there is a 'java stack trace' which developers can look at without anything else and often create a fix. Hence the current auto-report feature in prerelease can submit that info to the backend without providing any additional information. The extra info is really gravy and helps the dev team know where/how the problem occurred (sometimes necessary, some traces are really hard to reproduce)
-
@LaFayette makes sense to me
-
i think there is something wrong with the battle calculator currently the one land unit must survive checkbox doesn't seem to have any effect on the results.
-
@ubernaut and all please read first post!
-
@prastle bump link fixed in first post
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login