This name is already in use, try another.

[Jesse Chelin]

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?

[Ivor · Accepted solution]

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.

[Jesse Chelin]

This is incredibly annoying :/

[Jan-Hendrik Spieth]

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?

[Jesse Chelin]

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.

[Ivor]

---

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]

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 :)