The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

how to check the defects raised under a specific user story

liu.ping
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 6, 2019

1.the structure of project is

 

for each sprint. there are some stories created, with test case linked to the stories as "is child of". the defect linked to the test cases as"blocks". 

 

2.there is one field in the story "dev owner" to indicate the responsible dev leaders. 

 

3. if we want to gene a report to summarize for each dev owner how many defect  has been raised under the specific story. 

 

how to do it. is the report can be created via board,dashboard,structure,confluence or any other way?thanks for your guide in advance. 

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
liu.ping
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 10, 2019

thanks for your reply,will try to the free use for custom report. 

0 votes
Evan Golden {VisualScript}
Atlassian Partner
November 6, 2019

You can use the VisualScript for Jira marketplace application.  There is a solution that is designed for issue dependencies, and is completely customizable.

https://www.visualscript.com/issue-dependency/issue-dependency-report-jira-confluence.htm

With this, you can have the same grid as shown in the link above, show the epic on the left, the story in the middle, and to the right, only the defects that are assigned to the dev owner, and linked to test cases in the story.

This would all be in a single Jira dashboard gadget.  When you run it, it would ask you for 2 parameters.  1) the issue key of the story and 2) the value for Dev Owner.  The information would automatically update on refresh.

I hope this helps.