This page describes advanced Jira and eazyBI integration. If you need help with this please contact eazyBI support.
If you would like to pre-calculate and import in eazyBI additional calculated custom fields then
- you can either use Jira Misc Custom Fields add-on and define Jira calculated custom fields (or use some other add-on that allows to define calculated custom fields),
If you have 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.
Define calculated custom field in eazyBI advanced settings
You should define an additional custom field in the advanced settings with the following additional settings:
- Use your own
customfield_NAMEcustom field name where
NAMEis some unique descriptive name of your additional calculated custom field.
- Add a
namesetting and specify a display name for this calculated custom field that will be visible in Jira import custom fields selection (these calculated custom fields will be always visible for any Jira project selection).
Here is an example of a calculated custom field "Issues overdue" which will return 1 if issue has a due date and either resolution date is after a due date (for resolved issues) or a due date is in the past (for unresolved issues). Add to the advanced settings:
Then import "Issues overdue" custom field as a measure and eazyBI will create measures "Issues overdue created", "Issues overdue due" (total of unresolved issues that are past their due date), "Issues overdue resolved" (total of resolved issues that were late).
issue.fields then during testing it is easier to assign the result to top level
issue property as then you will not need to expand
issue.fields. (In this example during testing assign the result to
issue.customfield_overdue and when you see that it is working as expected then change it to
By default, you can see only standard issue fields as well as selected custom fields in the issue JSON object. Additional issue fields
issuelinks will be returned only if
Custom calculated field as an interval dimension
You can define calculated custom fields also for import as an interval dimension. In this case, specify the following additional settings:
time_unitspecify the corresponding time unit.
interval_unitspecify the default interval ranges that should be used (which can be later changed in the Analyze tab).
Here is an example of "Age since updated interval" dimension which will show the age intervals (from the last update date until now) for unresolved issues:
Calculated worklog custom field
Available from eazyBI version 4.1.
If you store some structured information in worklog comments (for example if the work is billable or non-billable, or if it is overtime) then you can use calculated worklog custom fields to extract this structured information as a separate dimension.
worklog = truewhich will indicate that it is a worklog custom field.
worklogobject (which contains JSON representation of one worklog entry as in issue JSON representation). Worklog comment can be accessed as
The custom field value should be assigned to
Here is an example of a Worklog Comment dimension which will import the first word in lowercase from worklog comments:
Import Worklog Comment as a dimension and then use it to analyze Hours spent measure.
All issue links
With eazyBI version 4.1. there is an option to define issue link custom fields with specified link direction.
Here is an example of a All issue link dimension which will import all issue links, except epic and sub-tasks links:
Import All issue links as a dimension and as a property.
Last date when custom field changed
In eazyBI, it is possible to import single-value select custom field in a separate table with value changes by adding these advanced settings to your custom field (where you place your actual custom field ID instead of NNNNN)
Then you could import this custom field as a dimension and import also value changes in eazyBI.
Here is an example of a Jira single-value select custom field which will return the last date when a pre-defined custom field was set to the pre-defined value:
Import Value change date as a measure and as a property.
Days for Assignee
To analyze how many days issue was assigned for each assignee until the issue resolution date, you can precalculate the time between assignee transitions based on issue change history for each issue and then import this information as a measure Days for assignee. The measure is also associated with Time dimension (by transition from assignee date)
Use this measure in reports together with Assignee and/or Time dimension.