Skip to main content

Reporting a bug

Found something wrong? A clear report is the fastest way to get it fixed.

Where to report​

Open an issue on GitHub:

github.com/PennStateCS/AFCT/issues/new/choose

Choose Bug report and fill in the form. You will need a free GitHub account. The form asks a few short questions (which area, your role, the version) so the report arrives ready to act on.

What makes a good report​

You do not need to be technical. The most useful things are:

  • What you were doing when it happened, step by step.
  • What you expected versus what actually happened.
  • A screenshot, if it is something you can see on screen. Drag the image straight into the form.
  • The version, if you are an admin: read it from Dashboard -> System Status -> Server (the "AFCT Dashboard" line).

Please remove student data first​

AFCT holds real grades and student work. Before attaching a screenshot or log, blur or remove any student name, email, or graded submission. A report never needs a real student's details to be useful.

Security problems go somewhere else​

If you have found a security vulnerability, do not open a public bug report. Use the private security advisory instead, so the details stay confidential until a fix is released.

Before you file​

Have a quick look through the existing issues in case it is already reported. If it is, adding a comment ("this happens to me too, on version X") is more useful than a duplicate.