Skip to main content

Performance and limitations

FieldCraft, as an Atlassian Forge app, provides Calculated Custom Fields functionality and has some limitations due to the Forge platform's architecture.

Recalculation triggers and reliability notes​

Use this section as the source of truth for when calculated field values are refreshed.

Guaranteed recalculation trigger​

  • Work item view: Field values are recalculated when a user opens a work item in the work item view.

Best-effort recalculation trigger​

  • Issue update events: Field values can be recalculated when an issue update event is captured by the app.
  • Due to Forge platform constraints, this trigger is best-effort and may occasionally be missed.

Not guaranteed​

  • Updates made through automation, REST API, or other background processes are not guaranteed to recalculate field values immediately.
  • If no guaranteed or best-effort trigger runs, values can remain stale until a work item is opened or reindexed.

When to run Reindex​

  • Run Reindex after major field configuration changes.
  • Run Reindex when you need up-to-date values on older work items that users have not opened recently.

⚠️ Key limitations​

  • Work item view is the only guaranteed trigger
    Opening a work item in the work item view is the only guaranteed way to refresh calculated values.
    Changes made by automation, REST API, or other background processes are not guaranteed to trigger an immediate recalculation.

  • Old work items remain without values until opened
    If a custom field is added to existing work items, those work items will not have values until a user opens them.
    This means historical work items remain unchanged until accessed.

  • Recommendation for updating old work items
    To populate values for all existing work items when a new custom field is added, we recommend using the Reindex feature.
    This operation must be performed by a Jira administrator, as it triggers a full recalculation of custom fields across all work items.

These limitations are due to the way Forge handles background execution and cannot be bypassed at the moment.