Bugzilla 到 JIRA 的迁移：将整个 bugzilla db->产品->组件层次结构映射到 JIRA 的明确方法？
我们的组织现在正在使用 JIRA，我希望将包含大约 1500 个条目的 bugzilla 数据库迁移到其中。
我知道 JIRA 有项目，但没有其中的部门。
我坚定的偏好是为这个 bugzilla 数据库创建一个 JIRA 项目，然后 bugzilla 产品和组件都包含在其中。这使数据库保持独立，并且不会暴露（因此过度拥挤）JIRA 中的顶级项目列表与我部门特定的 bugzilla 产品。
鉴于 bugzilla 中的层次结构与 JIRA 中的层次结构没有直接的一对一映射，我会考虑使用自定义字段来实现 JIRA 中的 bugzilla 产品和组件级别，并构建一个自定义 JIRA 网页，其表单将自动- 一旦选择了产品，就呈现正确的组件（就像 bugzilla 中的情况一样）。我知道 JIRA 可以通过 API 进行高度定制，但我还不知道细节 - 这是我需要建议的地方。
我尝试过一些研究，但这还没有定论： http://forums.atlassian.com/ message.jspa?messageID=257299050
所以总结一下：
- 自定义字段是 明确/可接受的表示方式 bugzilla 产品及其 JIRA 中的组件。有什么缺点吗？
- 如果是这样，是否有示例，建议如何实施这一点 - 以及 自动建议的形式 组件，一旦产品 已选择。
- 如果没有，那么使用自定义字段的替代方法是什么？
Our organisation is now using JIRA and I'm looking to migrate a bugzilla database of about 1500 entries into it.
I'm aware that JIRA has projects but not of divisions within this.
My firm preference is to have one JIRA project for this bugzilla database and the bugzilla products then components all contained within this. This keeps the database self contained and doesn't expose (and therefore overcrowd) the top level project list in JIRA with my department specific bugzilla products.
Given that there is not a straight one-to-one mapping of the hierachy in bugzilla with that in JIRA, I would consider custom fields to implement the bugzilla product and component levels in JIRA and build a custom JIRA webpage with a form that would auto-present the correct components once a product is selected (much as is the case in the bugzilla). I'm aware that JIRA is highly customisable with APIs but I don't know the detail yet - this is where I would need advice.
I've attempted some research but this is inconclusive: http://forums.atlassian.com/message.jspa?messageID=257299050
So in summary:
- Is custom fields the
definitive/accepted way to represent
bugzilla products and their
components in JIRA. Any disadvantages? - If so, are there examples, suggest as to how to implement this - and
the form that auto-suggests the
components, once a product is
selected. - If not, then what would be the alternative to using custom fields?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
通过将 Bugzilla 产品等同于 JIRA 项目，您可以节省大量工作，这样您就可以将组件直接从 Bugzilla 映射到 JIRA。然后，您可以免费获得每个项目的组件列表的自动建议，而不必进行大量自定义。
我在五个不同的组织中使用过 JIRA，并且始终将每个团队或部门映射到一个或多个 JIRA 项目。每个 JIRA 项目都可以有自己的版本、发布日期以及组件，这似乎与 Bugzilla 产品自然匹配。
You could save yourself a lot of work by equating the Bugzilla product to JIRA projects, so that you could map the components directly from Bugzilla to JIRA. You'd then get the auto-suggestion of the component list for each project for free rather than having to do a bunch of customization.
I've used JIRA in five different organizations and have always mapped each team or division to one or more JIRA projects. Each JIRA project can then have its own versions and release dates as well as components, which seems like a natural match to Bugzilla products.