Trac - 为开发人员和开发人员建议的权限级别经理人
我是 Trac 的粉丝，当然，当我只是单独使用它时，我可以给自己完全管理权限的项目。
当有其他开发人员参与时，或者技术不太熟练的经理（或者，就此而言，是设计师而不是硬编码开发人员）时，需要能够跟上正在发生的事情 - 并做事就像添加/更新票证一样，但不会破坏任何东西，那么权限的细粒度性质对于某人的需求来说会变得更加复杂。
您对这些人群（以及其他类似人群）使用什么权限？
I'm a fan of Trac, and of course when I'm just using it for my own, lone, projects I can just give myself full admin rights.
When there are other developers involved, or a not-very-technical manager (or, for that matter someone that is a designer rather than hard-code developer), that needs to be able to keep up with what is happening - and do things like add/update tickets, but not potentially break anything, then the fine-grained nature of the permissions gets to be a little more complicated as to what is required for someone.
What permissions do you use for those groups of people (and other similar ones)?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果可以的话，我通常会避免向用户授予
*_ADMIN权限。 Trac 0.11 通过添加 TICKET_EDIT_DESCRIPTION 使这一切变得更加容易。根据设置和文化，我会将
*_VIEW权限授予经过身份验证的（已登录的每个人）或在宽松的设置中，匿名代码>（每个人，即使没有登录）。我通常会创建一个
developer组，并向该组授予各种权限。然后，您只需将人员添加到组中（或将组添加为用户的权限，同样的事情）。对设计人员、经理、测试人员等执行相同的操作。经理可能需要各种
ROADMAP_*和<代码>MILESTONE_* 权限。我会对REPORT_ADMIN持谨慎态度，除非经理确实了解 SQL。我的老板通常很乐意给我一个他想要的报告的电子表格示例，我会为他准备一份报告。请务必向他们指出，如果他们设置了一个自定义查询来执行他们想要的操作，他们可以为其添加书签（所有内容都在 URL 中），这样他们就可以使用该书签返回到与当前数据完全相同的查询。您可能想让
经过身份验证文件并附加到票证中——通常不会有人注意到错误，您仍然想了解它。如果您足够锁定工作流程权限，您也可以将TICKET_MODIFY分发给更多人，尽管这条路线会需要更多工作。那些您有一定信任的人可能会被授予
TICKET_EDIT_DESCRIPTION，这样他们就可以在忘记开始时修复错误报告格式。如果您有一位首席开发人员，则该个人用户可能应该有 TICKET_ADMIN 来处理添加版本等问题。
I generally avoid giving the
*_ADMINperms to users if I can avoid it. Trac 0.11 makes that a little easier by addingTICKET_EDIT_DESCRIPTION.Depending on the setup and the culture, I'll grant the
*_VIEWpermissions toauthenticated(everyone who has logged in) or in lax setups,anonymous(everyone, even not logged in).I will generally create a
developergroup, grant the various permissions to that group. Then you just add people to the group (or add the group as a permission to the user, same thing). Do the same fordesigner,manager,tester, etc.A manager would want the various
ROADMAP_*andMILESTONE_*permissions. I'd be cautious aboutREPORT_ADMINunless the manager actually knows SQL. My boss is generally happy to give me an example spreadsheet of the report he wants and I'll whip up a report for him. Be sure to point out to them that if they setup a custom query that does what they want, they can bookmark it -- everything is in the URL -- so they can go back to exactly that same query with current data using that bookmark.You'd probably want to let
authenticatedfile and append to tickets--doesn't usually who notices a bug, you still want to know about it. If you lock down the workflow permissions enough, you may be able to give outTICKET_MODIFYto more people as well, though that route will be a bit more work.Those you have some trust in can probably be granted
TICKET_EDIT_DESCRIPTIONso they can fix up their bug report formatting when they forgot to to start with.If you have a lead developer, that individual user should probably have
TICKET_ADMINto deal with adding versions and such.我通常会打开所有
VIEW以及WIKI_CREATE、WIKI_MODIFY、TICKET_CREATE（或TICKET_CREATE_SIMPLE< /code>（如果使用 Simple Ticket 插件）和TICKET_APPEND。对于我相信拥有更多权力的用户，我还将启用
TICKET_MODIFY。对于非技术经理，我还将启用
MILESTONE_ADMIN。对于技术经理，我可能会跳转到TRAC_ADMIN- 但如果太远，至少添加REPORT_ADMIN。通常，我会继续向开发人员授予
TRAC_ADMIN...但如果您不那么信任他们，则可以通过高级用户级别加上TICKET_ADMIN获得上述权限可能就足够了。I typically turn on all the
VIEWs, plusWIKI_CREATE,WIKI_MODIFY,TICKET_CREATE(orTICKET_CREATE_SIMPLEif using the Simple Ticket plugin) andTICKET_APPEND.For users I trust to have a little more power, I'll also turn on
TICKET_MODIFY.For a non-technical manager, I'll also turn on
MILESTONE_ADMIN. For a technical manager, I'm likely to jump toTRAC_ADMIN-- but if that's too far, at least addREPORT_ADMIN.Typically, I'll go ahead and give the developers
TRAC_ADMIN... but if you don't trust them that far, the above permissions through the power user level plusTICKET_ADMINare probably sufficient.