Best way to track defects from Automation testing and manual testing separately in JIRA?

Question

I am looking for best way to keep track of defects identified in automation testing and manual testing in JIRA. I would like to use this metrics to analyse the behavior of functional and regression automation scripts. Please share your thoughts.

Thanks

Answer 1

In our case - if automation tests finds a defect, we add those defects to the automatically into Jira and in the bug summary we add FOUND BY AUTOTESTING.! and also put a label.

In the bug description add the process of the test in order to reproduce the steps and then if possible - to add a screenshot.

Answer 2

The quickest way to do this would be to use tagging of the defects. You can then create a filter and/or a dashboard element to monitor that filter.

Here is an article on using tags in JIRA -

https://confluence.atlassian.com/doc/add-remove-and-search-for-labels-136419.html

Answer 3

In my team we track tickets deviation by using two things:

1. Jira filters subscription for cases where we need plain(to one person/lead/manager) notification, but without fields analysis
   • https://confluence.atlassian.com/jira064/receiving-search-results-via-email-720416706.html?_ga=2.134616433.1430628443.1592459825-259335427.1591590509
   • https://confluence.atlassian.com/jira064/receiving-search-results-via-email-720416706.html?_ga=2.134616433.1430628443.1592459825-259335427.1591590509
2. https://github.com/dgroup/lazylead for cases where we need automatically check ticket fields, comments, links and alert corresponding person, assignee or reporter. Please note that i'm author of https://github.com/dgroup/lazylead app.

Answer 4

There are a couple of ways to differentiate those tickets:

1. Simplest way to track this is by JIRA labels
2. You can have a different issue type for the bug that is logged/found by automation
3. You can maintain EPIC (Release-wise) and log all the issue found by automation in a particular release under that epic.