Custom Fields in Jira: A 6-Step Setup and Usage Checklist
Need Jira issues to capture the right details? Use this 6-step checklist to set up custom fields in Jira. Read now to build cleaner workflows.
A Jira issue can look complete while still missing the details your team needs to prioritize, report, or hand off work. Add too many fields, though, and every issue becomes slower to fill out. The result is often a cluttered screen, inconsistent answers, and reports nobody trusts.
Custom fields in Jira can capture information that standard fields don’t cover, such as a customer impact rating or a deployment window. The key is to plan each field before you create it. But here’s the truth: a useful field depends on more than its name. Its type, availability, placement, and purpose all matter. Use this six-step checklist to set up fields with care, keep issue screens manageable, and get information your team can actually use.
How to Set Up and Use Custom Fields in Jira: A 6-Step Checklist
Start with a clear question: what information is missing, and what decision will it support? Then work through these six steps before rolling out a field across your Jira projects.
-
Define the need. Identify the task, report, or handoff that currently lacks information. For example, a support team might need a “Customer impact” rating to sort urgent issues. If nobody will use the answer, the field probably isn’t necessary.
-
Choose a field type that fits the answer. Use a dropdown when people should select from a consistent set of options, such as Low, Medium, or High. Choose a date field for a planned release date. A free-text field can work for context, but it may produce answers that are difficult to compare.
-
Set the field’s scope and context. Decide which projects and issue types need the field. In Jira, configuration options depend on the project type and your permissions. A field intended for software bugs may not belong on every service request or business task.
-
Make the field available where people need it. Check the relevant issue screens or project settings, so the field appears during issue creation, editing, or viewing as appropriate. A field that exists but is hidden from the team won’t collect useful information.
-
Set rules for completion. Decide whether the field is optional or required, and at what point in the workflow an answer is needed. For instance, a “Release window” field may be optional while an issue is being investigated, then required before it moves to Ready for Release.
-
Test, then review usage. Create sample issues using different issue types and project workflows. Confirm that the field is visible, accepts the expected answer, and supports the intended report or filter. After launch, check whether people fill it in consistently.
Here’s why this order helps: you settle the purpose before adjusting settings. That reduces rework and makes it easier to explain the field to your team.

Plan the Field Before You Configure It
A good custom field answers a specific question that helps someone take action. “Customer impact” can help a support lead prioritize a queue. “Extra notes” is less clear because people may enter anything, or leave it blank.
Write down the field’s purpose, who will maintain it, and how its answer will be used. For example, if a delivery team wants to measure risk, agree on what Low, Medium, and High mean before creating a dropdown. Otherwise, two people may apply different ratings to similar work.
You might be wondering: should you create a field for every useful detail? Usually, no. If the information is already captured in an existing field, a comment, or another agreed process, another field can add effort without improving decisions.
Choose a Field Type and Scope That Match the Work
The field type shapes the quality of the answer. A dropdown helps people choose from consistent options, while a number field makes sense for a measurable value such as estimated hours. A text field offers flexibility, but it can be harder to group or compare later.
Think about the people who will enter the information. A team handling several request types might use a dropdown for “Request category,” then limit the field to the relevant project and issue types. That keeps unrelated teams from seeing options they don’t need.
In Jira, the available setup steps can differ between company-managed and team-managed projects. Check the project type and your administrator permissions before planning the configuration. If a field should apply in several places, confirm its context carefully to avoid showing it where it has no meaning.
Place Fields Carefully and Keep Screens Readable
Even a well-designed field can frustrate people if it appears at the wrong time. A field needed only during release preparation may not belong on the initial issue creation screen. Put it where the relevant person can answer it as part of their normal workflow.
For example, a product team may collect “Target release” when work is accepted for planning. A “Deployment confirmation” field may be more useful later, when the team prepares a change for release. The timing makes each answer more accurate.
The best part? A short field list can make issues easier to scan and quicker to complete. Review screens after adding fields, and remove or hide anything that distracts from the current task.
Use Field Values in Reports, Filters, and Workflow Decisions
A field earns its place when the information helps someone act. A “Customer impact” dropdown could help a support lead filter urgent work. A “Target release” date might help a project manager review upcoming commitments.
Before launch, confirm that the field can be used in the reports, filters, or workflow conditions you have in mind. A useful-looking field may not support every reporting need in the same way. Test with sample issues and check whether the results match the team’s question.
Let me explain with a practical example: a team creates a “Blocked reason” field to understand delays. If the team uses five consistent options, it can review recurring causes. If people enter free-form descriptions, someone may need to interpret and group those answers manually.
Review Field Quality as Your Jira Setup Changes
Projects change, and fields can outlive the process they were created to support. Schedule a periodic review to check whether each field still has a clear owner, appears in the right places, and produces answers people use.
Look for signs of trouble: a field is frequently blank, two fields collect nearly identical details, or the options no longer reflect the team’s work. Ask a few people who use the issue screens what feels unnecessary or confusing.
When a field is no longer needed, check its impact before removing or changing it. Existing issues, filters, reports, and workflow rules may rely on it. A careful review helps prevent a cleanup from disrupting everyday work.
Custom Fields in Jira: An ONES.com Solution

