Anything that is broken

Not a bug, not a feature, just code cleanup.

Self-explanatory

Simple tasks that are good for people wanting to get started on stuff

Anything that involves API changes, should generally only be for PRs or bug reports on in-progress features.

Indicates a test case exists and is up-to-date.

A bug report, needs verification that it's actually a bug.

A PR that needs the code to be verified by someone.

Needs a test case or other reproduction of the issue.

Anything that is blocking on the submitter.

Cannot progress until the core team has discussed further.

A performance related issue. We could track this as a bug, but usually these would have slightly lower priority than standard bugs.

A well defined bug, with a PR pending to fix.

A well defined bug, needs someone to PR a fix.

A bug that did not exist in previous versions and isn't a new feature (applied in tandem with Bug)

Things to do with automated testing

User interface and experierence