How to create custom fields and formula fields in Jira
You can create a custom field in Jira in about five minutes, no code required. If your team is tracking budgets in a spreadsheet or manually calculating priority scores, you can move that work into Jira in about five minutes.
Custom fields capture the data; formula fields do the math.
How to create a custom field in Jira
You create every custom field the same way, then choose its type. A Jira admin creates and manages custom fields, and the same flow is the foundation for both a standard custom field and a formula field.
Choosing a field type to add to a Jira space.
Open field scheme settings. Go to Jira settings, then Work items, then Fields, then Field schemes.
Create a new field. Select Create custom field.
Choose the field type. Pick the type that matches the data and what you will do with it: text, number, date, a choice field, people, or formula.
Name the field for what it holds. A clear name like "Customer tier" or "Approved budget" tells anyone reading the work item what the value means.
Choose which projects and work types use it. Add the field to the right field scheme, then choose where it appears on the work item view. New custom fields do not appear everywhere by default, so add them only where teams need them.
Worked example: a "Customer tier" field
Say your support team wants to sort tickets by account value. Create a custom field, choose Select list (single choice), name it "Customer tier," and add the options Enterprise, Mid-market, and Small business. Add it to your support projects, and you can now filter and group every ticket by tier.
A note on project types
In company-managed projects, a Jira admin creates custom fields centrally and shares them across projects. In team-managed projects, project admins add fields within their own project settings. If you need the same field to behave identically across many teams, a company-managed, shared custom field keeps it consistent.
Field schemes, screens, and contexts do different jobs.
Field schemes control which fields are available for each work type across assigned projects, including whether a field is required or optional. Screens control placement and order in create, view, and edit experiences. Field contexts control default values and dropdown options for specific projects and work types.
How to create a formula field in Jira
A formula field starts as a custom field, then adds the calculation. Your admin may need to enable formula fields first, after which anyone who can create custom fields can build one. The steps below take you from an empty field to a live calculated value.
Create a custom field and choose the formula type. Follow the steps above, and select the formula field type.
Name it for the value it produces. Names like "Budget variance" or "Days until deadline" make the result self-explanatory.
Write the formula. Reference other fields by name inside braces and combine them with operators. For example, {Approved Budget} - {Actual Costs} returns budget variance. If you are not sure of the syntax, describe the calculation in plain language and let Rovo draft it.
Set the output type. Choose number, text, date, or duration so the result displays and sorts correctly. Number results can be formatted as currency, percentage, or decimal.
Apply it through a field scheme, then add it to screens. Choose the projects that use the field, then add it to the work item view.
Store any value you want to calculate on as a number, date, or duration field, not as text. Formula fields can only do math on fields that hold the right data type.
Formula field examples by role
The same field type solves different problems depending on who is using it. Each role below includes three formulas you can adapt by swapping in your own field names. All examples are drawn from real starter formulas.
Finance manager
Move budget tracking out of spreadsheets so every actual is measured against the forecast in real time.
Use case | Formula | Output type |
Budget variance | {Approved Budget} - {Actual Costs} | Number (currency) |
Burn rate percent | ({Actual Costs} / {Approved Budget}) * 100 | Number (percent) |
Overspend alert | IF({Actual Costs} > {Approved Budget}, "Over budget", "On track") | Text |
Marketing campaign manager
See campaign performance and budget health on the board instead of a separate ROI tracker.
Use case | Formula | Output type |
Campaign ROI | ({Revenue} - {Campaign Cost}) / {Campaign Cost} | Number (percent) |
Cost per lead | {Campaign Cost} / {Leads Generated} | Number (currency) |
Product manager
Automate prioritization frameworks so the backlog sorts itself by highest impact.
Use case | Formula | Output type |
RICE score | ({Reach} * {Impact} * {Confidence}) / {Effort} | Number |
Value-to-effort ratio | {Business Value} / {Story Points} | Number |
Priority banding | IF({RICE} > 100, "P0", IF({RICE} > 50, "P1", "P2")) | Text |
Project manager
Stay ahead of risk by calculating time to deadline and flagging items falling behind.
Use case | Formula | Output type |
Engineering lead
See remaining effort and scope changes without chasing developers for status.
Use case | Formula | Output type |
Remaining effort | {Original Estimate} - {Time Spent} | Duration |
Scope creep percent | (({Current Estimate} - {Original Estimate}) / {Original Estimate}) * 100 | Number (percent) |
Sprint progress percent | ({Time Spent} / {Original Estimate}) * 100 | Number (percent) |
IT operations lead
Track SLA health and flag tickets nearing breach in real time.
Use case | Formula | Output type |
Time to resolution | DATE_DIFF({Created}, {Resolved}) | Number |
SLA breach risk | IF(DATE_DIFF(TODAY(), {SLA Due}) < 1, "Breach soon", "Safe") | Text |
Incident impact | {Users Affected} * {Downtime Minutes} | Number |
HR and people ops
Measure onboarding and recruiting progress accurately across every candidate.
Use case | Formula | Output type |
Onboarding percent | ({Tasks Completed} / {Total Tasks}) * 100 | Number (percent) |
Time to hire | DATE_DIFF({Application Date}, {Offer Date}) | Number |
Employee tenure | DATE_DIFF({Hire Date}, TODAY()) | Number |
Common formulas by use case
Beyond specific roles, these formulas cover the calculations teams reach for most. Adapt the field names to match your project.
Financial calculations
Use case | Formula | Output type |
Budget variance (percent) | (({Approved Budget} - {Actual Costs}) / {Approved Budget}) * 100 | Number (percent) |
Vendor invoice total | {Quantity} * {Unit Price} | Number (currency) |
Total project spend | {Labor Cost} + {Material Cost} + {Travel Cost} | Number (currency) |
Actual labor cost | {Time Spent} * {Hourly Rate} | Number (currency) |
Prioritization and scoring
Use case | Formula | Output type |
RICE score | ({Reach} * {Impact} * {Confidence}) / {Effort} | Number |
Weighted risk score | ({Probability} * 0.7) + ({Impact} * 0.3) | Number |
Risk rating | {Probability} * {Impact} | Number |
Dates and deadlines
Use case | Formula | Output type |
Text and data hygiene
Use case | Formula | Output type |
Using custom field and formula results across Jira
A field is only as useful as what you can do with it. Once your fields hold the right data, put them to work:
Filter and search with JQL. Query a board for "Budget variance less than 0" or "Days remaining less than 5."
Report in dashboards. Summarize a formula result across work items in a dashboard gadget, like total remaining budget across active campaigns.
Trigger automation. Run an automation rule when a value crosses a threshold, like alerting a lead when variance goes above 10 percent.
Best practices for custom fields
A field costs nothing to create and something to maintain, so a little discipline keeps Jira fast and your reports clean.
Search before you create. Go to Jira settings, then Work items, then Fields, then Field schemes, and search for your idea. If "Client" already exists, do not create "Customer." You will split your reporting data.
Name for value, not type. “Approved budget” is better than “Number field 3.” A good name means no one needs a glossary.
Match the type to the job. Store values you will calculate on as numbers or durations, and values you will filter on as choice fields.
Reuse field schemes where you can. Standard schemes keep similar teams on the same fields and make reporting cleaner. Avoid creating one-off schemes unless the team has a real exception.
Keep field schemes below the limit. A field scheme can include up to 700 fields. Treat that as a ceiling, not a goal.
Archive what you do not use. Fields that no one fills in add noise to every screen and every report.
Frequently asked questions
What is a Jira field scheme?
A Jira field scheme controls which fields apply to each work type across assigned projects. It helps admins manage availability and required status from one place.
How do I create a custom field in Jira?
Go to Jira settings, then Work items, then Fields, then Field schemes, and select Create custom field. Choose a field type, name it, then apply it to the projects and screens where you want it to appear.
Who can create custom fields in Jira?
A Jira admin creates and manages custom fields. In team-managed projects, a project admin can add fields within their own project settings.
How do I create a formula field?
Create a custom field and choose the formula type, name it for the value it produces, write the formula referencing other fields, and set the output type. Then add it to the right field scheme and screens.
Do I need to know formula syntax to create one?
No. You can reference field names and operators directly, or describe the calculation in plain language and let Rovo generate the formula for you.
Which fields can a formula reference?
A formula can reference number, date, text, and choice fields on the same work item. Store values you plan to calculate on as numbers, dates, or durations rather than text.
Why is my formula value not updating right away?
Formula fields update automatically when a referenced field changes, but updates can be asynchronous. A new value may take a short time to appear across work items. Formula fields calculate per work item and do not roll up values across parent or child work items.