How to Add a Field to a Project in Jira

Jira is the backbone of how most teams track work — but its real power only shows up when you shape it around your process, not the other way around.

Adding a custom field to a Jira project sounds simple. In practice, it trips up a lot of people because Jira’s field system is layered: you create a field globally, then connect it to a screen, then attach that screen to your project’s workflow. Miss one step and the field just doesn’t show up.

This guide walks you through every step — cleanly, in order — so you stop second-guessing the interface and start using Jira the way it was meant to be used.

Why Custom Fields Matter in Jira

Over 75,000 companies use Jira to manage their projects and workflows. Despite this adoption, research shows that less than 40% of teams fully customize their Jira instance beyond default settings — leaving a huge amount of efficiency on the table.

Custom fields let you capture data that Jira doesn’t track by default: lead source, priority tier, account size, campaign name, or any context your team needs to make smarter decisions inside an issue.

Teams that actively configure Jira report up to 30% faster issue resolution compared to teams using out-of-the-box settings, according to Atlassian’s own productivity data. That’s not a small number — that’s hours back in your week, every week.

What You Need Before You Start

Before adding a field, confirm you have the right access:

• Jira Administrator or Project Administrator permissions
• Access to Project Settings (if you’re using a company-managed project)
• Understanding of whether your project is team-managed or company-managed — the steps differ slightly between the two

If you’re on a team-managed project, you can add fields directly from the project settings without touching global configuration. Company-managed projects require going through Jira’s global admin panel first.

How to Add a Field to a Company-Managed Project in Jira

Company-managed projects give you the most control, but they also have more layers. Here’s the full process.

Step 1 — Create the Custom Field (Global Level)

1. Go to Jira Settings (the gear icon in the top-right corner)
2. Click Issues
3. Under the Fields section, select Custom Fields
4. Click Create custom field in the top-right
5. Choose your field type — text, number, date, dropdown, user picker, etc.
6. Give it a name and description, then click Create

At this point, the field exists globally in your Jira instance. It’s not yet attached to any project or screen.

Step 2 — Add the Field to a Screen

Screens control what fields appear when you create, view, or edit an issue. A field only shows up if it’s on the right screen.

1. Go back to Jira Settings → Issues → Screens
2. Find the screen used by your project (typically named after your project or workflow)
3. Click the screen name to open it
4. Scroll to the bottom and use the Add Field dropdown to find and add your custom field
5. Click Update

If you’re not sure which screen your project uses, go to Settings → Issues → Screen Schemes to find the mapping.

Step 3 — Connect the Screen Scheme to Your Project

1. Go to Jira Settings → Issues → Screen Schemes
2. Find the scheme associated with your project’s issue type screen scheme
3. Confirm your screen is linked to the correct issue operations (Create, Edit, View)

If your project uses a dedicated screen scheme, the field will now appear on new and existing issues.

Step 4 — Verify the Field Appears in Your Project

1. Open your project
2. Create a new issue or open an existing one
3. The custom field should now appear in the Create Issue form or the issue detail panel

If it doesn’t show up, double-check the screen-to-project mapping under Screen Schemes and Issue Type Screen Schemes.

How to Add a Field to a Team-Managed Project in Jira

Team-managed projects (formerly “next-gen” projects) are simpler. You don’t need admin access to the global Jira settings.

1. Open your team-managed project
2. Click Project Settings in the left sidebar
3. Select Issue types
4. Click the issue type you want to add the field to (e.g., Task, Bug, Story)
5. In the right panel, scroll to Context fields or More fields
6. Drag the field you want into the active fields area — or click + Add a field to create a new one
7. Save your changes

That’s it. The field is immediately active for that issue type in your project.

Field Types Available in Jira

Choosing the right field type matters. Here’s a quick reference:

Text fields — Free-form input, great for notes, URLs, or descriptions.

Number fields — For tracking quantities, scores, deal sizes, or numeric metrics.

Date and date/time fields — Deadlines, launch dates, follow-up reminders.

Dropdown (Select list) — Single-choice options. Use when the answer is always one of a fixed set of values.

Multi-select list — Multiple choices from a defined list. Good for tags or categories.

User picker — Assigns a Jira user to a field. Useful for accountability or routing.

Checkboxes — Yes/no or multi-option boolean fields.

URL fields — Captures links directly inside an issue.

Atlassian’s data shows that dropdown and text fields account for over 60% of all custom fields created across Jira instances globally — they’re the most versatile and easiest for teams to adopt quickly.

