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; } } }

Create custom fields in JSM portal

Gemma Huang

Previously I raised CES-196833 Custom fields limit on team-managed JSM portal. Below is my question and the answer I received.

Q: What is the actual custom field limit applicable to our project type? Asia ITCG Portal is a team-managed service space.
→ For Jira Service Management (JSM) and other Jira Cloud products, the custom field limit for team-managed projects (referred to as "spaces" in some documentation) is 700 fields per project.

I believed my question had been resolved until I received the following message while trying to create new custom fields in my JSM space, Asia ITCG Portal. It still indicates that there is a limit of 50 custom fields, which is preventing me from creating any additional fields. Could you please advise how we can address this issue?

Accepted answers

Matthew Sinclair

The 700 Field limit applies only to "Company Managed" Spaces - as they are a global resource.

In a "Team Managed" Space - you are limited to 50 custom fields.

https://support.atlassian.com/jira-software-cloud/docs/available-custom-fields-for-team-managed-projects/

You cannot bypass this or override it.

Atlassian likely will not be changing this limit in the near future considering the latest changes and heavy push to future considerations (In that this year they've been clamping down on limits aggressively).

Personally I tend to avoid Team Managed platforms like the plague in my org - you could try using JSM Forms to store the additional information as generally speaking folks who track so much info are not going to be querying the information.

I would strongly encourage you to consolidate and simplify your configuration if at all possible.

That or you can move into a Company Managed Space (Note I said Move - not Migrate - not Convert - yeah - its bad - there's no seamless/painless process to do this).

All comments

Matthew Sinclair

The 700 Field limit applies only to "Company Managed" Spaces - as they are a global resource.

In a "Team Managed" Space - you are limited to 50 custom fields.

https://support.atlassian.com/jira-software-cloud/docs/available-custom-fields-for-team-managed-projects/

You cannot bypass this or override it.

I would strongly encourage you to consolidate and simplify your configuration if at all possible.

That or you can move into a Company Managed Space (Note I said Move - not Migrate - not Convert - yeah - its bad - there's no seamless/painless process to do this).

Olha Yevdokymova_SaaSJet

Hi! It looks like there may have been some confusion in the previous response between different Jira field limits.

For a team-managed JSM space, the 50 custom field limit can still become a real constraint. If you’ve reached it, there are a few ways to handle this:

1. Reuse global custom fields.
Team-managed spaces can use globally defined Jira fields, and these don’t count toward the 50-field limit. A Jira admin can create or reuse a global field and add a context that includes your space.

2. Audit and consolidate existing fields.
Check whether some fields overlap, are rarely used, or could be combined. Not every piece of information collected from a requester necessarily needs its own Jira custom field.

3. Use Smart Forms for the detailed intake.
If the main reason you need more fields is to collect additional information from users, Smart Forms developed by my team, can help separate what you ask the user from how the data is stored in Jira.

For example, a form can ask a user-friendly question like:

“What are you having a problem with?”

while mapping the answer to an internal Jira field such as Product area.

The form field and Jira field don’t need to have the same name or wording. This lets you design the form around the requester’s experience while keeping Jira fields structured around how your team works internally.

You can also keep fields completely form-only. Their values remain available in the Smart Forms response on the work item, but they don’t need to consume Jira custom-field slots.

Another useful option is consolidating several answers into one Jira field. For example, instead of creating separate Jira fields for:

Device
Browser
Steps to reproduce
Error message
Additional context

you can collect them as separate, structured questions in the form and map the relevant information into a single Jira field such as Description.

So the requester gets a much clearer form, while the Jira issue doesn’t need five additional custom fields.

I’d generally split fields into two groups:

Needed for filters, queues, SLAs, reporting or automation → map to Jira fields
Needed mainly to understand the request → keep as Smart Forms fields

This way, you can potentially collect dozens of pieces of information without creating dozens of Jira custom fields.

4. Consider a company-managed space if the project will keep growing.
If you genuinely need more than 50 Jira fields for reporting, automation, queues, and other Jira functionality, moving to a company-managed setup may still be worth considering.

But if most of those fields exist simply because you need to ask users more questions, I’d first look at moving that intake layer into Smart Forms rather than restructuring the whole service space.

Ismail Bin Ibrahim

Hi @Gemma Huang

The 700-field limit does not apply to project-specific custom fields in team-managed projects. According to Atlassian's documentation, a team-managed Jira Service Management project can create up to 50 project-specific custom fields.

If you're receiving a message that you've reached the 50-field limit, the project is behaving as expected. To add more fields, consider:

Removing unused project-specific custom fields, or
Reusing existing global custom fields, which Atlassian now supports in team-managed projects.

So, the current limitation you're encountering is the documented 50 project-specific custom field limit, not 700.

Regards,

Ismail.

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-management