-
Suggestion
-
Resolution: Unresolved
-
39
-
43
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.
At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
The suggestions for labels should be scoped by labels used in a given project. Or perhaps limited to a project or group specific list.
When multiple teams are using JIRA, they have different conventions for labels for their issues. By using a single namespace for the suggestions, the teams are presented with potentially ambiguous or misleading suggestions.
- has a derivative of
-
JRACLOUD-43060 Option for labels to only be visible to all projects based on project category
- Closed
-
JRACLOUD-43296 Restrict a label by project
- Gathering Interest
- is duplicated by
-
JRACLOUD-74850 Labels Suggestion based on Global (all projects) or Per Project (suggest labels based on labels used on issues available on specific projects)
- Closed
- is related to
-
JRACLOUD-80360 Labels suggestion should be scoped by field
- Gathering Interest
-
JRASERVER-23656 Labels suggestion should be scoped by project
- Gathering Interest