JavaScript calculated custom fields (NEW)
Should choose the best name for the page:
- New calcauted fields
- New calcauted custom fields
- JavaScript calculated fields
- JavaScript calculated custom fields
When you need calculated 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.
The main goals for calculated fields are:
- improve report performance
- organize data in a new way based on available data
Account specific vs. global calculated field
How to choose between account specific and global calcualted fields? And what is the difference?
- Do you need this field for one account, or will you reuse it for many?
- What is your access rights?
Account specific
TODO: Account calculated fields (RENAMED)
- Field only needed for this account >> Account calcauted field.
- No Jira admin needed, Account owner, user admin or Data admin can do this.
Global
TODO: Global calculated fields (RENAMED)
- Field could be used in other accounts too >> test the field in one account and add it to Global calcauted field.
- Only Jira admin can add field toa advancd settings.
Validation
While building the new calcauted field, you should validate the code on a specific issue to see the potential outcome.
For both calcauted 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.
- Global Global calculated fields (RENAMED)
- Account specific: Account calculated fields (RENAMED) TODO: add new chapter on how to validate the outcome
Calcualted fiel examples
Calculated field examples (NEW)