Can HP Quality Center and JIRA coexist for different teams?

Our company is facing a challenge. The QA team relies on HP Quality Center for managing defects and test plans. But the dev team really doesn’t like it. They want to use JIRA for their own task tracking.

I’m worried about how this might work out. In the past, I’ve seen projects where different teams used separate systems for tracking issues. It was a real pain to keep everything in sync.

Has anyone actually tried to make HP Quality Center and JIRA work together smoothly? I’m curious about real experiences. How did you handle the integration? Were there any big problems? Any tips for making it successful?

I’d love to hear some practical advice before we decide what to do. Thanks!

At my previous job, we faced a similar challenge and ended up running both systems concurrently. We defined a strict process for ticket hand-offs, including custom fields in each tool that allowed us to track corresponding issues. This setup required regular audits to resolve any data mismatches, but it also encouraged direct communication between teams. While managing both systems wasn’t perfect, the clearer responsibilities and focused processes helped maintain overall efficiency. It might involve some extra work on reporting and coordination, but with effort, the approach can indeed be successful.

yeah, we’ve done this at my company. it’s not perfect, but it works okay.
we use JIRA for dev stuff and QC for testing. the key is good communication between teams.
we have weekly syncs to make sure nothing falls thru the cracks. it takes some effort, but beats forcing everyone to use a tool they hate.

I’ve been in a similar situation, and it’s definitely manageable with the right approach. We implemented a hybrid system where QA used Quality Center and dev used JIRA. The key was establishing a clear workflow for issue handoffs between teams.

We set up automated syncing between the two systems for critical fields like status and priority. This reduced manual work and discrepancies. We also designated ‘liaison’ roles on each team to oversee cross-system coordination.

One challenge was reporting - it took some effort to get unified metrics across both tools. But overall, letting each team use their preferred tool improved productivity and morale. Just be prepared for some initial integration hurdles and ongoing maintenance.