Introduction

We are using Atlassian’s Cloud toolkit Forge for developing Agile Hive Cloud, which results in us being technically bound to Forge’s feature set. Forge is not as mature as other development toolkits (above all compared to DC), hence some things might just not work at all, until Atlassian fixes issues with Forge or extends it’s functionality. On this page, we want to document such scenarios and explain them technically.

Calculated Custom Field Values

In Agile Hive, we have a few Custom Fields, and some of them are derived from other Custom Field values, e.g. the Exposure values for Risks or the WSJF Value. These Custom Field values cannot be set through the UI, and are also not set by us manually. Instead, we registered a “value function” for these calculated fields, which retrieves other Custom Field and calculates the value based on them.

Unfortunately, this function (and as a result the calculation of the Custom Field value) is only triggered upon an issue view. The value is not initially set upon creation, and not updated when searching for it via JQL. For that reason, we are calculating and displaying the Risk Exposure and WSJF values locally in our Report widgets and displaying a warning for inconsistent field values.

Link to this page: https://seibert.biz/ahc-reports-limitations