Getting Started with Calculated Fields (Forge)

This guide walks you from a fresh install to a working calculated field on a Jira issue. You’ll add the Number of comments field as an example - the same flow applies to every JBCF Forge field type.


Step 1. Install from the Marketplace

  1. Log in to Jira Cloud as a site administrator.
  2. Go to Settings (gear icon) → Apps → Find new apps.
  3. Search for “Calculated Fields (Forge)” or open the listing directly: Calculated and other custom fields for Jira Cloud (Forge).
  4. Click Get it now or Try it free and accept the requested Forge scopes.
  5. Wait for the install to complete (usually a minute).

The app installs as a Forge app - there is no companion service to configure on your side. It carries Atlassian’s Runs on Atlassian badge.


Step 2. Open Jira’s custom field administration

  1. In Jira, go to Settings ⚙ → Issues → Custom fields.
  2. Click Create custom field in the top right.

Step 3. Pick the JBCF field type

Each JBCF field is registered as its own Jira field type - 32 of them in total - so you choose the calculation directly in the field type list. There is no second step where you pick a calculation inside a generic JBCF type.

  1. In the field type list, search for JBCF or for the field you need, for example Number of comments.
  2. Select the type. Each type corresponds to one of the field IDs documented in the Field reference.
  3. Give the field a name (for example, Comment count) and an optional description.
  4. Click Create (or Next, depending on your Jira version).

Step 4. Add the field to a screen

  1. After creation, Jira asks which screens should show the field. Choose the screens for the projects and issue types where you need the value.
  2. Click Update.

If you skipped this step, you can attach the field later via Settings ⚙ → Issues → Screens and editing the screen that displays the field.


Step 5. See the value on an issue

  1. Open or create a Jira issue on a project that uses the screen you just edited.
  2. Add a comment.
  3. Refresh the issue view - the Comment count field displays the calculated value (1).

Add a second comment, and the field updates to 2. JBCF Forge listens for the relevant Jira events (comments added, status changes, links updated, and so on) and refreshes the calculated value automatically.


Step 6. Fill in existing issues

A new calculated field has no value on issues that existed before it was created. On such an issue the value appears the next time the issue changes, or after a recalculation from the app’s admin page:

  1. Go to Jira settings → Apps → Calculated Custom Fields (you need Jira administrator permission).
  2. On the Overview tab, click Recalculate all. To fill in one field only, click its name and use Recalculate this field in Field details; for some issues only, use Recalculate by JQL on the Service Info tab.
  3. The dialog shows “This will affect approximately N issues.” Confirm with Recalculate.

The work runs in the background in batches, and you can close the page. Follow its progress on the Service Info tab. See Recalculation for the details.


What you should know about JBCF Forge fields

  • Calculated fields are read-only. They derive their value from issue state. When the data a field needs is not there, the issue shows the field as None; counters show 0. Writing a calculated value does not add an entry to the issue history. You cannot type a value into them; they are not surfaced on the Create or Edit screens as editable inputs. The one exception is ToDo List, which users fill in on the issue - see the Field reference.
  • They are standard Jira fields. Each calculated field is a native Jira custom field. It works in JQL, filters, list views, Issue Navigator columns, Export to CSV, and the REST API.
  • They recalculate on the right event. A comment-related field recalculates when a comment is added, edited, or deleted. A changelog-related field recalculates on status, assignee, or resolution changes. A link-count field recalculates when a link is created or removed. See the Field reference for the per-field trigger.
  • Values live in Jira. Each calculated value is written to Jira as the field value, so JQL searches work against an up-to-date index. The app keeps no copy of it; Forge KVS holds only the app’s settings, its service state, and ToDo templates.
  • They need an active license. When Jira reports the license as not active, calculated fields are no longer updated, recalculation from the admin page is refused, checklist templates are not applied, saved or deleted, PUT /todo/items answers 403, and Edit, Save and the ToDo List checkboxes are disabled. The admin page, the field context configuration, the ToDo List panel and the field editor show the banner This app requires an active license. Check the app license in Manage apps. Nothing is deleted: values already calculated stay visible and searchable, and checklists can still be read. If the license state cannot be determined, the app works as usual. See License.

Next steps

  • Field reference - what each field means, its data type, and what triggers recalculation.
  • Recalculation - what is recalculated automatically and how to recalculate from the admin page.
  • Admin page - the field table, Self-Check and Service Info.
  • Migration from Connect - if you already use JBCF (Connect edition) and want to move to Forge.
  • Security - Forge scopes, storage, monitoring, and data residency.