Migrate to new Issue Templates

[Builditluc]

GitHub recently released issue forms in beta. They are a new way of creating issues, allowing the user to interactively create an issue with buttons, drop-downs, forms, and much more. This is way more user-friendlier than the current issue templates, so we'll migrate our current issue templates over to the new issue forms. This migration can be used to update the outdated issue templates.

We’ll also add another issue template, the crash-report template. It is similar to the bug-report template, but has different fields to give us further information on the crash. Because a bug that is causing a crash to occur has to be at a higher priority than for example a small visual bug, we need to add some simple priority labels as well.

Checklist

• [ ] Update instructions in the crash message
• [ ] Rewrite feature-request issue template
• [ ] Rewrite bug-report issue template
• [ ] Add crash-report issue template
• [x] Add different bug labels

References

• https://github.com/stevemao/github-issue-templates/blob/master/.github/ISSUE_TEMPLATE/BUG-REPORT.yml

[Builditluc]

Blocking this feature because the following issues have to be completed first:

• #135

[Builditluc]

Because there are different types of bugs that each need other information (for example, a crash needs the crash log but a simple UI error like incorrect borders does not), I would suggest adding multiple types of bug labels. Currently, I can think of these types:

• bug (needs to be assigned to every bug-related issue)
• crash (when the bug causes a crash)
• parser (parsing related errors like incorrect lists or missing elements)
• ui (anything related to the UI. That includes link selection issues and control bugs)

Every bug-related issue would get the type: bug label and then, if necessary, also a sub-label that further specifies the type of bug. For example, a crash report would get the labels type: bug and bug-type: crash