Labels in Jira are tags or keywords that you can add to issues to show whether they possess certain characteristics. They let you classify issues more flexibly and more informally than by assigning version numbers or components.
...
Mob&Apps developers can’t create labels such as “ready for UAT”. They have to choose between “ready_for_UAT” and “ready-for-UAT”, or use another, similar approach. This latter label, for instance, can be used to tag all issues representing newly developed features that are ready to be rolled out to end users for acceptance testing.
This problem is resolved by Colored Labels Label Manager for Jira.
Example – Possible risks
Like any other tool, labels can indeed be misused. Any authorized user can add labels to an issue as long as the label field is available on the issue. Consequently, it’s easy to end up with a very large number of labels. The danger here is that the project can end up with numerous capitalization and spelling variations, e.g., login vs. Login, user vs. User, ready_for_UAT vs. ready_for_uat, etc. This can, in turn, render searching via labels inefficient and prone to error. Below, we’ll share our best practices for avoiding this situation.
This problem is resolved by Colored Labels Label Manager for Jira.
Atlassian Expert good practices
...