Calculated Fields (Forge) for Jira Cloud

Looking for the Connect edition docs? See Calculated Fields (JBCF) - Connect.

Welcome to Calculated Fields (Forge) for Jira Cloud

Calculated Fields (JBCF) for Jira Cloud is a library of custom fields that derive their value from issue state - comments, changelog history, links, project metadata, parent hierarchy, and Jira Service Management SLAs - plus one interactive field, ToDo List. You add a field to an issue screen, and Jira shows the calculated value automatically.

This is the Forge edition of JBCF, rebuilt on Atlassian Forge. Every resolver, scheduled job, and storage call runs inside Atlassian’s cloud, next to your Jira instance - no companion server, no Heroku, no OAuth setup on your side. The app carries Atlassian’s Runs on Atlassian badge.


What’s in the box

JBCF Forge registers 32 Jira custom field types: 31 calculated fields, organized into six groups, and the interactive ToDo List field. Each of them is a standard Jira custom field, so it is searchable, sortable, displayable on issue views, and exportable via the Issue Navigator or REST API.

Comment fields (12)

Surface what was said on an issue without scrolling the comment thread - first and last comment text, dates, authors, the full commenter list, and whether the commenter happens to be the assignee or reporter.

Changelog fields (7)

Read history straight off the issue - among them previous status, previous assignee, the user who triggered the last status change, the resolver, the last updater, and the full assignee history.

Plain numeric counters - total links, subtasks, inward links, outward links - that recalculate as links change.

Project context (2)

Project lead and component leads for the issue’s project, shown on every issue in that project.

Hierarchical sort keys (5)

Composite sort keys that group subtasks under their parent or issues under their epic in any sorted list, in ascending, descending, or rank order.

Jira Service Management SLA (1)

SLA breach time - the moment the goal of the current cycle of a JSM SLA metric will be breached. You pick the metric in the field’s context configuration.

ToDo List (interactive)

The one field users fill in themselves: a checklist on the issue, with items that can be marked done and assigned. It comes with an issue panel, three JQL functions for searching by checklist state, a workflow validator, and a REST API for your scripts and integrations.

For the field tables with data types and event triggers, see the Field reference.

License

JBCF Forge needs an active license. While the license is active, everything works as usual; while Jira does not report the license state, so the license state cannot be determined, the app works as usual too. When Jira reports the license as not active:

  • calculated fields are no longer updated when issues change, and recalculation from the admin page is refused;
  • checklist templates are not applied to new issues, and they cannot be saved or deleted on the admin page;
  • the ToDo List REST API refuses to update checklists (PUT /todo/items answers 403);
  • checklists cannot be changed in the ToDo List panel or in the field editor: Edit, Save and the item checkboxes are disabled; the checklist itself stays visible;
  • the admin page, the field context configuration, the ToDo List panel and the field editor show This app requires an active license. Check the app license in Manage apps.

Nothing is deleted. Values already calculated stay on the issues, stay visible and stay searchable in JQL, and checklists can still be read.


How JBCF Forge differs from the Connect edition

JBCF Forge is not a straight port of the Connect edition - the platform is different, and so are the operational guarantees.

Area JBCF Connect JBCF Forge
Platform Atlassian Connect + external server 100% Forge native - Runs on Atlassian
Hosting Vendor-managed Heroku service Atlassian-hosted Forge runtime
Storage Vendor-managed database Field values in Jira; settings in Forge KVS (Atlassian-managed, encrypted at rest)
Outbound network Required (Connect callbacks) None - the manifest declares no external: scopes
Monitoring Vendor logs / status page Built-in app-monitoring via the Forge App Logs API
Field set 29 derived fields 31 calculated fields plus the interactive ToDo List
Sub-processors Heroku and Atlassian Atlassian only

If you’re moving from JBCF Connect to JBCF Forge, see the Migration guide.


Get started

  1. Install the app from the Atlassian Marketplace - Calculated and other custom fields for Jira Cloud (Forge).
  2. Create a Jira custom field and pick the JBCF field type you need - each calculation is registered as its own field type, so search the type list for the field you want (for example Number of comments).
  3. Add the field to your issue screens for the projects and issue types that should see it.
  4. Use the value - it updates automatically as comments, status, links, and assignments change.

For a step-by-step walkthrough, see the Getting started guide.


All documentation pages

Get going

Configuration and migration

JBCF Forge focuses on calculated/derived fields. Other JiBrok products cover adjacent territory:

  • Time in Status (Forge) - status time, stopwatches, timers, work calendars, activity reports
  • JiBrok Studio - formula scripting language and scheduled jobs (separate marketplace listing)
  • Display Linked Issues - extended visualization of issue links