您如何组织临时工作文件？
我为几个不同的客户进行了大量的错误修复和实现新功能。 这些客户都将他们的错误、更改请求和新功能请求报告到我们的 Trac 系统中。 有时，这些请求导致我创建一些 SQL 更改脚本，有时需要 Excel 文档或带有测试数据的 Access 数据库、来自客户的 Word 文档等。 许多用于修复一张票证的文件，然后可以在票证关闭时删除。
我通常通过在文件系统中创建文件夹来实现此目的，如下所示：/customerXX/TicketNNNNN，然后将所有内容转储到其中。
您如何组织您的工作文件？ 您是否找到了一些很棒的工具来做到这一点？
I do alot of bugfixing and implementing new features for several different customers. These customers all report their bugs, change requests and new feature request into our Trac system.
Sometimes these requests result in me creating some SQL change scripts, sometimes there are Excel documents or Access databases with testdata, Word documents from the customer and so on. Alot of files that are used to fix one ticket and then can be deletede when the ticket is closed.
I usualy do this by creating folders in the filesystem like this: /customerXX/TicketNNNNN and then just dumping everything in there.
How do you organize your workfiles? Have you found some fantastic tool to do this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我想说，对于与特定票证相关的脚本或文件，最好的办法是将文件附加到问题跟踪软件中的该票证 - 几乎我使用过的所有问题跟踪器都允许您这样做这。 这样，您就可以回顾并 a) 准确查看您所做的事情，以防出现问题，或者 b) 如果问题稍后再次出现，则执行完全相同的操作。 几乎可以肯定，这也是保存包含客户额外信息的文件的最佳位置（或者至少是大多数人会首先查看的位置）。
对于不特定于特定票证的频繁重复使用的脚本，我会在关联的项目中创建一个 script/ 或 bin/ 目录，并将它们保存在那里。
我还有一小部分有用的文件，保存在我的主目录下的 src/misc/ 中，其中包含 SQL 查询之类的内容，用于从 Oracle 中获取可读的“解释”输出等，这些文件不特定于任何特定项目。 这些文件的数量足够小，因此不需要子目录 - 我怀疑如果您最终拥有大量这些文件，其中许多文件可以/应该移动到特定项目或您的问题跟踪系统。
I would say for scripts or files that are related to a particular ticket, the best thing to do would be to attach the file to that ticket in your issue tracking software - almost all issue trackers that I've worked with will allow you to do this. That way, you can look back and a) see exactly what you did in case something goes wrong, or b) do exactly the same thing if the issue comes up again later. That's almost certainly the best place to keep files with extra info from the customer, too (or at least the first place most people will look).
For frequently re-used scripts that aren't specific to a particular ticket, I would create a scripts/ or bin/ directory in the associated project, and keep them in there.
I also have a small handful of useful files that I keep in src/misc/ off my home directory, with things like SQL queries to get readable "explain" output out of Oracle and such, that aren't specific to any particular project. The number of these is small enough that subdirectories aren't necessary, though - I suspect if you ended up with a large number of these files, many of them could/should be moved to specific projects or your issue tracking system.
JIRA 在我的网站上对此非常有帮助。 它支持问题跟踪、文件附件，您可以轻松自定义和分类您的项目和问题。
JIRA has been quite helpful for this at my site. It supports issue tracking, file attachments,and you can easily customize and categorize your projects and issues.
我使用 Fogbugz 并将所有文件添加到案例中。 我相信，无论您使用什么应用程序，重要的是保留此文件以供将来参考。 如果您的错误跟踪工具不允许您附加文件，则将文件添加到版本控制中。
I use Fogbugz and I add all file to the case. I believe that no matter what application you use, The important is to keep this files for future references. If your bug-tracking tool does not let you attach file then add the files to the version control.
我们使用 CaWeb4并发现它非常容易用于我们的错误跟踪。
We use CaWeb4 and find it very easy to use for our bug tracking.