TFS 2013覆盖已将发布设置为“否”的子摘要任务资源分配 [英] TFS 2013 overriding child summary task resource allocation that has publish set to "No"

问题描述

我们已经设置了一个TFS项目来填充MS项目进度表。我们正在使用Agile模板。  MS项目计划已设置用于管理目的，我们正在跟踪计划中的功能和用户故事。在MS项目
文件中，我们添加了子任务以更详细地跟踪资源，计划，等等。

We have set up one of our TFS projects to populate an MS project schedule. We are using the Agile template.  The MS project plan has been set up for management purposes, and we are tracking Features and User Stories in the plan. In the MS project file, we have added child tasks for more detailed tracking of resources, schedules, etc. 

在其中一些项目中，具有以下层次结构：

On some of these items, have the following hierarchy:

功能（发布和刷新="是"）

Feature (publish and refresh = "Yes")

| - >用户素材（发布和刷新="是"）

|--> User Story (publish and refresh = "Yes")

       | - >计划（发布和刷新=" No"）

       |--> Planning (publish and refresh = "No")

                 | - >计划项目1（发布和刷新=" No"）

                |--> planning item 1 (publish and refresh = "No")

                 | - >计划项目2（发布和刷新=" No"）

                |--> planning item 2 (publish and refresh = "No")

                 | - >计划项目3（发布和刷新=" No"）

                |--> planning item 3 (publish and refresh = "No")

我们倾向于在"计划"中设置资源分配。摘要任务，单位为百分比（例如，开发人员1 [5％]，分析师1 [10％]等），而不是最低级别。这在所有情况下都可以正常工作，除非我们从Team Foundation插件刷新
工作项。 此时，无论TFS项目到MS Project的映射是否包含所有资源和工作估计，单位都变为0％（例如，开发人员1 [0％]，分析师1 [0％]等。）我是使用Project 2016的
，但是在项目中使用的所有MS项目版本都会出现这种情况。

It was our preference to set resource allocation on the "Planning" summary task, with units as a percentage (e.g., Developer 1 [5%], Analyst 1 [10%], etc.), rather than on the lowest level. This works fine in all instances, unless we refresh the work items from the Team Foundation plugin.  At that point, no matter whether the mapping for the TFS project to MS Project has all resource and work estimates included or not, the units change to 0% (e.g., Developer 1 [0%], Analyst 1 [0%], etc.) I am using Project 2016, but this occurs with all MS project versions used on the project.

这是设计的行为吗？ 除非刷新发生，否则资源单元很好，但我希望未发布或刷新的子任务不会更改。

Is this behavior by design?  Unless the refresh occurs, the resource units are fine, but I would expect that child tasks that are not published or refreshed shouldn't change.

推荐答案

你好Rob，

感谢您在此发帖。

我对MS Project不太熟悉，我想知道如何设置发布和刷新="是" /" No"

I'm not very familiar about MS Project and I want to know how to set publish and refresh = "Yes"/"No"

在MS项目中？

您的问题是，在您设置了&publish> refresh =" No"对于任务，它仍然将MS项目中的任务更改发布到TFS？

And your issue is that after you have set publish and refresh = "No" for tasks, it still publish the changes of tasks in MS project to TFS?

这篇关于TFS 2013覆盖已将发布设置为“否”的子摘要任务资源分配的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！