Skip to content

No labels!

There aren’t any labels for this repository quite yet.

AREA: accessibility
AREA: accessibility
Related to site accessibility
AREA: accounts
AREA: accounts
AREA: architecture
AREA: architecture
AREA: developer-qol
AREA: developer-qol
AREA: documentation
AREA: documentation
AREA: infrastructure
AREA: infrastructure
Server hosting and access, general infrastructure
AREA: legal
AREA: legal
Legal requirements that we have to implement
AREA: tech-debt
AREA: tech-debt
For paying off or preventing tech debt
AREA: UI/UX design
AREA: UI/UX design
AREA: UI/UX
AREA: UI/UX
Issues relating to user experience and user interface.
AREA: wst-internal
AREA: wst-internal
Issues relating to the internal management and organisation of WST, including project management.
CONVERT-TO-PROJECT: payments
CONVERT-TO-PROJECT: payments
A "Paymens" project will be created including all the issues with this label.
dependencies
dependencies
FEATURE: delegate reports
FEATURE: delegate reports
future-milestone
future-milestone
Issues which act as placeholders for milestones, for PM purposes.
github_actions
github_actions
Pull requests that update GitHub Actions code
javascript
javascript
Pull requests that update Javascript code
META: community-feedback
META: community-feedback
We want to know more from the community because the developers' opinion is not representative enough
META: controversial
META: controversial
Differing opinions on an issue, no consensus reached
META: good first issue
META: good first issue
Small/easy change which is a good introduction to working in the WCA repo
META: good second issue
META: good second issue
More involved than first issue, these help get a deeper understanding of the codebase
META: inactive-will-close-soon
META: inactive-will-close-soon
Inactive ticket that will be closed soon, unless compelling arguments are being made to keep it open
META: manual-dependency
META: manual-dependency
Dependabot updates that require manual intervention
META: move
META: move
This issue should be moved to a different repository
META: planned-in-project
META: planned-in-project
This is already planned in a Github project - no other labels needed
META: technical-clarity
META: technical-clarity
Basically for when Duncan isn't sure how something will be implemented, and this inhibits labelling
pm-only
pm-only
Issues which should be ignored, as they are purely for project management purposes
PRIORITY: backlog
PRIORITY: backlog
Items WST instends to implement, but which it considers very unimportant at present.