有没有办法将 JIRA 中的一组问题链接到一个问题？
我们还想开始使用 JIRA 和 GH 进行部署/变更管理。任务/故事的建议工作流程如下：
待办事项 ->打开（在Sprint中添加）->进行中（编码）->已解决（代码已提交，工作已完成）->请求更改（创建一个问题 RFC-x，其中包括 Sprint 中的一组问题）->
从这里我们在新的工作流程中跟踪此 RFC-x：
在测试系统中->正在测试->通过 QA 验证 ->经管理层批准 ->部署到生产 ->由最终用户验证
是否有一种方法可以轻松地将一个 Sprint 或版本中的一组问题与一个问题链接起来？
We would like to start using JIRA with GH for deployment/change management also. The proposed workflow for a Task/Story is as follows:
Backlog -> Open (added in the Sprint) -> In progress (coding) -> Resolved (code committed, work done) -> To Request for Change (Create a issue RFC-x which includes group of issues in the Sprint) ->
From here we track this RFC-x in new workflow:
In test system -> Being tested -> Verified by QA -> Approved by Management -> Deployed to Production -> Verified by end user
Is there a way to link group of issues in one Sprint or Version with an issue easily?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
使用链接是一种方法
您始终可以使用 JIRA 提供的问题链接功能来链接问题
http://confluence.atlassian.com/display/JIRA/Linking+Issues
有一个插件可以帮助您跟踪链接
https://studio.plugins.atlassian.com /wiki/display/ILR/JIRA+问题+链接+报告+插件
或链接层次结构报告
https://plugins.atlassian.com/plugin/details/5003
你甚至可以通过自动执行问题之间的状态转换，它可以提高一个档次。
我们在这里描述了分离规范和任务的概念：http:// www.idalko.com/display/WIC/Separation+of+specifications+and+tasks
另一种方法是将 RFC-x 作为冲刺的一部分，并使用修复程序对所有相关问题进行分组版本。
更改请求允许您在特定版本的上下文中跟踪部署的状态，而无需管理问题和 RFC 之间的链接。
Using links is one approach
You can always link issues using the issue link feature provided by JIRA
http://confluence.atlassian.com/display/JIRA/Linking+Issues
There is a plugin which helps you track the links
https://studio.plugins.atlassian.com/wiki/display/ILR/JIRA+Issue+Links+Report+Plugin
or the links hierarchy report
https://plugins.atlassian.com/plugin/details/5003
You can even take it a notch higher by automating state transitions between issues.
We described the concept of separating specifications and tasks here: http://www.idalko.com/display/WIC/Separation+of+specifications+and+tasks
Another approach would be to include your RFC-x as part of the sprint, and group all the issues which are related using a fix Version.
The request for change allows you to track the status of the deployment, in the context of a certain version without the need to manage the links between the issues and the RFC.
对于分组问题，您可能需要查看 Structure 插件 - 它仍然在不过早期的测试版。希望听到反馈和功能请求。
伊戈尔
For grouping issues, you might want to take a look at the Structure plugin - it's still in early Beta though. Would love to hear feedback and feature requests.
Igor