[bug]: Impossible to find label

[wamaw123]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current behavior

It is either that labels are limited to each project / sub-project or I can't access labels in my workspace and need to recreate them for different issues.

Steps to reproduce

Set label for an Issue Try to set the same label for another issue Impossible to see the first label even when reloading the workspace : either the labels are restricted to the project (which is very limiting) and thus comon labels must exist in multiple versions, or there is issue to access the labels globally in the workspace.

Browser

Google Chrome

Version

Cloud

[vihar]

@wamaw123, sorry for the delayed reply. Currently, labels are restricted and managed through project settings, and can't be used across the entire workspace.

To address this, we're introducing project templates. You'll be able to copy an entire project's configuration, like labels, estimates, state workflows, integrations, and use it as a template for other projects. However, there might be times when you don't want to use the full project as a template.

What do you think would be the easiest solution for this?

• Create custom templates for project settings at the workspace level
• A simpler way to borrow settings, like exporting selected labels and importing them into a different project
• Or maybe just an option to toggle workspace-level settings to replicate the settings of the primary project.

You could help us very well here if you tell us why you are looking for this feature and what would be the easiest way for you to solve for it.

[tim-the-arcane]

I think it would be great to have the option for workspace labels, as it would allow them to be used for custom views as well.

Example:

My manager would like to have a view for all issues with the "Billing" tag across all projects. Right now, that's not possible because each project has its own "Billing" label. In the analytics view, they're not grouped together properly either, which defeats their purpose when looking at all projects.

[tkjaergaard]

I agree with @tim-the-arcane on this. We also want to take advantage of the views feature. But with every project having their own labels, we continuously need to update the view, and select the labels.

Maybe at least group the labels that are the same into a single label for the views. So if you have a label called "billing" across multiple projects, group them into a single "billing" label for the views filer. Then backed by templates it could work.