A very bad feature, for a large jira dc system, is a very disappointing feature, needs to be optimized, has affected our JIRA datacenter with 20,000 users, the persistent node is down during the day, we are wondering if we can still keep using jira

You can only do this by creating a different custom field (Type of label) for each project. 

https://getsupport.atlassian.com/browse/GHS-241615

Each Label field that is added as a custom field, should have an option for its Field suggestions. You  should be able to configure the suggestions list in terms of scope, possible options could be

Global Scope       

Any value added to any label field in any project will show as a suggestion when you type in any label field in any project

Project Scope

Any value added to any label field in the same project will show as a suggestion when you type in any label field in the same project

Field Scope  (if field shared between projects - suggestion list transcends project)

Any value added to the same label field in any project, that shares that field, will show as a suggestion when you type in the same label field in any project

Local Field Only Scope  (if field shared between projects - suggestion list DOES NOT transcends projects)

Only values added to the label field will show as suggestions when you type in the same label field in the same project

Thanks

Marcus

No, that doesn't work. See my crude work around above.

Can't this be implemented via the label custom fields' Configuration > Add new context? I already expected it to work like that, but unfortunately, all suggestions appear on a global context.

My god what a ridiculous answer with no reasoning. This change should be a 1 liner and would make my life so much easier. 

A really crude workaround is to create 1 custom label field per project or group of projects where sharing labels is ok.

I had hoped that a custom label field could give you this result by setting up a different configuration scheme for each project in that custom label field. Unfortunately that still resulted in labels being shared across projects.  Can it at least be made so that this would work?

We stopped to use labels on our organization because of this missing feature. Is a major blocker for being adopted across all the development teams.

Custom label fields is a workaround, in my opinion. This is a basic feature for Agile platform in multi-departamental organizations.

@Shannon Making custom label fields (as suggested by Greg) is a good solution for you.  That approach gives you great flexibility since it lets you control the scope of each label field exactly as you wish, so it can be even better than simply a choice between "Project scope" or "Global scope" if you are dealing with many projects across many customers.  TBH, I think it is a better way to go than the change in this suggestion.

The lack of project specific labels is a major reason why we are not implementing JIRA across our 100 member development team.  We are working on a dozen plus projects across multiple industries at any given time, and the lack of project specific labels basically makes implementing JIRA globally a deal breaker.

"That's not to say we will never implement it"

But given Atlassian's track record, that is exactly how you should treat it, and plan your business accordingly.

snielson1725567118 when we say it's not on our roadmap it means we don't have plans to work on this feature in the foreseeable future. That's not to say we will never implement it, and we continuously reevaluate our roadmap and priorities to ensure we're working on what we believe will bring the most benefit to the most customers. Unfortunately, the reality is that there are vastly more feature requests that have merit than our development team could feasibly work on (and feature requests don't tend to capture the many other investments we make in performance, usability, helping new users get started, fixing bugs, and engineering health).

We can only work on a small number of features at a time, we don't try to pretend that we can schedule every feature across a large and complex product for multiple years (not very agile), and we try to be as forthcoming as possible to our customers about our priorities, in accordance with our company values.

All this is to say that it's not that this feature is without some merit, just not necessarily a priority right now. Hope this helps.

Regards,
Dave Meyer
Senior Product Manager, JIRA

@dmeyer your comment seems to suggest that this request has been evaluated and rejected. Why? It makes complete sense to suggest labels already in use in the current project. You could still list others, but at least prioritize the ones already used by the current project. Label management otherwise is a nightmare, because nobody can remember the exact label, which of the various label version they are using, and if you set up Quick Filters on those labels, stuff starts to get lost.

Try out Label Manager for JIRA to manage Labels from Project Admin Screen. It locks down labels so that not every user can create new items.
The admin or project admin can create, rename and delete items.
It is possible to use these label fields for all projects or for each JIRA project individual.

There are some more useful features like using colors for label items or adding, deleting, validating items during workflows.
It's for free by using the promotion link at the end of the details description.
https://marketplace.atlassian.com/plugins/rs.codecentric.label-manager-project/server/overview

We have 100's of programs, each with a JIRA project. But we want commonality between the projects so we use the same project configurations (custom fields, screens, etc). but these are still very different and distinct programs so it make no sense for the label spaces to overlap. It really makes using the label type for a custom field almost useless.
Really need the option to make the label space different for each project (or at least option on the project admin to make label name space just for project).

@ Johann - a crappy workaround, until such time (never?) that Atlassian actually fix this issue, is to make a new labels custom field, and apply it for each project.

Each label field has its own 'labelspace', so if you have ProjectXXLabels and ProjectYYLabels, the content of XX won't be visible to YY and vice versa.

Labels have now become unmanageable as another project has used (abused?) labels extensively and now it's near impossible to find labels that make sense for our project.

Hi Pete,

Not sure why you'd be running a single Jira instance for multiple different customers, but what you can do is make your own custom field using the label type. When you do that, the labels and suggestions for that field are isolated to only that field. So you could create different custom fields for each of your customers, thereby removing any chance of cross-contamination.

The issue of cross-project contamination with these custom fields still remains however, but at least you have a workaround for your particular concern.

I see that the Label cross Contamination is being worked on in JRA-23656.

This ticket does address the issue with the cross contamination of suggestions.
Please make this a priority as it does have a direct impact on out business and the use of jira by our clients.

As we are a consulting organization with multiple clients that are in competition with each other, the smallest visibility in to other projects by a client could be very detrimental to our business and client confidentiality agreements.

Please make this a top priority and keep open

This should be a project level option. Some projects may want label suggestions to be scoped to their project, others may not.

Sorely needed feature!
Many projects and an expectation that they actually are project local creates problems already. We've been using Jira since monday..

Disappointed that we’ve reached Jira 6.2 and this still has not been addressed.

Really surprised that they didn't do this in the first place.

We would require this feature as well, as we have many different projects.

This is very important to us. We have many different teams using Jira. We would really like to see this improvement resolved

Highly required for us, we would really like to see this improvement resolved.

Please implement this!

Highly required, many projects suffer without it.
Please implement.

I agree, this is important feature to keep order in labels. We have numerous projects each with it´s own set of labels. So it´s dificult for common user to select right label belonging to current project.

This is also an interesting feature that would help us to guarantee that one project has its own set of available labels

Yes we need absolutely this feature too because the need is the same.

Its odd. When you go to the project/labels tab, and you select "all labels" you will only see labels used per project. But the "suggestions" for labels when creating an issue seem to be by global popularity instead of project popularity. I guess I could see the argument for both cases but I would think having the suggestions based on the popularity of a label within the project would be best.

So, I agree with the issue and would think that label suggestions should be scoped by project (the most popular and/or recent) labels used in a project.

I would say that this is actually a regression. In Jira 4.1, using Labels plugin 2.4.1, label suggestions are scoped by project ... except in the Create Issue Screen