# Aggregate more than 1000 issues error with issues created measures

**URL:** <https://community.eazybi.com/t/aggregate-more-than-1000-issues-error-with-issues-created-measures/10509>\
**Category:** Questions & Answers\
**Created:** [September 8, 2022, 8:27am UTC](https://community.eazybi.com/t/aggregate-more-than-1000-issues-error-with-issues-created-measures/10509 "2022-09-08T08:27:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![XavierH](https://community.eazybi.com/letter_avatar_proxy/v4/letter/x/ebca7d/32.png) [@XavierH](https://community.eazybi.com/u/XavierH)\
**Post date:** [September 8, 2022, 8:27am UTC](https://community.eazybi.com/t/aggregate-more-than-1000-issues-error-with-issues-created-measures/10509/1 "2022-09-08T08:27:27Z")

</div>

I used to make aggregate of issues using

"agreggate ( Filter (…))

it’s working but i got an error for the whole groupe when using basic measure like issue created.

Why ??

 ![image](https://community.eazybi.com/uploads/default/original/2X/0/09685b6737faf1e5aaeee1ecde9307987e4443bd.png)

---

<div class="post-metadata">

**Author:** ![gerda.grantina](https://community.eazybi.com/user_avatar/community.eazybi.com/gerda.grantina/32/1994_2.png) [@gerda.grantina](https://community.eazybi.com/u/gerda.grantina)\
**Post date:** [September 19, 2022, 9:48am UTC](https://community.eazybi.com/t/aggregate-more-than-1000-issues-error-with-issues-created-measures/10509/2 "2022-09-19T09:48:19Z")

</div>

Hi @XavierH ,  
The problem you are encountering is caused by the high number of issues going into the calculated members “US/Enabler/Bugs/Task” and “Feat/EF”. The Mondrian engine has some limitations, and 1000 members for aggregation is one of these.

A better solution would be to precalculate (group) issues with specific text pattern in a summary and import this grouping as a new dimension using a [Javascript calculated custom fields](https://docs.eazybi.com/eazybi/data-import/data-from-jira/jira-custom-fields/javascript-calculated-custom-fields).  
See a similar use case here with a JavaScript code example:

> [@Filter open issue by summary](https://community.eazybi.com/t/filter-open-issue-by-summary/6046/2):
>
> Hi @karim , I don’t recommend defining such calculated members in the Issue dimension. They are a performance risk. If you don’t have the option to create a new custom field in Jira, define a new JavaScript calculated custom field in eazyBI. See more details on how to do that here - [JavaScript calculated custom fields - eazyBI for Jira](https://docs.eazybi.com/eazybijira/data-import/custom-fields/javascript-calculated-custom-fields). Add parameters similar to the one below to your eazyBI advanced settings: [jira.customfield\_developer\_issue] name = "Issue summary Developer" data\_type = "st…

best,  
Gerda // [support@eazyBI.com](mailto:support@eazyBI.com)