Our organization currently is subscribed to JIRA and Confluence Cloud. We are wanting to add more issue types and configure more custom fields. We need to have an understanding what is the custom field count limitation and how many are available to consume or have been used in our current instance?
The technical limit is so large you'll have made your system utterly unusable before you put a dent in it.
To see how many you have, look at Admin -> Issues -> Custom fields.
As a general rule, I don't start to worry until a system hits 100, but if it has more, I start to look for reasons. I've inherited a system with 4,000 once, and while it technially worked fine, it was a pig to look after and a total mess when it came to reporting. If you're creating lots of custom fields, you really need to insist that they are used and useful and that they're used and named appropriately.
Hi. This doesn't seem to be the case anymore? I'm encountering an issue, since I've reached 50 fields in one service desk project. And I'm prompted with "You can't add more than 50 fields in your Service Desk." See photo attached:
Is there a workaround I'm missing? Right now, we're looking into separating forms in different projects but that's not very ideal since it will affect reports extraction. Any inputs would help. Thanks!
I'm also getting a limit warning after 50, I didn't understand why there is an hard limit like that.
There was a post posted by an Atlassian staff that there is a soft limit which supposedly can be lifted if you contact Atlassian.
I've tried to contact them but they've given me a different reason and for some reason I am unable to find the original post
In the new Jira cloud update (we use Jira Work Management) - I have 124 custom fields but I am unable to add any more. Is there a reason for this? Will we get more custom fields. We are working on automating a huge range of processes and have the fields to help with reporting but we have now hit our limit
What does "unable to add" look like? What is stopping you during the "add field" process?
Hi Nic,
Apologies for the delay - I didn't see a notication come through on this.
When I go to add an extra field (I couldn't seem to screenshot it) - it has a little 'stop' sign and won't let me drag any more fields to the issue.
I've been through and deleted a heap of custom fields to remove them and add the 'prompt' to the description box. It would be better to have them as custom fields so we can report on them
Thanks,
You never need to apologise for a delay. This is a public forum, we are all busy, and we all understand people here have other things to do.I think you've run into team-managed project limitations. They stop us from adding fields when it's a bit too much for humans. I seem to remember the limit is about 50-ish.I think you will need to move to company-managed projects, if you want over (whatever the current limit is) as they have no limits on their field numbers.
But I cannot tell you that this is wrong. There are many cases where filling in loads of fields is right. I would question it, because I'm a massive fan of "keep it simple for the end user", but I do not know what field you work in, so I have no way to know.
It looks like you're new here. Sign in or register to get started.
