# Generate bar chart based Jira issue Creation Hours

**URL:** <https://community.eazybi.com/t/generate-bar-chart-based-jira-issue-creation-hours/8675>\
**Category:** Questions & Answers\
**Tags:** jira\
**Created:** [January 24, 2022, 4:58pm UTC](https://community.eazybi.com/t/generate-bar-chart-based-jira-issue-creation-hours/8675 "2022-01-24T16:58:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmenconi](https://community.eazybi.com/user_avatar/community.eazybi.com/dmenconi/32/6310_2.png) [@dmenconi](https://community.eazybi.com/u/dmenconi)\
**Post date:** [January 24, 2022, 4:58pm UTC](https://community.eazybi.com/t/generate-bar-chart-based-jira-issue-creation-hours/8675/1 "2022-01-24T16:58:06Z")

</div>

I’m fairly new to EazyBi and very new to this forum so be gentle… 😀

We want to create a report about Jira tickets that has a bar chart for each hour of the day and shows how many tickets are created in that hour. This would be an aggregate over some period of weeks or months.

The goal is to determine the hourly load so that we can staff correctly – we want more people on when more tickets are created.

Seems like a THING that people would need but I can’t see a way to do it in EazyBi.

Thanks  
Dave

---

<div class="post-metadata">

**Author:** ![daina.tupule](https://community.eazybi.com/user_avatar/community.eazybi.com/daina.tupule/32/8838_2.png) [@daina.tupule](https://community.eazybi.com/u/daina.tupule)\
**Post date:** [January 28, 2022, 3:26pm UTC](https://community.eazybi.com/t/generate-bar-chart-based-jira-issue-creation-hours/8675/2 "2022-01-28T15:26:12Z")

</div>

Welcome to the community.

eazyBI imports daily values by default. However, you can extend this by defining a new dimension during import to get hourly values. Then you can use this dimension in reports and eazyBI will split values by issue created hour.

See this community topic on how to achieve this:

> [@Issues created out of office hours](https://community.eazybi.com/t/issues-created-out-of-office-hours/180):
>
> There are a couple of ways how to calculate the number of issues created outside office hours. First, let us look at an example to find issues created before 9 am or after 6 pm in eazyBI. To do this, you can define a created hour breakdown dimension with [advanced settings](https://docs.eazybi.com/eazybijira/data-import/custom-fields/advanced-settings-for-custom-fields): [jira.customfield\_hodc] name = "Hour of Day Created" data\_type = "integer" dimension = true javascript\_code = ''' issue.fields.customfield\_hodc = parseInt(issue.fields.created.match(/T(\d\d):/)[1]); ''' Further, select the…

It goes deeper in out-of-hours reporting, but you can use it as a basis to get an overview of how an issue creation is split during the day.

Daina / [support@eazybi.com](mailto:support@eazybi.com)

---

<div class="post-metadata">

**Author:** ![dmenconi](https://community.eazybi.com/user_avatar/community.eazybi.com/dmenconi/32/6310_2.png) [@dmenconi](https://community.eazybi.com/u/dmenconi)\
**Post date:** [February 1, 2022, 7:47pm UTC](https://community.eazybi.com/t/generate-bar-chart-based-jira-issue-creation-hours/8675/3 "2022-02-01T19:47:36Z")

</div>

That goes pretty deep but it worked! I had to have some help from a colleague but that was great! THANK YOU!

I did notice that some tickets are in the “wrong” bucket. That is, they return the wrong number compared to their creation date. It’s weird because there will be 4 issues in, say, hour 5 that belong there and 4 more that belong in hour 4.

For the use case, this seems acceptable since the errors are just a few percent of the total and never off by more than an hour (recall that we’re trying to scale our staffing so close enough if good enough).

But can you give me any hints about what it might be just so I can learn about it?

Thanks again,  
Dave