Jira Fields Explained: A 2026 Guide to Types and Setup with Examples
Are Jira fields cluttering your tickets? Explore field types and setup examples in this 2026 guide—read now to build cleaner workflows.
Misconfigured Jira fields can make a simple task feel like paperwork. People see irrelevant questions, skip important details, or enter the same information in several places.
Over time, those small problems can leave teams with inconsistent tickets and reports they cannot trust. Adding more fields may seem like the fix, but unnecessary fields often make work harder.
But here's the truth: Jira fields work best when each one has a clear purpose, appears at the right point in a workflow, and captures information your team will actually use. This guide explains Jira field types, shows how to set them up, and walks through practical examples. You’ll also learn how to avoid common configuration problems and keep issue screens useful as your processes change.
What Jira Fields Are and How They Work
Jira fields are the individual pieces of information attached to an issue, such as its summary, status, assignee, priority, or due date. They help teams describe, sort, assign, and report on work.
A Jira issue is like a structured work card. Its fields are the labeled details on that card: “Summary” names the task, “Assignee” identifies who owns it, and “Priority” indicates how urgently it needs attention.

Standard fields and custom fields
Standard fields come with Jira and support common project needs. Examples include Summary, Description, Issue Type, Status, Reporter, Assignee, Priority, Labels, and Due Date.
Custom fields let you capture information that standard fields don’t cover. A support team might add “Customer impact,” while a product team might track “Target release.”
Here’s why: a field can exist in Jira without appearing on every issue screen. Its visibility depends on how administrators connect fields to screens, projects, issue types, and field contexts.
Fields, issue types, and screens are different things
An issue type describes the kind of work, such as a Bug, Task, Story, or Epic. A field stores a particular detail about that work. A screen controls which fields people see when they create, edit, or view an issue.
For example, a Bug might use the same Summary field as a Story but show extra fields for “Steps to reproduce” and “Affected version.” That difference comes from configuration, not from the basic definition of a field.
Common Jira Field Types, With Examples
Choose a field type that matches the answer you need. If a team needs a single launch date, a date field is clearer than a free-text field where people might enter “next Friday,” “June 5,” or “after review.”
| Field type | What it captures | Example use |
| Text | A short value or longer written response | Short text for a product area; paragraph text for reproduction steps |
| Number | A numeric value | Estimated units, number of affected customers, or a score |
| Date or date and time | A calendar date, or a date with a specific time | Target release date or scheduled maintenance window |
| Single-select list | One choice from a controlled set | Impact level: Low, Medium, or High |
| Multi-select list | Several choices from a controlled set | Platforms affected: Web, iOS, and Android |
| Checkboxes | One or more simple selections | Applicable regions or supported environments |
| User picker | A Jira account or group of accounts | Reviewer, service owner, or escalation contact |
| URL | A web address | Link to a design prototype or monitoring page |
| Labels | Flexible tags for grouping and filtering | Tags such as “accessibility” or “migration” |
Pick structured choices when reporting matters
If you want to compare or filter responses, use a field with defined choices. A single-select “Request type” field produces more consistent results than asking everyone to type their own description.
For example, a team that uses “Bug,” “Defect,” “Issue,” and “Error” interchangeably will have a harder time grouping work. A single-select list gives everyone the same options and makes reports easier to interpret.
Use free text when the answer needs detail
Text fields suit explanations that cannot be reduced to a short menu. “Steps to reproduce” is a good example because each issue may require a different sequence of actions.
But here's the tradeoff: free text can be difficult to compare. If you need both a written explanation and a consistent category, use separate fields for the category and the supporting detail.
How Jira Fields Connect to Projects and Workflows
A field’s configuration determines where it appears and how people can use it. In Jira, administrators commonly manage this through screens, field configurations, field configuration schemes, and custom field contexts.
Screens control what people see
Jira screens define the fields shown during actions such as creating, editing, or viewing an issue. A create screen can ask for essential details, while an edit screen can expose additional information later.
For example, a service request form might show Summary, Description, Impact, and Request type. A developer’s edit screen might also include Fix Version and Technical notes.
Field configurations control field behavior
A field configuration can set a field as required, hidden, or optional. It may also control how a field behaves in a particular project or issue setup.
Make a field required only when people have the information at the moment Jira asks for it. If an engineer cannot know the affected release during initial triage, requiring that answer at issue creation can encourage guesses.
Contexts limit where custom fields apply
A custom field context can restrict the projects and issue types where a field is available. This helps prevent a field created for one team from appearing across unrelated work.
Imagine a “Browser version” field used by a web support team. Limiting its context to that team’s project and relevant issue types keeps it out of a facilities request form.
Workflow rules can make fields matter at the right moment
A workflow describes how an issue moves through statuses and actions. Jira administrators can configure screens and rules around workflow transitions, so a field can be requested when the information becomes useful.
For instance, a release team might ask for a “Deployment window” when work moves to Ready for release. That timing is more practical than asking for the window when someone first reports a bug.
How to Set Up Jira Fields Step by Step
Start with the work your team needs to manage, then configure only the fields that support it. The exact menu names may differ between Jira plans or interface updates, but the setup decisions remain similar.
- Identify the question the field must answer. Write down the decision, handoff, or report the field should support. For example, define whether “Customer impact” helps triage a request or measure its effect.
- Check for an existing field. Search Jira’s available fields before creating a custom one. A standard field or an existing team field may already meet the need.
- Choose a suitable field type. Use a date field for dates, a number field for numeric values, and a select list when people should choose from consistent options.
- Give the field a clear name and guidance. Prefer “Affected platform” over “Platform info.” Add a short description or helper text when people might interpret the question differently.
- Set its context. Limit the field to the projects and issue types that need it. This avoids showing irrelevant questions to other teams.
- Add it to the right screens. Decide whether it belongs on create, edit, view, or transition screens. Keep the initial issue form focused on information people can provide immediately.
- Set required behavior carefully. Test whether people can answer the question accurately at each stage. Make the field mandatory only where the answer is genuinely needed.
- Test with representative issues. Create and edit examples for each relevant issue type. Check field visibility, option choices, permissions, and reporting behavior.
- Tell the team what changed. Explain what the field means, when to fill it in, and who maintains its options. A brief example can prevent inconsistent entries.
Example: adding a customer-impact field
Suppose a support team needs to rank incoming bugs. It creates a single-select field called “Customer impact” with Low, Medium, and High options.
The team limits the field to its support project and Bug issue type. It adds the field to the create screen, keeps it optional during initial reporting, and asks the triage owner to complete it before prioritization.
The result is a field with a defined purpose, controlled choices, and a clear point of use. The team can now filter high-impact bugs without trying to interpret different phrases in long descriptions.
Field Design Practices That Keep Jira Manageable
Good field design makes it easy to capture information and useful to retrieve it later. The best test is practical: can a teammate understand the field, answer it consistently, and use the answer to make a decision?
Use the smallest useful set
Every additional field asks for attention and may need ongoing maintenance. Before creating one, ask whether the information can be captured with an existing field, a workflow status, or a short description.
For example, if a team only needs to know whether testing has started, a workflow status may communicate that more clearly than a separate “Testing started?” checkbox.
Write labels that make the question obvious
Field names should make sense without an explanation from the person who created them. “Target release date” is clearer than “Target,” and “Customer impact” is more specific than “Impact” when several kinds of impact are discussed.
Use descriptions to clarify boundaries. For a “Severity” field, guidance might explain that it measures functional effect rather than urgency, if that matches your team’s process.
Keep choice lists consistent and maintained
Long choice lists become difficult to scan and may collect outdated options. Review them periodically, remove choices that no longer apply, and agree on naming before adding a near-duplicate.
For instance, keep “Mobile app” as one option rather than adding “Mobile,” “Phone app,” and “iOS or Android” without a clear reason.
Separate fields when they answer different questions
A single field should not combine unrelated details. If “Environment and release” asks for both where a bug happened and which version was affected, split it into focused fields when the team needs to filter those answers separately.
That small design choice can improve reporting. Someone looking for bugs in a particular version can filter the release field without searching through mixed notes.
Review usage, not just configuration
A field can be configured correctly and still be ignored. Check whether people fill it in, whether answers are consistent, and whether a report or decision actually uses it.
If a field stays blank or provides no useful distinction, ask the team why before adding more rules. You might need better guidance, a later point in the workflow, or no field at all.
Jira Field Examples for Common Team Needs
The right setup depends on what your team does. These examples show how the same field choices can support different workflows without adding questions to every issue.
Product development team
A product team could use standard fields such as Issue Type, Priority, Assignee, and Fix Version. It might add “Product area” as a single-select field to route work among teams.
Stories and Bugs may need different screens. A Story could ask for acceptance criteria, while a Bug could ask for reproduction steps and affected platform. Keeping those questions specific makes issue creation easier.
IT service desk
A service desk could use “Request type” to classify work, “Impact” to indicate how many people are affected, and “Urgency” to describe how quickly action is needed. Those separate answers can support triage more clearly than one broad priority field.
It might also use a user picker for “Requested for” when an employee submits a request on someone else’s behalf. A context can keep that field limited to the relevant request types.
Marketing or operations team
A marketing team could track “Campaign,” “Channel,” and “Launch date” on work items. Use a select list for the channel if consistent reporting matters, and a date field for scheduling.
For example, a campaign task might use Email as its channel and September 12 as its launch date. That is easier to filter than a description that says, “Newsletter planned around mid-September.”
Jira Field Challenges and Practical Fixes
Field problems often show up as confusing forms, inconsistent answers, or missing report details. Here are common issues and ways to address them without making the configuration more complicated than necessary.
- Problem: People see fields that do not apply. Review the screens and custom field contexts. Limit fields to the projects and issue types that need them, then test a few unrelated issue types.
- Problem: A required field blocks issue creation. Check whether the question can be answered at that stage. Make it optional at creation or request it later in the workflow when the information is available.
- Problem: Similar fields collect overlapping answers. Compare their purpose and ownership with the teams using them. Keep the field that supports a real decision, then update forms and guidance to reduce duplicate entry.
- Problem: Reports contain inconsistent categories. Replace open-ended entries with a controlled choice field if the team needs reliable grouping. Agree on option names and review them as the process changes.
- Problem: No one knows who maintains a field. Assign an administrator or process owner to review its description, choices, context, and usage. A named owner makes cleanup more likely when the team’s needs change.
Jira-Style Field Management with ONES.com
ONES.com brings project management and knowledge management together on one platform. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge management product and a Confluence alternative. They are sold separately, so a team can choose the product that fits its needs.

