Hei, we want to sum up how dev working with each task or bug in a company. That means, how many bugs or regressions QA found with in every task, is it possible to do it on jira?
Hi @Inesa Virsilaite
The approach depends on the way you track regressions.
Eg. if you have a "Bug" that was Merged and is now live, now if you create a new ticket that is a regression of this bug, how do you show the linkage between the two?
Also, you mentioned "regressions QA finds in every Task", by this I assume you are talking about a test run? or a Smoke test. Here the same logic would follow, if you create a new BUG for a failed test case, do you link the two? Or what other approach do you follow to display that "BUG B" is a regression due to "BUG A" .
Suggestion : If you can implement a process where your team members link the issues with "is a Regression of" correctly then https://support.atlassian.com/jira-service-management-cloud/docs/jql-functions/#linkedIssues-- this JQL might be of help to you.
It looks like you're new here. Sign in or register to get started.
