TFS 中的错误、问题和任务之间有什么区别

发布于 2024-10-20 05:54:28 字数 1704 浏览 2 评论 0原文

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

吻泪 2024-10-27 05:54:28

对于 Scrum TFS 流程模板

  • 错误 - 现有的任何问题功能,或缺少功能。代码或需求中的缺陷,非设计错误。

  • 问题(障碍) - 任何可能阻碍开发过程的问题,例如:您确定为依赖项的第三方驱动程序没有按时发布,因此这是您开发过程中的一个问题。

  • 任务 - 任何工作它被计划为项目开发的一部分,无论是由于错误、问题或需求,包括需求分析或开发或测试。等等

敏捷 TFS 流程模板

  • 错误 - 错误通信您的团队正在开发的代码中存在潜在问题。

  • 问题 - 事件或原因可能会延迟发货。

  • 任务 - 任务进行通信需要做一些工作。每个团队成员都可以定义任务来代表他们需要完成的工作。

For the Scrum TFS Process Template

  • Bug- Any problem in existing functionality, or missing functionality. Defect in code or requirement, error which is not designed to be.

  • Issue (Impediment)- Any problem which might block the development process, example : a third party driver you identified as dependency is not releasing on time, so it is an issue in your development process.

  • Task- Any work which is planned as part of development of your project, either as result of bug, or issue or requirements, including requirement analysis or development, or testing. etc.

For the Agile TFS Process Template

  • Bug- A bug communicates that a potential problem exists in the code that your team is developing.

  • Issue- An event or cause that may delay shipping.

  • Task- A task communicates the need to do some work. Each team member can define tasks to represent the work that they need to accomplish.

烟若柳尘 2024-10-27 05:54:28

以前我们用TFS的时候。

问题 - 是软件用户报告的需要调查的问题。这可能是代码错误或需求更改(在发出更改请求之前)

BUG - 是开发人员确认的“代码中”问题。可以提供可能的原因和解决方法等信息。可以标记为固定并链接到源代码检查。

任务 - 是交给人们完成的工作项目。比如需要完成的某个功能。如果是编程任务,可以链接到源代码签入。

更新

请参阅下面的评论。请记住,以有利于您的团队的方式使用该系统。每个人的工作方式都不同。

问题 - 涵盖可能需要一些工作或调查的项目的所有内容。这不一定是代码的问题,但它为调查提供了一个起点。如果提出问题,需要更改项目,则可能会导致错误或任务。

When we used TFS in the past.

ISSUE - Is a problem reported by a user of the software that requires investigation. This could be a code bug or a requirement change (prior to it been made a change request)

BUG - Is a problem "in the code" confirmed by a developer. Information can be provided like possible causes and workarounds. Can be marked as fixed and link to source code check ins.

TASK - Is a work item that is given to people to complete. Such as a feature that needs to be completed. If it is a programming task, it can be linked to source code check ins.

Update

See comment below. Just remember, use the system in a way that benefits your team. Everyone works differently.

ISSUE - Covers everything about the project which may require some work or investigation. It is not necessarily an issue with the code, but it creates a stating point for investigation. If an issue is raised, which requires a change to the project it may lead to a bug or task.

菩提树下叶撕阳。 2024-10-27 05:54:28

MSF Agile 工作项类型

MSF Agile 包含以下工作项类型:

  • Bug。代表您的应用程序中的问题或潜在问题。
  • 风险。表示可能对您的项目产生负面影响的事件或情况。
  • 设想。表示通过系统的用户交互的单一路径。
  • 任务。代表团队成员需要做一些工作。
  • 服务质量要求。表示限制系统如何工作的需求。

MSF CMMI 工作项类型

MSF CMMI 包含以下工作项类型:

  • Bug。代表您的应用程序中的问题或潜在问题。
  • 变更请求。代表对您的应用程序的拟议更改。
  • 问题。表示可能阻碍工作或当前正在阻碍工作的情况。
  • 要求。表示应用程序应执行哪些操作来解决客户问题的描述。
  • 审查。代表代码、设计或部署审查的结果。
  • 风险。表示可能对项目产生负面影响的事件或情况。
  • 任务。代表团队成员需要做一些工作。

请参阅此处描述工作项类型详细信息的链接:

http://msdn .microsoft.com/en-us/library/ms400752.aspx

http ://msdn.microsoft.com/en-us/library/bb668962.aspx

MSF Agile Work Item Types

MSF Agile contains the following work item types:

  • Bug. Represents a problem or potential problem in your application.
  • Risk. Represents a possible event or condition that would have a negative impact on your project.
  • Scenario. Represents a single path of user interaction through the system.
  • Task. Represents the need for a member of the team to do some work.
  • Quality of Service Requirement. Represents a requirement constraining how the system should work.

MSF CMMI Work Item Types

MSF CMMI contains the following work item types:

  • Bug. Represents a problem or potential problem in your application.
  • Change Request. Represents a proposed change to your application.
  • Issue. Represents a situation that may block work or is currently blocking work.
  • Requirement. Represents a description of what your application should do to solve a customer problem.
  • Review. Represents the results of a code, design, or deployment review.
  • Risk. Represents a possible event or condition that would have a negative impact on the project.
  • Task. Represents the need for a member of the team to do some work.

Please refer the links here which describes the details of Work Item Types:

http://msdn.microsoft.com/en-us/library/ms400752.aspx

http://msdn.microsoft.com/en-us/library/bb668962.aspx

新雨望断虹 2024-10-27 05:54:28

有时错误、错误和缺陷被定义为
当代码中的错误被测试团队识别为缺陷时,称为错误;当它被开发团队接受时,称为错误。如果不符合 SRS 文档中的客户要求,则称为失败。

Sometimes Error, Bug and defect is defined as
A mistake in the code is called Error when it is identified by the testing team called a defect, and when it is accepted by the development team called Bug. If it does not meet with customer requirements as in the SRS document it is called Failure.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文