Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Field Types: Are there plans for multiple labels, dependent dropdowns, or other field types?

Are there plans to allow creation of multiple "labels" fields?

CONTEXT (I will start this as a separate discussion thread though!). We have started proof-of-concepting JPD by having all our product teams in the same single JPD space. One of our challenges is a combination of field type availability +/- making JPD a company-managed project type... It's AWESOME to utilize the flexibility and insight of JPD across all our teams, BUT we also can't figure out how to have certain fields that would be unique to different product groups without having WAY too many fields in JPD.

1 answer

2 votes
Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 16, 2022

Hi @J P - you're right, JPD doesn't support company-managed yet, and you can't yet share field definition between projects, which creates complications. 

There are a few things we have planned, but most of them are further out as they require underlying Jira platform changes. 

  • The first thing we'll do is to let you create a project based on another one (copy all field definitions, views, etc.). The main limitation with this approach is that any change you make you'll need to make in all projects
  • After that we'll add a way to share fields between projects (which should answer most of the problems)
  • And finally we are looking into supporting company-managed, but that's much further out. 

In the meantime you have 2 options: 

As for creating multiple labels field: you can create multiple "multi-select" fields which let you do the same thing as a labels field (with the added benefit that label names can contain spaces, but the limitation that not everyone can create a new label - only people who can manage fields for the project. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events