Jira custom field advanced settings

You could modify import options for Jira standard custom fields and define calculated custom fields in Private eazyBI as you can do it with Jira add-on eazyBI advanced settings. Jira custom field advanced settings should be defined in eazybi.toml.

Jira custom field advanced settings could be defined globally or for some Jira site.

Jira site definition

Jira site should be defined in eazybi.toml file prior to custom field definition. 

[source_application.jira.site_XXX]
url = ".."

You should use any name instead of XXX for naming Site. You should use Jira base URL instead of ".."

Advanced settings for custom field

Global Jira custom field advanced settings should be defined:

[source_application.jira.customfield_NNNNN]

where NNNNN is a custom field ID. This will start the block of configuration parameters for the NNNNN custom field. After that line add any other custom field specification as described in Jira add-on eazyBI advanced settings.

Global settings could be used only for those custom fields with the same identification for all Jira instances. Custom field ID should match in all Jira instances to get imported properly. If custom field IDs do not match in your Jira instances please define this custom field for each site separately.


Jira custom field advanced settings for a particular site should be defined: 

[source_application.jira.site_XXX.customfield_NNNNN]

You should use the previously defined Site name for XXX and custom field ID instead of NNNNN. This will start the block of configuration parameters for the NNNNN custom field. After that line add any other custom field specification as described in Jira add-on eazyBI advanced settings.

Custom fields with this configuration will be available in the Jira import options screen for selection after changes are saved in eazybi.toml file.

JavaScript calculated custom fields

In eazyBI, you can pre-calculate and import additional calculated custom fields based on Jira issue data. Those fields will be available just in eazyBI and not in Jira.

For example, If you have a larger number of Jira issues then it is better to import calculated custom fields and not to create calculated members with complex MDX formulas. Calculated custom fields are pre-calculated just once during Jira import and then saved in the eazyBI database and then eazyBI queries will perform much faster using pre-calculated data.

The main principles to create JavaScript calculated custom fields are the same as for eazyBI for Jira product. The difference is how the custom field is addressed in the eazybi.toml file

  1. Make sure the source application is defined prior to the custom field

    [source_application.jira.site_XXX]
    url = ".."
  2. the custom field name (1st line) matches the pattern:

    [source_application.jira.site_XXX.customfield_NAME]

Example

With this custom field definition for Jira site XXX will enable change value import for a custom field with ID NNNNN:

[source_application.jira.site_XXX]
url = ".."
 
[source_application.jira.site_XXX.customfield_NNNNN]
data_type = "string"
dimension = true
separate_table = true
changes = true

Please use the correct Jira base URL instead of ".." 

Data from Jira apps

eazyBI has integration with most of popular Atlassian Marketplace Jira apps. Some app custom fields will be available, but to enable data import from

you should specify the Jira database connection details in eazybi.toml file. The example below is for Jira site XXX with MySQL database connection.

For MSSQL the Jira user should have DEFAULT_SCHEMA=<jira_database_name>


[source_application.jira.site_XXX.database]
"adapter" = "mysql"
"host" = "localhost"
# "port" =
# "ssl" =
# "instance" =
"database" = "jira"
"username" = "jira_db_user"
"password" = "*****"