I have team project in TFS. There are already some work items in the project. I need to add new fields to work item type. How can I do it?
Export the work item type, add the fields, and re-import it. As long as you do not delete any fields, this will not affect existing work items.
You may have to bulk-edit existing work items to put in valid values for the newly-added fields.
The best way to do this is by installing the TFS Power Tools, which will add the Process Editor to your Team menu.
Related
I'm relatively new to developing with tfs (only used git before).
I'm connecting to a server, which contains a decent amount of projects.
When I create a new work item, I can select only the server below 'classification' and not the specific project.
How can I allocate a work item directly to a project instead of the server?
Thanks!
You could directly create work item under the specific team project. The simplest and effective way is through web portal.
Project--Work--New Work Item--Work Item Type
After this the a work item directly allocated to this project instead of the server.
In work item, several features depend on the team project or team that
you have selected. For example, dashboards, backlogs, and board views
will change depending on the context selected.
When you add a work item, the system references the default area and
iteration paths defined for the team context. Work items you add
from the team dashboard (new work item widget) and queries page are
assigned the team default iteration. Work items you add from a team
backlog or board, are assigned the team default backlog iteration.
You navigate to your team context from the top navigation bar.
If you are new to tfs work item, suggest you take a look at related tutorial in MSDN: Plan and track your project with work items. Besides in TFS, there is a concept of permission, also make sure your account have enough permission for the project and adding work item.
Is there any way to add a new drop down on the bug page in TFS. I want to add a new drop down as 'Bug Fixed In Build' with options as build versions
Thanks
You could add a Integration Build filed for your bug work item type.
When the Integration Build field is present in the WIT definition,
Team Foundation Build identifies work items that were resolved with
each build and then updates those work items to set the build number
in which they were resolved in the Integration Build field.
More detail info please refer this link: Fields that support integration with test, build, and version control
To display the fields in the work item is also not hard in TFS. Details please take a look at this tutorial: Add or modify a work item type. Highly recommend you to install Team Foundation Server Power Tools and use Process Editor to modify the work item template.
Note: To add or customize a WIT, you must be a member of the Project Administrators group or have your Edit project-level information permission set to Allow.
Is it possible to reset the work item type history that is proposed to a user who creates a new WorkItem query?
We have some TeamProjects that went through two Process-Template customizations including localization and WorkItem form layout optimizations.
With TFS 2015 we're finally moving to the Agile process template. The problem is that somewhere the TFS stores the WorkItem-Types you have ever used and displays them in the WorkItem query designer.
The values in the Work Item Type are mixed both german and english and are picked from all of the past process templates the team project has ever been configured to use.
Is it possible to reset that list and if so, how?
The scope of the query editor is for all projects in a give collection. When you open the dropdowns, it thus shows all work item types in any of the projects in the collection.
In TFS 2015 we have added a checkbox to scope your query to the existing project. This checkbox is off by default because the majority of the queries run in the scope of a project. When the checkbox is unchecked, the dropdowns are limited to show only the states, fields and work item types that are in use by the existing project.
If you don't need these work item types and the work items, you can use witadmin destroywitd to destroys the work item types, after running the destroy command, the work item types will disappear from the drop-down. But please notice this will also destroy every work item of that type permanently without recovery.
witadmin destroywitd /collection:CollectionURL /p:Project /n:TypeName [/noprompt]
I need to change one of the item in ALLOWEDVALUES, and preferably to update all existing workitem and possibly all history as well, is there any built in TFS 2010 command or function to do this? If not, can I update the table directly, after applying the new ALLOWEDVALUES?
You should create a query and open it in excel. This will allow you to easily bulk edit all of the old values to the new ones. If you create a query with the right columns you can right click on it in visual studio and open in excel. The other way round you can open excel and use the Team tab to open the query. The you can update all if the work items and save in one go.
if you plan on keeping some of the old values around you should also add so that folks can still save without changing the value.
I have a TFS 2010 Work Item Type with a custom field called "Requested By." This field can be populated with any name, but since most of the requests come from project developers throughout the organization, the SUGGESTEDVALUES property should populate the dropdown list with members of any TFS team project.
I have tried various values for SUGGESTEDVALUES, but both Collection\ Project Collection Valid Users and Server\ Team Foundation Valid Users seem to return every valid Active Directory account—well over 10,000 names.
I recognize that one option is to add an ALLOWEDVALUES item with multiple LISTITEM entries for Project\ Contributors for every team project, but with more than 150 team projects in the organization, this would be time-consuming initially and challenging to manage in the future.
Is there any easy way to populate the drop-down with TFS valid users who have actually been assigned to any team project in the collection, and exclude "Valid" users who exist in Active Directory but have never been assigned to a project?
What do you get if you use Project Collection Valid Users?
Project Collection Valid Users is the correct group to use, and I have entered it correctly.
However, one project team wanted to make their code available to the entire organization, and added ORG\Domain Users to the [Project]\Readers group. This was discovered by running a full audit with TFS Projects based on a hunch that something like that must have happened.
Having answered this question with "because a project team was doin' it wrong," I have posted a follow-up question to find out how to correctly grant all valid TFS users access to a specific project. See How can I grant Team Project access to all Project Collection Users? for the discussion on (hopefully) doing this "the right way."