是否可以将 Mercurial 提交与 JIRA 或 FishEye（通过 TortoiseHg 或 hg）集成？
有没有办法将每个 HG 提交链接到特定的错误跟踪问题？
例如，从 TortoiseHg 提交时显示一个下拉列表，并将所有活跃的 JIRA 问题分配给当前用户（类似于 适用于 JIRA 的 TortoiseSVN 插件）。也许下拉菜单太花哨了，但是有没有类似于 TortoiseSVN 的东西至少可以与错误跟踪系统/问题跟踪器集成，即提交窗口右上角的文本框，您可以在其中输入问题编号？在THG中似乎找不到类似的东西。
我在TortoiseHg手册中发现了一些有前途的配置，但找到了它们非常原始...想法/想法/解决方法？
Is there a way to link every HG commit to a specific bug tracking issue?
For example, show a drop down when committing from TortoiseHg with all active JIRA issues assigned to the current user (similar to the TortoiseSVN Plugin for JIRA). Maybe a drop down is too fancy, but is there something similar to the TortoiseSVN Integration with Bug Tracking Systems / Issue Trackers available at least, i.e. a text box in the top right of the commit window where you can enter the issue number? Can't seem to find anything similar in THG.
I found some promising configurations in the TortoiseHg manual but find them very primitive... Ideas/thoughts/workarounds?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
现在就在那里。
转到
File/Settings/，然后选择global settings选项卡或存储库的选项卡。在
问题跟踪下添加适当的正则表达式和链接。例如\b\w{3,7}-\d+\b和http://your.jira.server.com:8080/browse/{0}。请参阅http://caraulean.com/blog/2011/09/ 09/tortoisehg-and-jira-integrationthe-lightweight-option/
It's there now.
Go to
File/Settings/, then choose either theglobal settingstab or the repository's one.Under
Issue Trackingadd the appropriate regex and link. For example\b\w{3,7}-\d+\bandhttp://your.jira.server.com:8080/browse/{0}.See http://caraulean.com/blog/2011/09/09/tortoisehg-and-jira-integrationthe-lightweight-option/
仅供参考，TortoiseHg 团队大约两周前解决了这个问题。它目前处于夜间构建中，但很可能会进入下一个真正的版本。
fyi, this was addressed by the TortoiseHg team about two weeks ago. it is currently in nightly builds, but will likely make it into the next real release.
答案是否定的——TortoiseHg 不支持您要求的功能。该功能已输入到TortoiseHg的错误跟踪器中，所以我建议您在 Bitbucket 上注册并“关注”那里的问题。
The answer is no -- TortoiseHg does not support the features you ask for. The feature has already been entered into TortoiseHg's bug tracker, so I suggest you sign up at Bitbucket and "follow" the issue there.