Skip to content

"UX" and "UX Team" labels are too similar and cause confusion

At present, we have two similar-but-different global UX labels:

  • UX: which people use across the Tor Project to indicate an issue that has some impact on the user experience of our products.
  • UX Team: which we use to track issues that will require work from a member of the UX Team.

Given that the bucked of issues that could be tagged as UX is very, very broad – and not necessarily useful to filter by – I'm beginning to think we should replace both with a Needs UX label that's far narrower in scope. This label should then be used to invoke a UX team-member, rather than pinging people individually in Gitlab or IRC, and can remain tagged as such until the UX Team feels it's no longer necessary to track the issue on our kanban.

So, thoughts?

Edited by donuts
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information