blocks|key|2722774|text|你需要在质量中心和JIRA之间架起一座“桥梁”。JIRA具有允许您构建和/或定制这些接口的API。我曾与Orasi合作过，它有一座桥(不知道成本)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2722775|http://www.orasi.com/products/Pages/Orasi.aspx|offset|length|2722776|http://www.beteoblog.com/2009/01/21/integrating-jira-and-the-hp-quality-center/|2722777|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|1A|0|0|0|27|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|H|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]|O|$5|K|L|M|A|$N|G]]]]

You will need a 'bridge' between Quality Center and JIRA. JIRA has APIs to allow you to build and/or customize these interfaces. I have worked with Orasi, which has a bridge (no idea on the cost).

<a href="http://www.orasi.com/products/Pages/Orasi.aspx" rel="nofollow noreferrer">http://www.orasi.com/products/Pages/Orasi.aspx</a>

<a href="http://www.beteoblog.com/2009/01/21/integrating-jira-and-the-hp-quality-center/" rel="nofollow noreferrer">http://www.beteoblog.com/2009/01/21/integrating-jira-and-the-hp-quality-center/</a>

blocks|key|1626679|text|QC有很多很多Jira没有的特性。即使列出它们，也会使这篇文章大错特错。我在QC工作了两年多，虽然我不是它的狂热粉丝，但我必须承认，所有这些QC功能允许它支持几乎所有的QA活动(如果工具和测试过程在组织中得到充分和适当的实现)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1626680|至于这个问题，弗兰克，你是对的，保持QC缺陷和Jira+Bugs同步可能是一件痛苦的事情。我建议：|1626681|a)查看Jira+(link)的orasi插件|offset|length|1626682|b)查看Jira+(link)的Go2Group插件|1626683|c)为Jira编写自己的插件|1626684|不幸的是，在我的公司，这三个解决方案都还没有实现，所以我可以说很多关于它们的事情。|1626685|entityMap|0|LINK|mutability|MUTABLE|url|https://plugins.atlassian.com/plugin/details/26467|1|https://plugins.atlassian.com/plugin/details/8129^0|0|0|9|6|0|0|9|6|1|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@$F|10|G|11|1|12]]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@$F|14|G|15|1|16]]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]]]

QC has many, many, many features that are not in Jira. It would make this post horribly wrong even to list them. I've been working with QC for over 2 years, and although I'm not big fan of it, I must admit, that all those QC features allows it to support almost every QA activity (if tool and testing process are fully and properly implemented in organization). 

As for the question, frankadelic you are right, maintaining QC defects and Jira Bugs in sync can be a pain. I would suggest: 
a) look at orasi plugin for Jira <a href="https://plugins.atlassian.com/plugin/details/26467" rel="nofollow noreferrer">(link)</a> 
b) look at Go2Group plugin for Jira <a href="https://plugins.atlassian.com/plugin/details/8129" rel="nofollow noreferrer">(link)</a> 
c) write your own plugin for Jira 

Unfortunately in my company none of those 3 solutions were implemented yet, so I can;' say much about them.

blocks|key|1622901|text|首先，我会找出是惯性还是特定的功能让他们认为他们需要使用不同的工具来完成非常相似的任务。改变工具通常比改变人们的思维方式更容易:-)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1622902|~哑光|1622903|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I'd start by finding out whether it is inertia or specific functionality that makes them think they need to use different tools for very similar tasks. Changing tools is often easier than changing the way people think :-)

~Matt

blocks|key|4131013|text|我知道有一个Jira-to-Quality+Center桥可以买到，但没有使用经验。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4131014|我们的QA小组使用Quality+Center编写和执行测试用例，但由于我们的开发小组使用Jira进行错误跟踪，因此QA也使用Jira。|4131015|从QA的角度来看，缺点是在bug和发现它的测试用例之间没有自动连接，用户必须手动粘贴测试用例的路径。正如可以预期的那样，有时这一点会被忽略。|4131016|我工作过的项目中，开发人员和QA都使用Quality+Center来跟踪错误。我觉得它在bug和发现它的特定测试之间提供了更好的联系。|4131017|我不知道Jira为开发端提供了什么优势，但我还没有遇到过喜欢QC的开发人员。|4131018|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I know that there is a Jira-to-Quality Center bridge that can be purchased, but have no experience with using it.

Our QA group uses Quality Center for writing and executing test cases, but since our development group uses Jira for bug tracking, QA also uses Jira. 

The disadvantage, from a QA perspective, is that there is no automatic connection between a bug and the test cases that discovered it, users must manually paste the path to the test case. As can be expected, sometimes this gets left out of the ticket.

I have worked on projects where Quality Center was used by both dev and QA for bug tracking. I felt like it provided a better connection between the bug and the specific testing that discovered it. 

I don't know what advantage Jira provides to the development side, but I've yet to meet a developer that likes QC.

blocks|key|4131045|text|我已经尝试了惠普QC连接器为Jira，它有一个很好的用户界面和报告，我们已经同步，与其他产品相比，它是便宜的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4131046|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have tried HP QC connector for Jira, and it has a nice UI and report for what we have synchronized, compared with other products, it's cheap.

Our QA team uses HP Quality Center for defect tracking, test plans, etc.

The dev team really detests Quality Center and wants to use JIRA for internal task tracking.
Can these two systems work seamlessly together?

I have worked on projects where 2 teams used separate issue-tracking systems and keeping them in sync was a major headache.

Anyone have real-world experience integrating Quality Center and JIRA?

QA team uses HP Quality Center, Dev team wants to use JIRA -- will this work?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们的QA团队使用HP Quality Center进行缺陷跟踪、测试计划等。开发团队非常讨厌Quality Center，并希望使用JIRA进行内部任务跟踪。这两个系统可以无缝地协同工作吗？我曾经在两个团队使用独立的问题跟踪系统的项目中工作，保持他们的同步是一个令人头疼的问题。有人有集成质量中心和JIRA的实际经验吗？

问QA团队使用HP Quality Center，开发团队希望使用JIRA --这行得通吗？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问QA团队使用HP Quality Center，开发团队希望使用JIRA --这行得通吗？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问QA团队使用HP Quality Center，开发团队希望使用JIRA --这行得通吗？
EN