Jira issue workflow for code implementation and bug management

Question

I have just started to work in a company that uses the same Jira Issue workflow to manage development tasks and bugs.

I must confess that during the last 5 years I was working a little bit outside the QA scope. When I used to work as a proper QA the customers that I worked for were using ALMs to manage defects, or at least they were dealing with defects in a separated view from the implementation tasks. So, I was trying to understand which is the best approach while using JIRA and its issues workflow to manage defects. I already created (sse the imag below) a separated workflow for defects but I am still confused if it would make sense to decouple it from the Implementation workflow (that currently, at the company also applies to defects).

I would like to ask for your opinion on that. What do you think and what do you usually see when it comes to use JIRA as a solo tool to manage defects and development?

Thanks in advance!

Answer 1

I have seen both approaches used and can see advantages and disadvantages to them.

Using the same workflow for bugs and requirements simplifies the process and makes it easier to gather metrics (the same stages and transitions exist so can be tracked in a similar way).

Customising the workflow for bugs (and other issue types) has the advantage that it can better reflect the way the team works. It also tends to make tracking the status of bugs more effective.

My personal opinion is that the best approach is to keep the workflows as similar as possible, but allow differences where they are significant for tracking and usability.