Jira：多个版本的状态跟踪
我们经常在 JIRA 中报告应用程序多个版本的问题。 但是，对于报告问题的每个版本，不会同时提交对这些问题的修复。 这使得很难跟踪在哪个版本中提交了修复，并且开发人员有时会忘记提交版本的修复。
有没有办法跟踪单独报告但在同一问题中的每个版本的问题状态？ 除了问题的单一状态（仅当所有版本都具有该状态时才更新为状态，即当问题在所有修复版本中都得到解决时设置为“已解决”）之外，我还希望看到每个修复版本的状态不同。
查看 Atlassian 页面后，我发现 JIRA 中存在一个老问题，该问题请求此类功能。 与此相关的论坛讨论建议为每个版本使用一个子任务。 如果有一个插件可以在问题创建和修复版本更新时自动创建子任务，这将是一个很好的解决方案。 有这样的插件吗？
We often have issues reported in JIRA for multiple versions of an application. However the fixes for these issues are not commited at the same time for every version the issue is reported for. This makes it hard to track in which version a fix was commited and developers sometimes forget to commit a fix for a version.
Is there a way to track the status of an issue for each version where it is reported separately, but in the same issue? In addition to a single status for an issue (which is only updated to a status when all versions have that status, i.e. an issue is set to "resolved" when it has been resolved in all fix versions), I would like to see a different status for each fix version.
After looking on the Atlassian-page I found an old issue in their JIRA which requests such functionality. Related to that there are forum discussions which suggest using a sub-task for each version. This would be a good solution if there was a plugin to automatically create the sub-tasks upon issue creation and fix version update. Is there such a plugin?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
你不需要插件。 您可以使用标准 JIRA 功能轻松完成此操作。
只需创建一个记录错误的 JIRA 问题，然后为要修复错误的每个版本创建子任务。我通常使用父问题来跟踪最新（未发布版本）中问题的修复。
在 JIRA 配置中，创建一个名为“Backport”的自定义子任务问题类型可能有助于将这些问题与通用子任务区分开来。
You don't need a plugin. You can easily do this using standard JIRA functionality.
Just create a JIRA issue documenting the bug and then create sub-tasks for each version you want to fix the bug in. I usually use the parent issue to track fixing the issue in the latest (unreleased version).
In your JIRA configuration it might help to create a custom sub-task issue type called "Backport" to distinguish these issues from generic sub-tasks.
我不确定，但如果我没有弄错的话，JIRA 是 Atlassian 产品，因此您最好直接与他们联系并提出您的问题。 我了解这家公司，他们非常好，并且非常愿意回答您的问题。
（我觉得这有资格作为某种答案，尽管它实际上没有帮助）
I'm not sure but if I'm not mistaken JIRA is an Atlassian product and therefore you would do well to contact them with your question directly. I know the company and they are very good like that and would be more than willing to answer your questions.
(I feel that this qualifies as an answer of sorts even though it does not actually help)