Update UX debt language in the issue workflow docs
What does this MR do?
There are inconsistencies in how the UX debt label is being applied to issues. It is requiring a significant amount of effort to review and de-label the issues that do not fit our definition for usage. The goal of this change is to help folks understand the UX debt label is used only when intentional decisions are made to deviate from an MVC, which sacrifices the user experience.
The proposed language is the same as the language used in the label description within the product.
Additional context: The UX department tracks UX debt as a PI so getting more accurate usage will help us better understand how we're doing in addressing these types of issues.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team