Value proposition
If your team wants structured work tracking without treating every process as a Jira configuration problem, ONES Project offers custom fields and workflows alongside project management features. Its deployment choices also include self-hosted options for organizations with specific hosting requirements.
Core capabilities: common field-management pains and responses
- Pain: The team needs fields that reflect its process. ONES Project supports custom fields and custom workflows. Teams can shape issue details and work stages around how they plan and deliver work.
- Pain: Different teams need different steps. Custom workflows let a team define stages for its work. This can make a process clearer when one generic status flow does not fit every project.
- Pain: Teams want familiar Jira-style processes. ONES Project supports Jira-compatible workflows. That can help teams carry familiar workflow patterns into a Jira alternative.
- Pain: Sprint work needs a clear cadence. Sprint management supports teams organizing and tracking iterative work. This is useful for groups that plan tasks in regular delivery cycles.
- Pain: Teams need visibility into progress. Built-in reporting helps teams review project work without relying only on manually assembled status updates.
- Pain: Repeated actions take time. Automation can handle configured recurring actions, helping reduce manual steps in project workflows.
- Pain: Plugin dependence complicates administration. Native capabilities can reduce the need for plugins when the required functionality is already included. That can simplify maintenance for teams with matching needs.
- Pain: Hosting requirements limit options. ONES.com is available in Cloud, On-Premise, Private Cloud, and Air-gapped deployments. The cloud and self-hosted versions have full feature parity.
Application scenarios
A product team moving from Jira: A team can explore ONES Project as a Jira alternative, adapting its project structure with custom fields and workflows. Jira-compatible workflows may help the team preserve familiar ways of organizing work while evaluating its new setup.
An organization with restricted network requirements: A team that needs an air-gapped or other self-hosted deployment can consider ONES Project’s deployment options. Full feature parity between cloud and self-hosted versions means the team does not have to choose a reduced-feature edition solely to meet its hosting needs.
A small team trying project management: The free plan supports up to 30 seats. Teams can assess whether its project management capabilities fit their work before deciding whether a different plan or deployment suits their requirements.
FAQs About Jira Fields
What is the difference between a Jira field and an issue type?
An issue type identifies the kind of work, such as a Bug, Story, or Task. A field stores a detail about an issue, such as its Summary, Priority, or Affected platform. The same field can appear on several issue types, while each type can have a different set of fields on its screens.
Can I make a Jira field required for one issue type only?
Often, yes, when the project’s field configurations, screens, and issue setup support that distinction. You may need a separate field configuration or scheme, depending on your Jira setup. Test the behavior on each relevant issue type so the requirement does not unexpectedly apply to other work.
Why can’t I see a field on an issue?
The field might not be added to the screen you are using, or its context may exclude the project or issue type. Permissions and field configuration can also affect what appears. Check the relevant screen, context, and configuration, then test the issue using the same action and project where the field is missing.
When should I use a custom field instead of a standard field?
Use a standard field when it already captures the information your team needs. Create a custom field when the information is specific to your process and cannot be represented well by an existing field. For example, use Priority for work urgency, but consider a custom “Customer impact” field if you need a separate measure.
How many custom fields should a Jira project have?
There is no ideal number for every project. Keep fields that support decisions, handoffs, filtering, or reporting, and remove or retire fields that no longer serve a clear purpose. A short create screen can make reporting more useful because people are more likely to complete focused, relevant questions consistently.
Conclusion: Make Every Field Earn Its Place
Jira fields help teams describe work in a consistent way, but their value depends on thoughtful setup. Choose a suitable field type, place it where people need it, and make its purpose easy to understand.
Start with the decisions your team needs to make. Test fields with real issue examples, keep irrelevant questions off screens, and review whether each field still helps the team work or report more effectively.
When field configuration creates unnecessary friction, revisit the process before adding more fields. A focused setup—whether in Jira or a Jira alternative such as ONES Project—can make issue tracking clearer and easier to maintain.