i think a lot of organizations, both big and small, have software installed by employees that have used it at a previous engagement/position/opportunity.
as these installed software solutions become more prevalent through the organization, they can no longer be ignored and must be folded in to the organizational technology processes and policies. in this instance, jira may be one of these pieces of software.
you are correct - qc has a great bug/issue tracking system. the product mentioned here allows these two systems to tightly integrate so organizations don't have to spend additional resources on training or licenses (or deal with the backlash of moving everyone to one system).
Thanks for the clarification. I have never worked with a company that used many different bug tracking systems.
I would think that with two different systems, there would be a higher than average potential for duplicate issues logged since you have two different systems and only some of the staff are trained on one system and the others trained on the other system.
My view is that with one system, everyone is trained on one system and maintaining one database would be cheaper that having to deal with multiple databases and systems.