Value Proposition
ONES.com brings project management and knowledge management together in one platform, with AI support through ONES Assistant. ONES Project is a Jira alternative for teams that want configurable project workflows, reporting, and field management, with cloud and self-hosted deployment options.
Core Capabilities
Fields spread across project needs: Custom workflows and fields help teams capture details for different kinds of work. The result is more relevant issue information for each process.
Hard-to-follow work stages: Custom workflows let teams shape transitions around their actual approval or delivery steps. People can see what needs to happen next.
Limited visibility into progress: Built-in reporting helps teams review work and spot trends without relying on a collection of separate add-ons.
Sprint planning friction: Sprint management supports teams organizing iterative development work, so planning and execution sit within the project management environment.
Repeated manual actions: Automation can handle routine workflow actions and reduce repetitive updates for the team.
Existing Jira processes to preserve: Jira-compatible workflows can help teams carry familiar ways of working into a Jira alternative.
Separate project and knowledge practices: ONES.com includes ONES Project for project management and ONES Wiki for knowledge management. They are sold separately, so teams can select the product that fits their needs.
Deployment constraints: Choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment. The self-hosted version has feature parity with the cloud version.
Plugin overhead: Built-in capabilities can reduce reliance on plugins for common project management needs, depending on your team’s requirements.
Small-team evaluation: The free plan supports up to 30 seats, giving a team room to evaluate the platform before deciding on a wider rollout.
Application Scenarios
A software team replacing or reviewing its Jira setup can use ONES Project to configure issue workflows, sprint management, and custom fields around its delivery process. Built-in reporting can help the team review project progress in the same environment.
An organization with restricted network requirements can consider On-Premise, Private Cloud, or Air-gapped deployment. A team that also wants a knowledge management product can evaluate ONES Wiki separately from ONES Project.
Common Challenges With Custom Fields
Too many fields make issue entry tedious
Problem: People face a long form and may skip fields or enter rushed answers. Solution: Review the purpose of each field, remove duplication, and show fields only where they fit the task.
People interpret options differently
Problem: A dropdown has labels such as “Urgent” or “High,” but no shared definition. Solution: Explain each option in team guidance and use concrete examples to clarify when it applies.
A field is missing from the expected screen
Problem: The field was created, but teammates cannot see it during their normal workflow. Solution: Check project type, field context, screen or project settings, and access permissions. Test as someone with a typical team role.
Reports show incomplete or inconsistent answers
Problem: Fields are blank or filled inconsistently, so reports fail to answer the team’s question. Solution: Revisit when the field appears, whether it should be required, and whether the available options make sense.
FAQs About Jira Custom Fields
What are custom fields used for in Jira?
Custom fields capture issue details that standard fields don’t cover. A team might add “Customer impact,” “Target release,” or “Request category” to support prioritization, planning, or filtering. Each field should have a clear purpose and an intended audience. If the information won’t inform a decision, report, or handoff, consider whether the extra field is worth maintaining.
What types of custom fields can I add?
Available types depend on your Jira setup and configuration options. Common choices include text, numbers, dates, checkboxes, and dropdown-style selections. Choose a type based on the answer you need: a date for a release target, a number for a measurable value, or a dropdown for a consistent category. Test the selected type in the places where the team will use it.
Why can’t I see a custom field on an issue?
The field may not be available for that project or issue type, or it may not be placed on the relevant screen. Your permissions and project configuration can also affect what you can see or change. Check the project type and field settings, then confirm the field appears during the expected action, such as creating or editing an issue.
Should a Jira custom field be required?
Make a field required only when the answer is essential at a defined point in the workflow. For example, a release team might require a deployment window before approval, while leaving it optional during early investigation. If a field becomes mandatory too soon, people may enter guesses just to move an issue forward. Match the requirement to when someone can provide a reliable answer.
Can I remove a custom field after creating it?
Often, you can change or remove fields, subject to your permissions and Jira configuration. First check whether existing issues, filters, reports, screens, or workflow rules depend on the field. Removing it without that review can affect ongoing work or the way teams interpret past issues. If you’re unsure, test the change in a limited area before applying it more broadly.
Conclusion
Custom fields help your Jira team capture details that standard issue information doesn’t cover. Define the need, choose the right field type and scope, place it in the right workflow, and test its value before wider use.
Too few fields can leave a team without useful context; too many can slow down every issue. Review field usage as your process evolves, and keep only the fields that support clear decisions, dependable reports, or smoother handoffs.