You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
I recently hit my max number of custom fields on a Jira Service Management cloud Team-managed project. I deleted some fields to free up space, but the project is still not allowing me to add new fields. The project is still saying I have hit my max of 50 fields even after I have deleted fields.
I assume it's because it takes some time to update but it's almost 24 hours ago now and I still can't add new fields.
Does anyone have any suggestions on how to solve this?
Thank you,
@Jakob Kristoffersen Since you are on a team-managed project the fields could be associated with multiple request types. So the fields that you deleted might still be used on a different request. You need to see how many fields are being used across all project request types.
I would suggest looking into forms as a way to collect large submission sets. Unless you need to report on or filter on the information using forms will lighten the project overhead.
Hi Brant. Thank you for your reply. The fields I deleted are not part of any other request types but I still haven't gotten back the allocation from the deleted fields. I'm still getting a message that I have hit my max 50 field limit even after deleting several fields
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How many fields are you using across all requests in the project. This is how the count is determined?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jakob,
Can you share a screen shot of the error message?
And of course, the next question is - why so many custom fields?
Are these fields just on the form? Or are the mapped to Jira database fields?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
Thank you for your reply. The project requires a lot of custom fields, hence the high number. However, I'm below 50 custom fields but still getting the error message as per screenshot below:
Are these fields just on the form? Or are the mapped to Jira database fields? Not sure exactly what you mean with this question. It's custom fields used in the tickets, so they must be mapped to Jira's database I assume.
Thank you,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, you are in a Team-managed project. That is the reason for the limit. If you need more than that, you should switch to a Company-managed project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John. That you for your reply. I'm aware of the 50-field limit on Team-managed projects. My issue is that I initially hit the 50 field max, then deleted some fields to make space, but the project is still telling me that I have hit my max and won't allow me to add additional fields even after I deleted some fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would go ahead and open a support ticket with Atlassian. Let them take a look and see how they are calculating the number of fields. Please post back here with the resolution so future readers will know.
As a rule though, I would suggest staying away from Team-managed projects if you are going to use nearly 50 custom fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.