Review of UX ready label and it's usage
The UX ready label has been around for some time and basically means that an issue is done in terms of UX.
Lately, at the Verify and Release teams, we have gone to consider UX ready as the label which should applied to all FE related issues, even the ones that don't need UX, so everyone knows designers took a look. This, however, introduces double meaning towards the label: UX is done and UX considered.
Lastly, I'd like to add that if no UX label has been applied it generally means no UX work is required. Overall I'd argue this is the correct behavior though one which requires a good oversight from UX on every issue in the milestone and future milestones. If one is overlooked it can easily mean that UX might be involved a little too late.
Additionally, I want to mention that UX ready has been considered transactional throughout its history and that it has been used by the FE team as a clear indicator that FE work cannot start yet for a certain issue. This seems like an additional indicator that we might want to rethink this label.
- Let's discuss the use of the UX ready across the different teams as it's currently used.
- Consider the pro's and con's of getting rid of UX ready entirely (this might touch PM Ready as well)
- Consider if we need a label assignment to indicate "UX considered"
gitlab-ee#9175 (closed) might introduce the concept of binary labels