JavaScript calculated custom fields

eazyBI can precalculate new fields using JavaScript and based on available data. Calculated custom fields are pre-calculated just once during data import and then saved in the eazyBI database. Using pre-calculated data, eazyBI queries will perform much faster. But keep in mind that each additional field imported in eazyBI increases the size of the data cube. Therefore, we recommend defining and importing those fields necessary for reports.

The main goals for calculated fields are:

improve report performance
organize data in a new way based on available data

On this page:

Account specific vs. global calculated field

How to choose between account-specific and global calculated fields? And what is the difference?

You can start by answering the following questions:

Do you need this field for one account, or will you reuse it for many?
What are your access rights?

Account-specific custom fields

Account-specific custom fields are calculated and used in one eazyBI account only and are not available for other eazyBI accounts.

eazyBI users with data admin or higher roles can define new calculated fields in the account.

This is a good choice for team-specific or project-specific measurements or dimensions that are not relevant for other teams or projects. For example, a new calculated field that merges multiple issue fields.

Global calculated fields

Global calculated fields are defined once per eazyBI instance from advanced settings and are available for all eazyBI accounts. The data admin should select and import them into a particular account to use them in reports.

Only Jira system administrators and Jira org admins can define new global calculated fields in eazyBI.

Validation

While building the new calculated field, you should validate the code on a specific issue to see the potential outcome.

For both calculated fields, account-specific and global, validation is done in the account import options, where you can access data on a specific project and issue chosen for testing. We recommend choosing at least two issues to test as many different outcome scenarios as possible.

Examples

Here are several examples for both - global and account-specific examples: