Resolving this issue would provide very real, immediate benefits to our users or would somehow greatly improve developer quality-of-life (e.g. fixing a crash on launch bug, implementing circuit display, enabling screen-reader support, automating changelog generation, etc)

Resolving this issue would provide small benefits to most users, provide substantive meaningful benefits to a small set of low-risk users, or only provide substantial benefit over the long-term (e.g. fixing a crash bug on legacy systems, minor UI polish, fixing dev-tool annoyances, etc)

Resolving this issue would provides benefits to some of our users and improve the quality of the product; not important enough to be High but too important for Low (e.g. improving the build or signing process, fixing 'annoyance' bugs, etc)

Resolving this issue would provide minimal immediate benefit or only a minor improvement over the long-term (e.g. fixing some low-probability bug, improving code-quality of some rarely-modified developer tool, etc)

Resolving this issue would provide no benefit to users or developers

Resolving this issue would have an unknown impact on users or developers

An issue which must be resolved as soon as possible as it is blocking the release

A high priority issue which nonetheless does not block the release

A low priority issue; this is work we really should do but is not important enough to prioritise right now

A medium priority issue

This issue is somehow not important yet worth keeping around

Issue for a technical review of some 3rd party code (e.g. WebRTC, WebAuthN, etc)

Issue for back-porting a changeset to a different release channel (e.g. Stable or Legacy)

Issue for a bug in the software (e.g. crash, incorrect behaviour, etc)

Issue for a task which is somehow required but shouldn't *visibily* affect the user experience (e.g. updating dependencies, cleaning up build scripts, etc)

Issue for the specifying the look, feel, and behaviour of some user experience (e.g. create a new icon for Tor Browser, design the connect assist flow on Android, etc)

Issue for updating team documentation (e.g. gitlab templates, policies, wiki, etc)

Issue for new feature or functionality (e.g. enabling a new locale, implementing connect-assist, etc)

Issue for researching some topic or proposal (e.g. requirements for integrating ublock-origin)

Issue for tracking other multi-part issues (e.g. major features, infrastructure changes, etc)