Common Reasons a Field Isn’t Showing Up

Even after following every step, fields sometimes don’t appear. These are the most common causes:

The field isn’t on the right screen. Jira uses separate screens for Create, Edit, and View operations. A field on the Edit screen won’t show on the Create screen. Check all three.

The screen isn’t connected to the project’s screen scheme. Go to Issue Type Screen Schemes and confirm the link exists.

The field is hidden by a field configuration. Field configurations control whether a field is hidden, optional, or required. Check under Settings → Issues → Field Configurations.

You’re looking at the wrong issue type. If your project has multiple issue types (Epic, Story, Task, Bug), each can have different field setups. Confirm you’re editing the right one.

Permissions issue. If you’re a project admin but not a Jira admin, you may not have access to global field settings. Contact your Jira administrator.

How to Make a Custom Field Required

Making a field required ensures data quality — your team can’t close or create an issue without filling it in.

1. Go to Jira Settings → Issues → Field Configurations
2. Find the field configuration used by your project
3. Locate your custom field in the list
4. Click Required next to the field name

This is especially valuable for fields that feed into reporting or automation — bad data in means bad reporting out.

Using Custom Fields in Jira Filters and Reports

Once your field is live, you can use it across Jira’s built-in tools:

Filters: In the Jira issue navigator, use JQL (Jira Query Language) to filter issues by your custom field. For example: cf[10001] = “Enterprise” pulls all issues where that field equals “Enterprise.”

Dashboards: Add gadgets that group or count issues by custom field values.

Reports: In company-managed projects, some report types let you filter or segment by custom fields.

Automation: Jira’s built-in automation rules can trigger actions based on custom field values — like auto-assigning issues when a certain dropdown option is selected.

Teams using JQL with custom fields report saving an average of 2–4 hours per week in manual issue tracking and reporting, according to Atlassian community surveys.

Bulk-Editing Custom Fields Across Existing Issues

Adding a field to your project doesn’t automatically populate it on old issues. If you need to update existing issues in bulk:

1. Run a filter to find all affected issues
2. Select all from the issue list view
3. Click Tools → Bulk Change → Edit Issues
4. Find your custom field in the list
5. Set the value and apply

This works for most standard field types. Some complex field types may require manual editing or an automation rule.

Best Practices for Managing Jira Custom Fields

Custom fields are powerful, but they can also create clutter fast. Research from Atlassian partners shows that organizations with more than 200 custom fields experience significantly slower Jira performance and higher admin overhead.

Keep your field setup clean by following these habits:

Name fields consistently. Use a naming convention your whole team recognizes. Avoid abbreviations that only make sense to one department.

Audit fields quarterly. Delete or archive fields that haven’t been used in 90 days. Jira doesn’t automatically clean these up.

Limit who can create global fields. In large teams, uncontrolled field creation leads to duplicates and confusion. Restrict global field creation to Jira admins.

Document your field logic. Keep a shared record of what each custom field is for, who requested it, and which projects use it. This saves hours when onboarding new team members.

Use field contexts strategically. Jira lets you create field contexts that apply different options or behaviors to the same field based on project or issue type. Use this instead of creating duplicate fields.

How Jira Custom Fields Connect to Your Sales and Outreach Process

If your team uses Jira to track deals, campaigns, outreach tasks, or client work, custom fields are what turn Jira from a generic task board into a revenue-tracking system.

Fields like Lead Source, Decision-Maker Name, Company Size, Last Contact Date, and Next Action can transform a Jira board into a lightweight CRM-style tracker — especially for teams that live in Jira and don’t want to context-switch to another platform.

The caveat: Jira is built for project execution, not lead generation. It won’t find your next customer, qualify them, or get them on a call. That part still requires a dedicated outbound system.

Conclusion

Adding a field to a Jira project is a multi-step process — but once you understand the logic of fields, screens, and screen schemes, it becomes straightforward to repeat.

The fastest path: create the field globally, attach it to the right screen, confirm the screen is connected to your project’s scheme, and verify it shows up on the issue types you care about. For team-managed projects, it’s even simpler — drag, drop, save.

Custom fields are how you make Jira match your workflow instead of forcing your workflow to match Jira. Used well, they improve reporting accuracy, speed up issue triage, and give your team the context they need to move faster.

If your Jira board is tracking outreach, client work, or sales activity — and you want leads actually flowing into that board — that’s where SalesSo comes in. We run the full outbound engine: targeting, messaging, campaign management, and meeting booking. Book a strategy meeting and see what a full pipeline looks like.