Your project management, bug tracking and time management (if different from the pm tool) should follow the same pattern, no matter what the pattern is. I usually like to do a top down approach: project-application-page (for example: Amazon-Order Entry-Confirmation Page) - if the project/task management, bug and time management all follow the same pattern then you can track tasks to open issues to time spent easily. After the page you enter a short descriptive text of the issue. In the description area, you need to state:
environment (OS/browser)
version being tested
server environment (dev, QA, or production)
the bug (screen captures help greatly)
the expected results (what you expected to happen)
level of issue (show stopper to nice-to-have-but-will-never-get-done)
发布评论
评论（1）
您的项目管理、错误跟踪和时间管理（如果与 pm 工具不同）应该遵循相同的模式，无论模式是什么。 我通常喜欢采用自上而下的方法：项目应用程序页面（例如：亚马逊订单输入确认页面） - 如果项目/任务管理、错误和时间管理都遵循相同的模式，那么您可以跟踪任务开放的问题很容易花费时间。 在该页面之后，您输入问题的简短描述性文本。 在描述区域中，您需要说明：
Your project management, bug tracking and time management (if different from the pm tool) should follow the same pattern, no matter what the pattern is. I usually like to do a top down approach: project-application-page (for example: Amazon-Order Entry-Confirmation Page) - if the project/task management, bug and time management all follow the same pattern then you can track tasks to open issues to time spent easily. After the page you enter a short descriptive text of the issue. In the description area, you need to state: