# Issues categorization by development field

**URL:** <https://community.eazybi.com/t/issues-categorization-by-development-field/12266>\
**Category:** Feature Requests\
**Created:** [April 3, 2023, 9:29am UTC](https://community.eazybi.com/t/issues-categorization-by-development-field/12266 "2023-04-03T09:29:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GavinBelson](https://community.eazybi.com/letter_avatar_proxy/v4/letter/g/8e8cbc/32.png) [@GavinBelson](https://community.eazybi.com/u/GavinBelson)\
**Post date:** [April 3, 2023, 9:29am UTC](https://community.eazybi.com/t/issues-categorization-by-development-field/12266/1 "2023-04-03T09:29:19Z")

</div>

**Problem description:**  
There are 2 places, where developers provide input / data for analysis: repo (like github) and “dashboards” (Jira i.e).

EazyBi works perfectly to organise the data from Jira. However as experienced EazyBI user, I can say for sure it does not always consider real use-case scenarios. In example, it’s a common fact, that many development teams create “issues” not only for development purposes, but also for “on duty” tasks, designs, testing, support, etc … There are long list of non-development related tickets, which is extremely hard to organize in a filtered way. Considering, that teams are free to organize their development flow and work culture by using the Jira tool as they want (without centralized policies around fields / states / etc …) it makes the task of differentiating “development” and 'non-development" tickets even harder.

**Feature request:**  
Based on recent statements “[For now, eazyBI does not have a direct import of issue properties, like commits.](https://community.eazybi.com/t/development-field-from-jira/715)” .  
Could we suggest to add an easy solution via “filter” option, which would differentiate all tickets by “Development” property? If field is empty - it has nothing to do with code change, if not - it’s a development task.

---

<div class="post-metadata">

**Author:** ![oskars.laganovskis](https://community.eazybi.com/user_avatar/community.eazybi.com/oskars.laganovskis/32/5902_2.png) [@oskars.laganovskis](https://community.eazybi.com/u/oskars.laganovskis)\
**Post date:** [May 17, 2023, 4:53pm UTC](https://community.eazybi.com/t/issues-categorization-by-development-field/12266/2 "2023-05-17T16:53:42Z")

</div>

Hi @GavinBelson ,  
​  
​The Development section is available for import from Jira as a custom field.  
​You might as well create a new JavaScript calculated custom field dimension to assign issue a category based on the presence of data within that custom field.  
​  
Please read about defining new customfield ​here - [New calculated fields](https://docs.eazybi.com/eazybi/data-import/data-from-jira/jira-custom-fields/new-calculated-fields).  
​  
​The primitive code might be as follows.  
​

```auto
if (issue.fields.customfield_NNNNN)
 {return "Development"} 
else {return "Administrative"}

```

You need to replace the NNNNN with the customfield ID for the Development on your instance.

​Regards,  
​Oskars / [support@eazyBI.com](mailto:support@eazyBI.com)