内部错误跟踪票 - Redmine、Trac 或 JIRA
我一直在考虑设置Redmine，Trac，或 JIRA 来跟踪问题。我希望能够让我的开发团队创建客户从未看到的内部票证，而客户可以创建/编辑内部团队看到的票证。
在 Trac 文档中，您可以设置创建或查看票证的权限，但它并没有似乎不允许只查看某些门票。 Trac 细粒度权限可能有可能，但似乎并非如此。
Redmine 文档提到：
定义您自己的角色并单击即可设置其权限
但似乎没有粒度级别。
来自 JIRA 文档：
目前 JIRA 只能 支持项目级别的安全性或 问题级别。 目前没有 提供现场级安全性。
根据这个问题，Redmine不支持内部票证，所以你必须使用多个项目。我不希望出现这样的情况：我必须创建多个项目 - 一个内部项目，一个外部项目，并将外部票证带入内部存储库。看来这会导致不必要的开销，并且不可避免地，项目不会同步。是否有任何方法可以使用这些产品（如果不在核心产品本身中，则可能通过插件）来指定这些权限，或者简化具有不同用户和权限但仍必须共享信息的两个项目？
I've been looking at setting up Redmine, Trac, or JIRA to track issues. I want to be able to have my development team create internal tickets that are never seen by clients, while clients can create/edit tickets that are seen by the internal team.
From the Trac documentation, you can set permissions to create or view tickets, but it doesn't seem to allow for viewing only certain tickets. It may be possible with Trac Fine Grained Permissions, but doesn't appear so.
The Redmine documentation mentions:
Define your own roles and set their permissions in a click
but doesn't appear to have the level of granularity.
From the JIRA documentation:
At the moment JIRA is only able to
support security at a project level or
issue level. Currently there is no
field level security available.
According to this question, Redmine doesn't support internal tickets, so you would have to use multiple projects. I don't want a situation where I would have to create multiple projects - one internal, one external and have the external tickets brought into the internal repository. It seems as this would lead to unnecessary overhead and inevitably, the projects wouldn't be in sync. Is there any way with any of these products (possibly through a plug-in if not in the core product itself) to specify these permissions, or simplify having two projects with different users and permissions that must still share information?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
在redmine中我们只是使用子项目进行外部访问。
子项目的所有票证对于开发人员具有完全访问权限的父项目也是可见的...
工作没有问题
In redmine we just use sub-projects for external access.
All ticket of the sub project are also visible to the parent project where the developpers have full access...
Works with no problems
Jira 有相当多的可见性控制，我不会这么快就忽略它。
这是我发现的一个谈论它的链接：
https://confluence.atlassian.com/display/JIRA/Configuring+问题级别+安全性
您将有一个项目，然后您可以使用问题类型来向公众隐藏某些内容。我相信，您也可以在内部或公开发表评论。
Jira has quite a bit of visiblity control, I wouldn't dismiss it so quickly.
Here is a link I found that talks about it:
https://confluence.atlassian.com/display/JIRA/Configuring+Issue-level+Security
You would have one project and then you can use issue types to hide certain things from the public. You can also make comments internal or public, I believe.
Jira 有“问题安全级别”，允许您做您想做的事情（请参阅另一个答案中引用的链接）。
Jira has "Issue Security Levels" that allow you to do what you want (see link quoted in another answer).
听起来您想要 Trac 的 私人门票插件。这样您就可以使客户只能看到他们报告的工单，而看不到其他客户报告的工单。
Sounds like you want the private tickets plugin for Trac. This will allow you to make it so that clients can only see the tickets they have reported, and not tickets other clients have reported.
CounterSoft Gemini 可以满足您的需求。
在您设置外部项目参与者时可以帮助您的白皮书：
http://countersoft.com/downloads/whitepapers/Implementing_an_Issue_Management_Platform.pdf
CounterSoft Gemini does what you need.
Whitepaper that may help you as you set up external project participants:
http://countersoft.com/downloads/whitepapers/Implementing_an_Issue_Management_Platform.pdf
Redmine 1.2 有“私人”门票。
Redmine 1.2 has "private" tickets.
JIRA 是您最好的选择。我们广泛使用它，可以创建具有显着粒度的内部票证或私人票证，但不可否认的是，达不到现场级别。您可以编写一个插件来实现这一目标。
快速阅读有关比较的博客文章：http://blog.pineywoodstech.com/index.php/2011/12/jira-issue-tracking-for-the-masses/
JIRA is your best bet. We use it extensively and can create internal tickets or private tickets with significant granularity, but admittedly not to the field level. You could possibly write a plug-in to achieve that.
Have a quick read of a blog post on the comparison: http://blog.pineywoodstech.com/index.php/2011/12/jira-issue-tracking-for-the-masses/