Add computed custom fields whose values are calculated by your scripts. Nine field types - text, number, date, datetime, rich text, user, user list, group and group list - that recalculate on issue create and update, running entirely on Atlassian Forge.
Out of the box, Jira custom fields are static - the user types a value, the value is stored. Scripted custom fields turn the value into a derivation: at the moment an issue is created or updated, your script runs and computes the field's value from anything you can reach via the Jira REST API or your own data tables.
This is exactly the workload teams used to build on legacy Connect-based scripting tools. With Atlassian Connect end of support arriving on 31 January 2027, moving scripted fields to a Forge-native runtime keeps them maintained, secure, and aligned with Atlassian's platform direction.
JiBrok Studio's scripted fields are computed inside the same Forge runtime as the rest of the app. No external server holds the calculation logic, and no third-party service sees your issue data.
A scripted number field on each Story that sums the story-point estimates of all its subtasks. The value refreshes whenever a subtask is added or its estimate changes.
A scripted datetime field that computes a target resolution time from priority, business hours, and customer tier - usable in JQL, dashboards, and SLA reports.
A scripted paragraph field that builds an Atlassian Document Format (ADF) block summarising linked epics, customers, and key dates - rendered as native rich content on the issue.
Scripted fields store a value on each issue and refresh on create/update. When you need on-demand search logic instead - "which issues match these arbitrary criteria right now?" - use a custom JQL function like issue in jbExec(...).
Both run on the same Forge runtime, share the same Scripting API, and live in the same script library.
Sum story points across all subtasks of the current issue.
// Scripted Number Field: sum of subtask story points
// 'issue' is the parent issue, auto-loaded by the platform
const STORY_POINTS = 'customfield_10016';
const subtasks = issue.fields.subtasks || [];
let total = 0;
for (const sub of subtasks) {
const child = Issues.get(sub.key,
{ fields: [STORY_POINTS] });
total += child.fields[STORY_POINTS] || 0;
}
return total;Save the script, link it to a Scripted Number Field, and assign the field to your screens. The value refreshes whenever the parent issue is updated.
JiBrok Studio's scripted fields run 100% on Atlassian Forge - your issue data never leaves Atlassian's cloud.