Defects Under a User Story

[Puneet Gupta]

Hello Experts,

In a project, there are User Stories. QA team is raising defects under the User Stories. For this, there is a sub-task as "Bug", so QA can raise the bugs under a User Story.

There is a ask to show number of Bugs raised under a User Story for last 1 year.

Need guidance on how to achieve this on a Jira Dashboard. It should show , in descending order,

2 Columns as :-

1. Jira Key

2. Bug Count

For example, if a Jira ID, ABC-1234 has 3 sub-tasks as type "Bug" then the report should show

Jira Key	Bug Count
ABC-1234	3

Would appreciate, if the solution can be without any third party gadget.

Thanks

[Danut M _StonikByte_ · Accepted solution]

Hi @Puneet Gupta,

This can be easily done by using Jira's Issue Filter Statistics gadget.

All you have to do is to configure the gadget with a filter that returns the sub-tasks (bugs in your case) and to generate the statistic pa Parent field. 

As a result, you will get a list of parent stories with the count of sub-tasks. The gadget also displays the Percentage of total. 

Danut.  

[pawarsachin84]

Hello @Puneet Gupta ,

Thank you for your question.

I am not sure if this is possible using native Jira. If yes, I would also like to know/understand how it could be possible.

I can suggest here that it can be possible using Atlassian marketplace plugin eazyBI for Jira. Details suggestion as below.

Step 1: Make sure eazyBI is configured to import sub-tasks
Go to Source Data → Edit → Additional options
You need to Enable:  Import sub-tasks

Step 2: In this step you can define a new calculated measure for sub-task Bug countGo to Measures → Add new calculated measure:

You can use Assistant feature to get the calculated measures as per your requirement.

NonZero(
Count(
Filter(
Descendants([Issue].CurrentMember, [Issue].[Issue]),
[Issue].CurrentHierarchyMember.Level.Name = "Sub-task"
AND [Measures].[Issue Type] = "Bug"
AND [Measures].[Issues created] > 0
)
)
)

You can give name something like this - Bug Sub-task Count

Step 3: Now this is the main steps to build the report

Rows:
Use Issue dimension → Epic/User Story level

Columns:
Issue Key (from Issue properties)
Bug Sub-task Count (calculated measure)

Pages (Filters):
Issue Type → filter to User Story or relevant parent types
Time → last 1 year (e.g., “Last 12 months” or custom range)

Step 4: Sort the results
Click on Bug Sub-task Count column
Order by → Descending