Whole Number Field for Jira

Set up the field

A Jira administrator creates a custom field of type Whole number and adds it to the relevant screens. Use it for counts, years and reference numbers that do not need leading zeros. Jira stores a number: 007 becomes 7.

In the field's context settings, choose an optional minimum, maximum and thousands separator. With no separator, 2026 and 1234567 show as typed. Comma displays 2,026 and 1,234,567. Negative whole numbers such as -7 are allowed unless the configured range excludes them.

Decimals are refused. The create screen and REST API can show Whole number field: only whole numbers are allowed, and 2.5 has a decimal part. Issue-view inline editing uses Jira's number input and can show the browser's own validation tooltip instead.

Ranges during create and edit

Work-type range enforcement is unavailable during create: Jira does not tell the validation the work type. A test with multiple contexts in one project accepted a value fitting another work type's range. The exact range for the work type applies on subsequent edits. Create-time range checks are not reliable after changing context settings; review values after creation and do not rely on create to enforce a minimum or maximum.

For example, if Epic allows 0 to 5000 and Task allows 10 to 20, a Task with 30 can be created. It is not refused during create. The formatter subsequently shows 30 (outside the range 10 to 20 set for this work type). The value is not changed or cleared. Editing it to 15 removes the notice; an edit to an out-of-range value is refused with Enter a whole number from 10 to 20.

Copy existing number values

In Jira administration, open Apps › Whole Number Field. Choose a source number field, a target Whole number field and a query, then preview before copying. The copy leaves filled targets alone. It lists decimals, values too large to hold exactly and values outside the governing context's range instead of rounding or copying them. Keep the page open until it finishes. There is no app undo; review the preview first.

Known limitations

Use Jira's newer bulk Edit fields panel; the legacy Bulk change wizard does not list the Forge field. A bulk refusal can show only Jira's Failed to update. Whole numbers are exact only within ±9,007,199,254,740,991; longer references belong in text fields. Forge fields may not work in Jira mobile, other Atlassian apps or Automation.

The range notice is supported by development 4.2.0 evidence; the Marketplace production release must include that change before relying on this notice there.

See the privacy policy and terms. Questions: support@accounts.datadelight.co.