Guide · Jira Cloud
Add custom fields to Jira that behave like native
Product scoring, ratings, and structured intake should live as real Jira fields next to Summary and Assignee — not in a spreadsheet your team abandons after the first sprint. Pick a type from a catalog, create the field in Jira’s own screens, and keep values on the work item.
Try free when live · ~USD 1.30/user/mo after ≤10 free · listing may still be pending Atlassian approval
App docs · try path01 — The gap
Why teams invent fields outside Jira
Native Jira field types cover a lot, but product frameworks (MoSCoW, WSJF, RICE), multi-axis ratings, and intake patterns often end up in Confluence tables or Sheets. When scoring lives off-issue, filters and boards cannot use it — and the next portfolio review asks why priority scores disagree between tools.
02 — What buyers usually want
Catalog types that become real custom fields
- Forty-plus field types across common categories — scoring frameworks, ratings, and structured values — not a one-off text dump.
- Admin catalog that shows what each type does, whether it is editable or computed, and whether calculation is on.
- Values on the issue next to Summary and Assignee so boards, JQL, and exports can use them.
- Real Jira custom fields created in Jira’s own screens — not a sidecar database of values the rest of Jira cannot see.
- Honest platform limits documented in-app (Forge cannot withdraw a field type or hide fields already on screens).
03 — How to add them without a sidecar
A practical path for Jira Cloud admins
- List the 3–8 scores or ratings your teams actually use in planning (skip vanity fields).
- Open the field catalog, pick matching types, and note editable vs computed.
- Create the actual custom fields in Jira’s custom-fields screen and put them on the right screens / issue layouts.
- Train one pilot project: fill values on create or in triage, then filter / sort on a board.
- Roll out only the fields that stuck — empty fields train people to ignore all custom fields.
04 — Tooling
Custom Fields for Jira
Custom Fields for Jira (Custom Fields Suite on Marketplace) is a Forge app for Jira Cloud. It ships forty-plus field types; you create the real custom fields in Jira’s own screens. Intended design: compute on Atlassian Forge, customer data stays in your site — no external egress path. It is not a replacement for native fields or a separate CRM of issue values.
Marketplace listing: Custom Fields Suite (may still be in Atlassian review — the Marketplace URL is the source of truth). Product docs: /apps/custom-fields-for-jira. Support: info@berkly.nl.