Forge edition — November 2026
This is the first Forge edition of Calculated Fields (JBCF) for Jira Cloud. It is an update of the Connect edition’s Marketplace listing: an installed Connect app updates to Forge in place, with the Update button in Manage apps. The app runs on Atlassian Forge and does not use external servers.
New
32 field types: 31 calculated fields and the ToDo List
JBCF adds 32 custom field types: 31 calculated fields and 1 interactive field, the ToDo List.
- Calculated fields fill themselves in from data the issue already has: comments (12), issue history (7), links and sub-tasks (4), sorting (5), project (2) and Jira Service Management SLAs (1). Users cannot edit them, and most of them need no setup.
- Two of them take one setting in the field context: Date of last transition (which status, or any status) and SLA breach time (which SLA). Until you choose, the field stays empty.
- Calculated fields are real Jira fields of their type: user fields show the user with their avatar and are searched like any user field (for example
= currentUser()), date fields take date comparisons, number fields take=,>,<.
See Field reference.
ToDo List
ToDo List is a checklist field that users fill in on the issue: add items, tick them off, give them a status, an assignee, a due date and a note, and mark the ones that must be done. Section headers group items. A site can have several ToDo List fields - for example, one for a definition of done and one for a release checklist. The field comes with an issue panel, and each field context sets its own statuses. See ToDo List.
Checklist templates
A template prefills ToDo List fields on issues as they are created. Jira administrators manage templates on the admin page, Templates tab. See Checklist templates.
ToDo List in JQL
Three JQL functions find issues by the state of their checklist: allItemsDone(), allItemsUndone() and todoItem("text", "state"). Each ToDo List field also has searchable properties, for example "ToDo List.TodoProgress" >= 50 or "ToDo List.TodoOpenMandatory" > 0. See ToDo List in JQL.
Workflow validator
The validator ToDo List: mandatory items resolved blocks a transition while the checklist still has unresolved mandatory items, with an optional message of your own. See Workflow validator.
ToDo List REST API
Two REST endpoints let scripts and integrations read and replace the items of a ToDo List field: GET /todo/items and PUT /todo/items. They run on behalf of the calling user, and read and write are separate scopes. See ToDo List REST API.
Admin page and recalculation
The admin page (Jira settings → Apps → Calculated Custom Fields, for Jira administrators) has four tabs:
- Overview - the table of all field types with search and Field details, Run Self-Check, and Recalculate all;
- Templates - the checklist templates;
- Service Info - the state of background recalculation, refreshed every 30 seconds, and Recalculate by JQL;
- Migration from Connect - the move from the Connect edition and the filter audit.
Fields recalculate by themselves when Jira reports a change on the issue. To fill in values on issues that existed before a field was created, recalculate every field (Recalculate all), one field (Recalculate this field in Field details) or the issues of a JQL query (Recalculate by JQL). See Admin page and Recalculation.
Changes for Connect users
Values and searches that behave differently from the Connect edition:
| Area | Connect edition | Forge edition |
|---|---|---|
| The four Is author of first / last comment assignee / reporter fields | true / false |
Yes / No - search them as = "Yes" / = "No" |
| These fields on an issue without an assignee (or without a reporter) | Empty | No - a filter with = false now finds such issues too, and one with is EMPTY no longer does |
| User fields | The user’s name as text | User fields that hold the accountId - rewrite JQL that searched them by user name |
| Field ids | Connect fields | New fields with new ids - check saved filters, dashboard gadgets, quick filters and reports that use the old cf[id] or name |
Text fields - Last comment, First comment, the Yes / No fields, Previous status and the sorting fields - are matched on the whole value: =, in and is EMPTY work, for example "Previous status" = "In Progress"; searching for a word with ~ does not find them.
The filter audit on the Migration from Connect tab suggests the new JQL for saved filters, including = true → = "Yes", = false → = "No" and ~ → = for the Yes / No fields. See Searching comment fields and Filters after the move.
Migration
From the Connect edition
- Settings are picked up automatically. The app looks for the Connect settings by itself every hour, so nothing has to be exported by hand.
- A file as a fallback. If the settings are not found, select Download for Forge in the Connect edition and Upload file from Connect in the Forge edition.
- A checklist of fields to create. The Migration from Connect tab lists every field to make, with its exact name, type, projects and issue types. Create them by hand, or with a JiBrok Studio scenario the tab prepares.
- Run again links each new field to its Connect settings by type and name and queues a recalculation, so the values are worked out from the issues.
- Filter audit. A read-only report lists the saved filters that use an old Connect field, with a suggested JQL to send to the filter owner.
See Migrate from JBCF Connect to JBCF Forge.
From Jira Data Center
The Forge edition also takes part in a migration from Jira Data Center with the Jira Cloud Migration Assistant. See Migration.

