ZenHub uses GitHub repo's native label set to populate which available labels exist when navigating issues in ZenHub.
Creating labels in GitHub (to show up in ZenHub)
To create new labels, you have to work within GitHub. At the moment, labels cannot be created in the ZenHub web app.
In GitHub, navigate to the repository where you want to create or edit a label. Next, navigate to Issues and further click on Labels next to the search.To create a new label, click New label on the top right.
You can also edit or delete existing labels in the same interface using the label table.
Using emojis in labels
Both GitHub and ZenHub do support using emojis in label names, as long as other text accompanies the emojis. You'll need to use the native emoji keyboard instead of using the text shortcuts.
For example, if you're using an Apple keyboard, you can bring up this keyboard with the following shortcut : ctrl +cmd+space :
Alternatively, you can copy and paste emojis into labels when creating or editing them.
Creating the same set of labels across all connected repos
Since labels are native to GitHub, label-sets are repo-dependent. Because ZenHub adds a layer of being able to create Workspaces using multiple repos, we share a workaround to create the same set of labels cross-repo in this article.
You can also add your vote and comments on the feature request to make this more streamlined in our feature request product portal.
Why you might not be seeing an available label to assign an issue in a Workspace
If you've created a multi-repo Board, because labels belong to a repo, not a ZenHub Workspace, you might be misidentifying an issue existing in one repo with the label you're looking for in the other repo connected.
Issues still belong to repos, so when assigning labels to issues, only the available labels from the repo the issue lives in will be available. At this time ZenHub does not pull in labels from other connected repos in the issue itself.
Use the suggested creation of labels cross-repo workflow, using multi-action, to assign labels to issues that might only exist in some of your connected repos.