Labels in business managed project not populating to all instances

Question

I've added a label type ("Confidential") to the Labels field the the primary instance of a business managed project. Several other projects use this configuration. However, other users don't see the "confidential" label as an option in the other boards. My understanding was that labels were supposed to be universal across business-managed projects?

Bill Sheboy · Answer

That is a curious symptom...

Labels are stored with the issues that use them.  When a new one is added, it is available everywhere for selection (other than the exceptions I noted above).  Only when the last occurrence of a value's usage is removed from issues does it vanish.

What do you mean by "top-level template"?

Are all of these projects in the same Jira site / instance?

Has someone created a custom field with the same / similar name of Labels?  In that case, the available values would vary for the different fields.

Geneva Skeen · Answer

Hi Bill, thanks for the response.

There aren't more than 100 labels in our instance, no - so that shouldn't be the blocker here.

To clarify setup here: there is a business managed work management project that I've used to serve as a template configuration for 8 other similar projects across departments. Each department should be using similar terminology, including the values for the Labels field, which is available for each issue in each project.

Ex:

The problem is that the Label values I've created in the top-level template ('confidential' being one of them) aren't being pulled down to any of the other 8 projects; at least not for other users. Those users are having to create their own new values within the Label field.

Bill Sheboy · Answer

Hi @Geneva Skeen -- Welcome to the Atlassian Community!

First to confirm some terminology, are you asking about the Labels field for issues?  If so, those are shared across all projects for a Jira site.

And, when you describe:

However, other users don't see the "confidential" label as an option in the other boards.

Where in Jira are those other users trying to use the label value?  What were they trying to do when this happened?

There is an open defect JRACLOUD-82068 for Jira Work Management (JWM) projects where labels may not be listed when there are more than 100 labels existing in the site.  Does that apply for your case?

Kind regards,
Bill