# Measure to count number of subtasks of specific issue type per parent issue **URL:** \ **Category:** Questions & Answers\ **Created:** [September 16, 2020, 11:15am UTC](https://community.eazybi.com/t/measure-to-count-number-of-subtasks-of-specific-issue-type-per-parent-issue/5255 "2020-09-16T11:15:46Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![zane.baranovska](https://community.eazybi.com/user_avatar/community.eazybi.com/zane.baranovska/32/7209_2.png) [@zane.baranovska](https://community.eazybi.com/u/zane.baranovska)\ **Post date:** [September 29, 2020, 9:08am UTC](https://community.eazybi.com/t/measure-to-count-number-of-subtasks-of-specific-issue-type-per-parent-issue/5255/2 "2020-09-29T09:08:12Z")
Hi @bar368, The calculated measure “Dependency Subtask” looks for issues with type Dependency Subtask and that also has some subtasks under it. As Dependency subtasks are sub-tasks themselves and can not have any other sub-tasks, the calculated measure returns no data. To make this work, you might want to use the **Sub-task hierarchy** in the Issue dimension. And then you may use measure **Issues create** for the calculation to represent subtasks with a particular issue type. When using a hierarchy, measure values are automatically aggregated from lower hierarchy levels. In this case, the measure “Issues created” would show one for the issue itself plus count of sub-tasks under it. The calculation might look like this: ``` ([Measures].[Issues created], [Issue Type].[Dependency Subtask]) ``` The report might look like in the picture below: ![Sub-tasks with specified issue type](https://community.eazybi.com/uploads/default/original/2X/0/06b31bf8f12c4f10ed40809e4d8dcb86d22e9940.jpeg) Best, Zane / [support@eazyBI.com](mailto:support@eazyBI.com) --- _[View the full topic](https://community.eazybi.com/t/measure-to-count-number-of-subtasks-of-specific-issue-type-per-parent-issue/5255)._