I got the following structure:
Epic (contains custom_field value needed)
I want a report like this:
Num of bugs resolved
Num of bugs created
Custom_field value 1
Custom_field value 2
Any suggestion is welcome, Thanks!
In this case, try defining and importing new inherited field “Epic custom_field” from the advanced settings as in this example:
Since eazyBI does not currently support Components as Linked Issue Dimensions, we are looking for a workaround to apply the Component set on a Epic to all of its Child tickets.
We tried creating the below Advanced Import field but can’t seem to get it to import properly.
name = “Epic Components”
data_type = “string”
multiple_values = true
split_by = “,”
dimension = true
update_from_issue_key = “epic_key”
The JS code part an vary depending on your “custom_field” type as different type fields could have different JSON structure in Jira.
But this approach would work only for single-select Jira custom fields (one value per field per issue).
Martins / eazyBI
I tried this solution.
The only thing that I am missing is that using this solution - I can’t see the bugs… The bugs are located in different project(s) and using this method only issues from the same project of the epic can be seen.
in my use case - the custom fields are text fields
Make sure the bugs from other projects are imported from the import options page.
The hierarchy won’t show unimported issues.
The approach should work find with single-line text fields.
The JS code would be slightly different (because JSON structure for text fields is different), but it should work with text fields.
Martins / eazyBI
Thanks, it worked!
I missed something in the configuration of the epic custom field, now it’s working as expected.