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.
我为很多不同的客户做了很多错误修正和实现新功能。这些客户都将他们的错误,变更请求和新功能请求报告到我们的Trac系统中。有时这些请求会导致我创建一些SQL更改脚本,有时会有Excel文档或带有testdata的Access数据库,来自客户的Word文档等等。很多用于修复一个故障单的文件,然后可以在故障单关闭时删除。
I usualy do this by creating folders in the filesystem like this: /customerXX/TicketNNNNN and then just dumping everything in there.
我通常通过在文件系统中创建文件夹来执行此操作:/ customerXX / TicketNNNNN然后只是将所有内容转储到那里。
How do you organize your workfiles? Have you found some fantastic tool to do this?
你如何组织你的工作文件?你找到了一些很棒的工具吗?
4 个解决方案
#1
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).
我会说对于与特定故障单相关的脚本或文件,最好的办法是将文件附加到问题跟踪软件中的故障单 - 几乎所有与我合作过的问题跟踪器都允许你这样做这个。这样,您可以回顾一下并且a)确切地看到您在出现问题时所做的事情,或者b)如果问题稍后再次出现,则做同样的事情。这几乎肯定是保存来自客户的额外信息文件的最佳位置(或者至少是大多数人会看到的第一个地方)。
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.
对于非特定于特定故障单的频繁重用脚本,我将在关联项目中创建脚本/或bin /目录,并将它们保存在那里。
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.
我还有一些有用的文件,我保存在src / misc / off我的主目录中,使用SQL查询之类的东西可以从Oracle中读取“解释”输出等等,这些文件并不特定于任何特定项目。这些数量足够小,但子目录不是必需的 - 我怀疑如果你最终得到大量这些文件,其中许多可能/应该被移动到特定项目或问题跟踪系统。
#2
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.
JIRA在我的网站上对此非常有帮助。它支持问题跟踪,文件附件,您可以轻松地自定义和分类您的项目和问题。
#3
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.
我使用Fogbugz并将所有文件添加到案例中。我相信无论您使用什么应用程序,重要的是保留此文件以供将来参考。如果您的错误跟踪工具不允许您附加文件,则将文件添加到版本控制。
#1
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).
我会说对于与特定故障单相关的脚本或文件,最好的办法是将文件附加到问题跟踪软件中的故障单 - 几乎所有与我合作过的问题跟踪器都允许你这样做这个。这样,您可以回顾一下并且a)确切地看到您在出现问题时所做的事情,或者b)如果问题稍后再次出现,则做同样的事情。这几乎肯定是保存来自客户的额外信息文件的最佳位置(或者至少是大多数人会看到的第一个地方)。
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.
对于非特定于特定故障单的频繁重用脚本,我将在关联项目中创建脚本/或bin /目录,并将它们保存在那里。
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.
我还有一些有用的文件,我保存在src / misc / off我的主目录中,使用SQL查询之类的东西可以从Oracle中读取“解释”输出等等,这些文件并不特定于任何特定项目。这些数量足够小,但子目录不是必需的 - 我怀疑如果你最终得到大量这些文件,其中许多可能/应该被移动到特定项目或问题跟踪系统。
#2
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.
JIRA在我的网站上对此非常有帮助。它支持问题跟踪,文件附件,您可以轻松地自定义和分类您的项目和问题。
#3
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.
我使用Fogbugz并将所有文件添加到案例中。我相信无论您使用什么应用程序,重要的是保留此文件以供将来参考。如果您的错误跟踪工具不允许您附加文件,则将文件添加到版本控制。
#4
We use CaWeb4 and find it very easy to use for our bug tracking.
我们使用CaWeb4,发现它非常容易用于我们的错误跟踪。