At my company we use JIRA for new feature requests and then the QA department logs any bugs/defects in Quality Center. I find Quality Center to be very non-userfriendly as it requires IE because it uses ActiveX.Is this a common practice to use separate trackers for feature requests and defects? Is there any advantage to having separate trackers?
Separate trackers for features and defects?
issue tracking;qa
Hey.I actually have the same setup at my work. I must say it doesn't have sense, if you use QC only to store defects. If you need bug tracking, you can stick with Jira. But you must understand that QC is tool dedicated for QA and it does much more. So it has sense to have Jira and QC if you (I mean QA at your work ) use all/most of QC features and you have Jira plugin that synchronizes defects between QC and Jira (I know about two plugins for Jira like that).[end of answer]  If you're thinking 'but why the fck QA needs this stupid tool?' let me uncover a bit about QC for you.Please understand that although both provide bug tracking capabilities, they have very different target and purpose. I assume that most people (programmers) here know Jira, so I will uncover a bit about QC for you:  It is Test Management system. It looks at (almost) all possible aspects of QA and is specialized only for that.  It has Management module, where you can define software releases, cycles, provide their descriptions, documents, links, etc..It has Requirements module, where you can store requirements with descriptions, associated documents, links. It has Business Components module, where you can define sort of 'areas' of application, define they expected behavior, expected input and output. Later you can combine those components into business process with flow of actions, inputs, outputs, expected behaviour - nice setup to link with proper test.It has Test Plan module, where you define tests, their description, associated documents, test steps, expected results...  It has Test Resources where you can define additional resources for your testsIt has Test Lab module where you group tests into Test Sets, and where you run them. This 'runner' gathers from you actual results, screenshots, Defects...   It Has Defects module which is database of bugs with their descriptions etc. Additionally you define different roles and Defect Life Cycle so you can manage them the way you want.  It has Dashboard module where you can display tracked information about testing. Between all those modules in 2-8 you can setup links, if you do so QC provide you Traceability Matrix between Requirments, Tests, Defects, Test Execution, Software Release, and so on...It has Document generator which allows you to generate various 9also user-defined0 reports based on all information in QC (I say all as it has built in module that allows you to querry QC database and put info into report automatically). It has integration with QuickTestPro 9and some other tools) which allows you to upload to the server automated tests, and additionally it allows you to run them from server on remote machines. You can schedule sets of tests to run on different machines and have results reported directly to QC database.  P.S. It is a big tool, used properly works great, otherwise it sucks