nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

This name is already in use, try another.

Jesse Chelin_6wazrb

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:

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?

Accepted answers

Ivor_1r8wvh

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.

All comments

Ivor_1r8wvh

Jesse Chelin_6wazrb

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_6wazrb

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.

Welcome!

It looks like you're new here. Sign in or register to get started.