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

This name is already in use, try another.

I have around 50 custom fields in JPD, however it seems like I might have hit some sort of limit.


I am trying to create another field and receiving this error:


This name is already in use, try another.


I know for a fact that the name is not already in use, as it doesn't matter what value I put in for the field name, I always receive this error.

Have I hit a custom field limit and the error is just wrong?

Any thoughts?

1 answer

1 accepted

Suggest an answer

Log in or Sign up to answer
3 votes
Answer accepted

Team managed projects which is what jpd is built on are limited to 50 custom fields as I have been told as well. I'm not sure if they will plan to have company managed projects in the future which will allow more fields to be added.

This is incredibly annoying :/

Uuh, that's really good to know. We'd better keep an eye on not having too many experimental fields. Guess the idea to have fields specific to individual delivery projects (think "Roadmap for Component A", "Roadmap for Component B", ...) should be used very sparse, too :-/

Atlassian, any chance this restriction can be lifted, or increased?

We are migrating from Productboard to JPD, and have ALOT of custom fields which we use for various prioritisation frameworks, so this is rather limiting.

Like # people like this

Yup, the same for me as well. I also used to have a lot of calculated/derived fields which are used for reports. Some of them I've tried to migrate to automation rules with variables to store derived values to further determine other values but it is painstakingly annoying 

Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 28, 2022

Thanks all. We're looking at how we can increase that limit, but indeed it's limited to 50. as a first step we'll make that error message better :) 

Like # people like this
AUG Leaders

Atlassian Community Events