LIMITATIONS IN TFS 2010
There are several limitation exist in TFS 2010 that may affect your team
project after is it being created. Let’s examine each of these limitations.
Limitation #1: Renaming Team
Project Limitation
TFS 2010 does not allow you to change team project name after project is created. It is very important to settle on your project name and getting all of the approvals for this name before creating a project in Team Foundation Server. This limitation of changing names does not apply to team project collection however.
TFS 2010 does not allow you to change team project name after project is created. It is very important to settle on your project name and getting all of the approvals for this name before creating a project in Team Foundation Server. This limitation of changing names does not apply to team project collection however.
Limitation #2: Moving Work Items
it is impossible to move work items between Team Project due mainly for difference in Team Project templates. For instance, QA team logs a defect into TFS for one of the project but upon reviewing by developers it turns out that this defect applies to a different team with its own team project. It needs to be moved to the other TFS team project space. There is a way to accommodate this by creating a large team project and setting up smaller applications as Area Paths. This way movement of work items can be accomplished without too much trouble.
it is impossible to move work items between Team Project due mainly for difference in Team Project templates. For instance, QA team logs a defect into TFS for one of the project but upon reviewing by developers it turns out that this defect applies to a different team with its own team project. It needs to be moved to the other TFS team project space. There is a way to accommodate this by creating a large team project and setting up smaller applications as Area Paths. This way movement of work items can be accomplished without too much trouble.
Limitation #3: Merging and
Branching Visualization is not allowed across Team Projects
It is not a common practice to Brach and Merge your code between team projects and TFS 2010 comes with the limitation when visualization of these changes is not even possible.
It is not a common practice to Brach and Merge your code between team projects and TFS 2010 comes with the limitation when visualization of these changes is not even possible.
Limitation #4: Reporting applies
to Team Project only and artifacts are scoped to Team Project
All of the TFS Reporting capabilities including Dashboard are scoped to Team Project only. If you need to create a report across Team project it may become a challenge. You can however report on project across Area Paths and Iteration Paths. It can also be a consideration for the type of a Team Project you want to create in a first place. In addition, all of the TFS 2010 team project artifacts are scoped to this team project only. This is done primarily to preserve all of the artifact’s linkages within your Team Project. On the other hand, you can create a report that goes against Data Warehouse since it contains information across all Team Projects and Team Project Collections.
All of the TFS Reporting capabilities including Dashboard are scoped to Team Project only. If you need to create a report across Team project it may become a challenge. You can however report on project across Area Paths and Iteration Paths. It can also be a consideration for the type of a Team Project you want to create in a first place. In addition, all of the TFS 2010 team project artifacts are scoped to this team project only. This is done primarily to preserve all of the artifact’s linkages within your Team Project. On the other hand, you can create a report that goes against Data Warehouse since it contains information across all Team Projects and Team Project Collections.
Limitation #5: You cannot move
Team Projects between Team Projects Collections
it is not possible to move Team Projects due to conflicts of IDs that each Team Project has. This ID is important for artifacts linkages within TFS 2010. The only possible way to split up a project into is by cloning Team Project Collection and cleaning up each individual Team Project from unwanted artifacts.
it is not possible to move Team Projects due to conflicts of IDs that each Team Project has. This ID is important for artifacts linkages within TFS 2010. The only possible way to split up a project into is by cloning Team Project Collection and cleaning up each individual Team Project from unwanted artifacts.
Limitation #6: Physical Limitation
of your TFS instance
TFS 2010 has several limitations that may affect the way you design and build your Team Project and Team Project Collections. For example, TFS 2010 can only support up to 100 Team Project Collections and up to 500 team projects.
TFS 2010 has several limitations that may affect the way you design and build your Team Project and Team Project Collections. For example, TFS 2010 can only support up to 100 Team Project Collections and up to 500 team projects.
Limitation
#7: TFS Work Item Attachment Size Limit
Work Item has 4 Mb size limit on attachments
by default. However, we can increase this size limit by setting this limit up
to 2 gigabytes. In order to do that, we need to use web services that Team
Foundation Server provides.
In order to set this limit you
have to be a member of the Administrators group on the Application Tier which
is a requirement.
Maximum size as it was mentioned
is being set using Web Services and you need to access Web Services using your
browser and by typing Server Name and WorkItemTracking directory.
http://SERVER:8080/WorkItemTracking/v1.0/ConfigurationSettingsService.asmx?op=SetMaxAttachmentSize
In the maxSize text box you need
to enter desired attachment size in bytes and then Invoke it.
No comments:
Post a Comment