As a Jira administrator, open the admin panel, select Work items, then Fields in the Fields section, and choose Create new field. Pick the field type, which you can't change later, add a name and description, add options if needed, then select Create. Finally, add the field to a field configuration so it appears where your team works.
Decide three things before you click
Creating the field takes a minute. Getting it right takes a little thought first, because one choice is permanent.
- The type. You can't change the field type once the field exists, so decide whether it's text, a number, a date or a list of options.
- The name. It shows on work items across your whole site, so Atlassian advises a clear name. Client name beats CN.
- Who it's for. Creating a field that can be used in any space needs Jira administrator permission. Fields in team-managed spaces are created differently, and that route isn't covered here.
A quick example of picking the type
Say you want to record each client's service tier. A free-text field lets people type Gold, gold and GOLD, and your filters break. A field with predefined options, set to Bronze, Silver and Gold, keeps every entry consistent and makes reports work. As a rule of thumb, if there's a fixed list of answers, choose a type with options. If every answer's different, such as a contract reference, choose text.
Creating the field
- Open the Jira admin panel from the icon in the top navigation and select Work items.
- In the Fields section, select Fields, then Create new field.
- Choose the field type.
- Enter a name and a description. The description appears in the Fields table, which helps with sorting later.
- If the field has predefined options, add the choices users can pick from.
- Select Create, then add the field to a field configuration.
Why your new field isn't showing yet
This is the question that comes up most. Selecting Create makes the field exist, but it doesn't put it in front of anyone. You still have to add it to a field configuration. Until you do, nobody sees it on their work items, and it looks as if the field was never made.
The 700-field ceiling per space
Atlassian Support's Data limits and guardrails page sets out a limit that's easy to miss. Jira enforces a cap of 700 fields per space, counted through the field configuration schemes associated with that space. There's no limit on the total number of custom fields across the site, though, so the cap is about how many fields a single space carries.
| Rule | Detail |
|---|---|
| Fields per space | 700, counted through field configuration schemes |
| Custom fields across the site | No limit |
| Trashed fields | Don't count towards the 700 |
| At the limit | Admins can't associate more fields with that space |
| Existing setup at the limit | Keeps working |
| Changing the limit | Not possible in Jira settings |
If a space reaches the limit, Jira stops an admin from associating more fields with it until usage comes down, but everything already configured keeps working. Admins can view and reduce usage, but they can't change the limit values themselves.
Keeping field counts under control
For a small team, 700 fields sounds like a lot. In practice, spaces pick up fields over years as different people add one-off fields for one-off jobs. A few habits help:
- Search the Fields table before you create a new field. Someone may already have made Client name.
- Write a useful description every time, so the next admin knows what the field's for.
- Trash fields nobody uses, since trashed fields don't count towards the limit.
Custom fields in another work tool
Asana has API calls to create, update and delete a custom field and to create enum options, which suits teams that manage fields through code. If you're weighing tools more broadly, my guide to the best project management software is a useful starting point.
My advice for your first custom field
Choose the type with care, because it's permanent, and give the field a name anyone on the site would understand. Add it to a field configuration straight after you create it, then open a work item to check it's there. If Jira feels heavier than your team needs, my roundup of Jira alternatives covers simpler options.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Who can create a custom field in Jira?
A Jira administrator, for fields that can be used in any space.
Can I change the field type later?
No. Atlassian says you can't change it once the field is created.
Is there a limit on custom fields?
Yes, 700 fields per space, but there's no limit on the site total.
Why isn't my new field showing?
Add it to a field configuration.
Do trashed fields count?
No. They don't count towards the 700 limit.
