Is there a way to track the changes done to Process Templates or Workitem Types in TFS. Something like Logs\History etc? If so please let me know.
I did not see a change history for process template. But you can use (git or tfvc) version control:
Download your process template and add it to version control. https://learn.microsoft.com/en-us/vsts/work/work-items/guidance/manage-process-templates
Add a process template to version control.
Edit needed work item types and over objects through version control. Commit (or checking) new changes.
Update changed work item types with witadmin importwitd https://learn.microsoft.com/en-us/vsts/work/customize/reference/witadmin/witadmin-import-export-manage-wits
Upload updated process template from version control for new projects: https://learn.microsoft.com/en-us/vsts/work/work-items/guidance/manage-process-templates
Related
I am working with the Scrum workflow in TFS (Visual Studio 2017) and the only available value for the state is New when I would be expecting Approved, Committed and Done.
Why are they missing? How could I solve this?
The transitions between the different states of the work items are defined thanks to a specific workflow.
You have to save your work item with the "new" state before being able to modify its state to other states like Approved for example.
You can find more information at this page : https://learn.microsoft.com/en-us/vsts/boards/work-items/workflow-and-state-categories?view=vsts
Seems you have customized your WIT definition file (in you scenario it should be Product Backlog Item.xml file), and removed the state Approved, Committed and Done and transitions from the file.
So, you just need to add them back and set the transitions between the different states of the work items accordingly.
If you only customized the PBI wit definition file, then the simplest way is exporting the PBI wit definition file from a normal team project (with non-customized templated, it will have the state values you needed), then import the file to your current team project to apply the changes.
However if you also customized other things for your process template, then you may need to modify other related things based on your customized process template.
See Import, export, and manage work item types for details.
You can also use the extension TFS Process Template Editor to export and import the wit file.
I am about to move a local TFS project to visualstudio.com
When the project was created, it was created with a SCRUM process template. However, only source control functionality was used (except about 20 work items which can be deleted).
I want to add them to visualstudio.com as a project of process template type CMMI.
I am reading confusing (and seemingly conflicting) information on-line about how it is done (and if it is even possible).
Has anyone does this before (or have experience with TFS migrations in general)? Any input appreciated!
Thanks
You can use TFS integration tool to process migrating Source control and work items. As you want to change the process template, you need to put the mapping file during migration. More information, you can refer to this blog: https://mohamedradwan.wordpress.com/2015/05/14/migration-to-vso-visual-studio-online-with-different-tools/
I've been looking into change the process template on a Team Project, but still have a few questions. I'm looking to move from MS Agile v5 to TeamPulse v1. There are no existing work items that we care about, so no need to move those over, however we do want to keep the existing source control history/branches.
With this in mind what is the best method to use? I am currently looking at using witadmin but am also considering TFS Integration Tools (MS or CodePlex versions). I think these are essentially my only options.
Do I need to worry about mapping existing fields to those in the new template if I don't intend to keep the current items?
Any additional advice would also be welcome.
It is not possible to explicitly change the Process Template, though it is possible to import the new work item type definitions using witadmin
I found the following answers helpful in finding a solution:
https://stackoverflow.com/a/2999219/509356
https://stackoverflow.com/a/5664531/509356
If you don't need any existing workitems I recommend to create a new team project with TeamPulse v1 and migrate only the source with the TFS Integration Tool. The problem with the witadmin solution is that you won't be able to delete the old workitem definitions and that could lead to confusions.
Does anyone know how to configure the auto-generated message that is created on a git-tf checkin command to TFS?
I would like to have more control over that to allow for adding a comment during checkin.
The agile process system that my company uses allows adding a task number in front of a comment, and then will associate the source code with the task in the agile system.
Anyone have any ideas? Anyone have any customized git-tf source?
As mention in this thread, you can try!
I've upgraded to the latest version of git-tf and noticed that it generates a different comment for a tfs changeset after doing a checkin than the previous version (I'm using the --deep option, no message provided with the command).
Is there a way to revert to the 'clean' (without the commit guid, author, commiter) comment from git?
Yes, You can use the --no-metadata flag when checking in and it will revert back to the "clean" comment.
So you don't have much control on the comment, but at least you can reuse git comments.
There is a request for making that option the default.
How can one determining which TFS process template is being used? A few were installed and now I can't determine which one is being used by TFS.
TFS Team Project Manager on CodePlex is a free tool which will inspect all your team projects process templates (even if they're customized) and tell you which process template was most likely used to create that Team Project (and give you a % confidence in the match). You can even give it additional "source" process templates, such as your company custom process template, and it will tell you which projects were created with it.
In addition to Edward's approach:Another one, quick & dirty and without any capability to reveal any changes you might have performed, is the following:Right-Click on your TeamProject from within the Team Explorer and select "Team Project Process Guidance":
This should pop-up a webpage that will show you the Process Template that was used to create it.
If you have not modified the process templates (either the ones that are included with TFS, or any that you might have downloaded and installed) then you can export the process template as an XML file and compare against the original version.
(That link is really about modifying the process template, but steps 1-3 discuss how to export the current process template for a Team Project.)
Of course, even if you had modified the process templates slightly, using a diff tool may be able to yield results as to which process templates those were derived from.