# Report based on the issue epic value

**URL:** <https://community.eazybi.com/t/report-based-on-the-issue-epic-value/12540>\
**Category:** Questions & Answers\
**Created:** [May 4, 2023, 10:08am UTC](https://community.eazybi.com/t/report-based-on-the-issue-epic-value/12540 "2023-05-04T10:08:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![elyashivg](https://community.eazybi.com/letter_avatar_proxy/v4/letter/e/f19dbf/32.png) [@elyashivg](https://community.eazybi.com/u/elyashivg)\
**Post date:** [May 4, 2023, 10:08am UTC](https://community.eazybi.com/t/report-based-on-the-issue-epic-value/12540/1 "2023-05-04T10:08:11Z")

</div>

I got the following structure:  
Epic (contains custom\_field value needed)  
----bugs

I want a report like this:

| (From epic) | Num of bugs resolved | Num of bugs created |
| --- | --- | --- |
| Custom\_field value 1 | ### | ### |
| Custom\_field value 2 | ### | ### |
| … | … | … |

Any suggestion is welcome, Thanks!

---

<div class="post-metadata">

**Author:** ![martins.vanags](https://community.eazybi.com/user_avatar/community.eazybi.com/martins.vanags/32/8905_2.png) [@martins.vanags](https://community.eazybi.com/u/martins.vanags)\
**Post date:** [May 8, 2023, 1:56pm UTC](https://community.eazybi.com/t/report-based-on-the-issue-epic-value/12540/2 "2023-05-08T13:56:13Z")

</div>

@elyashivg

In this case, try defining and importing new inherited field “Epic custom\_field” from the advanced settings as in this example:

> [@Applying Epic Components to all Child Tickets](https://community.eazybi.com/t/applying-epic-components-to-all-child-tickets/5496):
>
> 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. [jira.customfield\_epiccomponents] name = “Epic Components” data\_type = “string” multiple\_values = true split\_by = “,” dimension = true update\_from\_issue\_key = “epic\_key” javascript\_code = ‘’’ issue.fields.customfield\_e…

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

---

<div class="post-metadata">

**Author:** ![elyashivg](https://community.eazybi.com/letter_avatar_proxy/v4/letter/e/f19dbf/32.png) [@elyashivg](https://community.eazybi.com/u/elyashivg)\
**Post date:** [May 8, 2023, 2:31pm UTC](https://community.eazybi.com/t/report-based-on-the-issue-epic-value/12540/3 "2023-05-08T14:31:01Z")

</div>

Thanks @martins.vanags !  
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

Thanks

---

<div class="post-metadata">

**Author:** ![martins.vanags](https://community.eazybi.com/user_avatar/community.eazybi.com/martins.vanags/32/8905_2.png) [@martins.vanags](https://community.eazybi.com/u/martins.vanags)\
**Post date:** [May 8, 2023, 2:32pm UTC](https://community.eazybi.com/t/report-based-on-the-issue-epic-value/12540/4 "2023-05-08T14:32:43Z")

</div>

@elyashivg

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

---

<div class="post-metadata">

**Author:** ![elyashivg](https://community.eazybi.com/letter_avatar_proxy/v4/letter/e/f19dbf/32.png) [@elyashivg](https://community.eazybi.com/u/elyashivg)\
**Post date:** [May 9, 2023, 4:47am UTC](https://community.eazybi.com/t/report-based-on-the-issue-epic-value/12540/5 "2023-05-09T04:47:24Z")

</div>

Thanks, it worked!  
I missed something in the configuration of the epic custom field, now it’s working as expected.