GSUnitedLabs / NTAPlatform

The repo upon which the Northwind Traders Basic Edition is going to be built.
GNU General Public License v3.0
0 stars 0 forks source link

Testing Git Reports #4

Open SeanCarrick opened 2 years ago

SeanCarrick commented 2 years ago

Submitter: Test Bug Report from Git Reports I am just testing how Git Reports works to be able to better design the Bug Reporter in the NTA Project

SeanCarrick commented 2 years ago

So, using the Git Reports service will take the user to a page at the Git Reports website, which we can automatically populate with the Issue Name, user's email address, and details of the bug report. The user must then fill in the captcha and click on the Submit button to actually create the issue on the repo. We can set the label and auto emails to the team, but not the Assignees.

Also, unless we put the contents of the log and error log files into the details section, there is no way of attaching them to the bug report. And, since we cannot allow anonymous access directly to the repo's issues page, there is no way to allow the application users to update the issue by attaching the files here. So, how do we get the log files to see what was going on within the application at the time of the error?

[EDIT] Another thing is that I placed my email in the Git Reports form and had the checkbox for public email selected, which states that the email address would be included in the body of the issue report, but it is not present. Is this because I am a member of the organization and repository? I may try another test bug report and use one of my other email addresses to find this out.

If the user's email address does show up in the body of the message, we could email them and ask them to reply with the log and error log files attached to their reply. However, they may have already started NTA again and the original log files may have been clobbered, so they would no longer exist. Due to this, can we come up with an alternative method for the application to have automatic bug reporting that will allow the logs to be attached to the bug report? Any ideas?