Can we track the Content defects/bugs in jira? if yes, what is the best way to track ?

[Satish Vallurupalli]

Hello Everyone,

I was trying to find out if there is any way to track content defects/bugs in Jira. At my current role, we do a lot of testing to make sure the content and user experience for our application is correct. The current method we use to log and track the defects is through email. For Example: if i find a content defects, i would take a screenshots of all the defects and send them all to the dev for fix through e-mail (a single email can have more than 1 content defect, sometimes there might be 10). I now want to raise the content defects and other non-functional defects in Jira itself in order to track them. I tried creating a bug in Jira and noted down all the content defects in bug description. Please see below for the format i use:

Defects

S.no               Description                                    Browser                 Comments

1                    Button text is wrong                      Chrome                 Unfixed

2                    Lable text is wrong                        Chrome                 Unfixed

If i raise the bugs in above way the Jira will track the above two content defects as one bug because, i have only created one bug and listed all the defects in one bug. If i create a separate bugs for each content defect then there will be a lot of defects assigned to a single story and also more work for Dev and other teams to close them after fix because, most of our defects will need a very small fix.

Could someone give me a suggestion on how to track every content defect in Jira without listing them all in one single bug ?

I appreciate your response!

Thanks!

Satish

[Libu B]

Probably one thing you can consider doing is this - If you are confluence you can record all the observations of the user story in on page, attach details, screenshots etc and then link the confluence in one single bug in Jira. The disadvantage is that you have two places to maintain the bugs - Jira and the confluence. But this works for some teams

[Satish Vallurupalli]

Thank you for your reply!

But how would we track how many content defects we found in each story? If we list all the observations in confluence page and link it to one single bug, Jira will still going to consider all the observations in confluence page as one bug.. I want to track every observations in the story as a bug, even though they all are listed in one page..

for example: Story A has 10 observations but 1 bug.. Story B has 15 observations again with one bug.. but every month end if i want to extract a defect report from jira it should show me as 25 defects were found instead of just showing 2 bugs which we linked each of them to story..

hope this gives more clarity !!

thank you!

satish

[Satish Vallurupalli]

Anyone help please!!!

[Libu B]

Hi Satish,

 If you intend to use Jira for bugs management, you have to choose one of these for your situation  - 

1. Either club all issues as one bug in Jira
2. Or create separate bugs and tag all of them under that particular story

you are looking for a solution in which you don't want multiple bugs but don't want to club all of them together either. This is kind of contradicting each other. 

I would have created separate bugs for each of the observations( you have to make a judgement call on what qualifies as a separate bug ) . If each bug is unique, they are meant to have a separate existence - separate fix, separate lifecycle in Jira etc.

Thanks

Libu