JIRA Custom Fields
JIRA ships with fields such as Summary, Description, Assignee, and Priority. Real teams need more details. A support team wants a Customer Name. A testing team wants a Browser Version. A finance team wants a Budget Code. Custom fields add these extra details to issues.
Layman's View: A Hospital Form
A hospital registration form asks for name, age, and address. A children's ward adds a line for the parent's phone number. The extra line is a custom field. The form stays the same for everyone else.
Common Field Types
Popular Custom Field Types
| Field Type | What It Stores | Example |
|---|---|---|
| Text Field (single line) | A short piece of text | Customer Name |
| Text Field (multi-line) | A longer paragraph | Steps to Reproduce |
| Number Field | A numeric value | Estimated Cost |
| Date Picker | A calendar date | Customer Deadline |
| Select List (single choice) | One option from a list | Customer Tier: Gold, Silver, Bronze |
| Select List (multiple choice) | Several options from a list | Affected Browsers |
| Checkboxes | Tick one or many items | Test Types Completed |
| User Picker | One JIRA user | Business Owner |
| URL Field | A web link | Design File Link |
How a Field Reaches an Issue
A new field does not appear on issues automatically. JIRA connects three pieces: the field, a screen, and a context. The screen decides which form shows the field. The context decides which projects and issue types use it.
[ Field: Browser ]
|
| added to
v
[ Screen: Create Bug ]
|
| used by
v
[ Issue Type: Bug in Project WEB ]
|
v
Field shows on the Create Bug form
Steps to Create a Custom Field
- Open the administration settings and go to the Issues section.
- Select Custom Fields and choose the option to create a new field.
- Pick a field type from the list.
- Type a clear name and a short description.
- Select the screens where the field should appear.
- Save the field.
Company-managed projects need a JIRA administrator for these steps. Team-managed projects let project admins add fields inside project settings. Menu labels change slightly between JIRA versions.
Field Context
A context sets where a field applies and which default value it carries. One field can hold different defaults in different projects.
Context Example for the Customer Tier Field
| Context | Project | Default Value |
|---|---|---|
| Support Context | SUP | Standard |
| Sales Context | SALES | Prospect |
Field Configuration
Field configuration controls the behavior of each field. Administrators mark a field as required, hide it, or add help text. A required field blocks issue creation until someone fills it in.
Searching with Custom Fields
Custom fields work inside JQL searches. Quotes around the field name handle spaces.
"Customer Tier" = Gold AND status != Done
Select lists give cleaner searches than free text. A list holds the value Gold every time. A text field may hold gold, GOLD, or Gld.
Planning Tips
- Choose clear names. "Browser" and "Browser Type" confuse users when both exist.
- Prefer select lists over free text for values used in reports.
- Keep the number of fields low. Long forms slow people down and invite empty answers.
- Write a description for every field so new users know what to enter.
- Review unused fields every few months and remove the ones nobody touches.
Real-World Example
A support team handles requests from paying customers and free users. The administrator adds a select list called Customer Tier with the values Gold, Silver, and Free. The team builds a filter for Gold issues and watches that list first each morning. Response times for premium customers improve because the field makes priority visible at a glance.
Summary
Custom fields capture details that default fields miss. Each field needs a type, a screen, and a context. Select lists keep data clean, and short forms keep people productive. Careful naming and regular cleanup keep the system tidy as it grows.