I want to be able to check my spelling (and grammar) when I am entering text into work item fields (for example a PBI or Bug) in TFS VS2010. I found this addon and installed it. Is there anything else should I do besides run the installer? I can not find any spell checking buttons when I am inputting work items.
Any idea why this is happening?
What is wrong with the installation?
Is there any better way to add spell checking capability to work items in TFS?
After Installing the Custom Control you still need to manualy add the custom control to you work item definition.
Best way to do this is using the Process Editor from TFS Power Tools: http://visualstudiogallery.msdn.microsoft.com/c255a1e4-04ba-4f68-8f4e-cd473d6b971f
Hope this helps.
Regards,
Adam
Related
Is there a way to reset or start over with the latest version TFS work item template? I do not care about any existing work item history.
Scenario: I have a TFS project that has code, but never used work items. The existing template is too old to use the automatic Configure Features wizard tool. It is ok to mess up any work item history.
Is this possible? Thank you!
Have a look at TFS-PowerTools
The built in Work Item Templates should override your existing ones. That might even work before updating, but i'd not recommend that try.
We had this trouble once too. A coworker fixed this after doing some kind of Troubleshooting guide. (Let me check tomorrow if i can find that one again)
Let me know if that helped!
Take a look at https://nkdagility.com/tfs-process-template-migration-script-updated/
It covers off what you need to do, and includes some PowerShell to help you.
As in subject:
Go to "Find Changeset" option.
Find a changeset.
Double-click on changeset to open Changeset Details window.
It gives a list of all files that have been checked in within given changeset.
Why I cannot apply a label on those files from that level where I have them all in one place? Especially, that very often they are part of different solutions and projects, so normally I would have to create a label for one file and then search and add one by one to the existing one.
It is so inefficient!
Is it some bug or lack of functionality? If the second - it is hard to believe MS guys forgot about such handy function.
How do you deal guys with such situation?
EDIT - to clarify my reasoning:
If I use jessehouwing's method - yes, it works and it's simple.
But then when I search in the future for that label and want to see what code was included, it gives me a list of all solutions - even those totally unrelated (IWP and PDPRO are the unwanted ones):
If I use it my way - it gives me that:
I think it looks cleaner and gives directly the information of what solutions and files underneath where included at the time when I put stuff into Production environment and applied corresponding PROD label.
The feature you're looking for doesn't exist. generally a single file or group of files at a label doesn't make a lot of sense. While it's possible to "scope" labels in TFVC, it's only possible through the commandline.
generally you'd create a label at the repo or branch level at the specified changeset. That will include all files, including the ones you just checked in. Creatign such label is relatively easy from the source control explorer, though you need to copy the changeset number:
It's unclear to me why you'd only want the changed files to be included in the label, maybe you can elaborate a little more on that requirement.
Update: What you desire isn't possible from inside VS and isn't simple from the commandline either. I suppose that with a bit of Powershell Magic against the TFS Client Object Model you can do this from the commandline and it should also be possible to build this as a Visual Studio Extension (or maybe suggest it to the author of the TFS Source Control Explorer Extensions.
How does your team differentiate TFS work items that are "done" (development/testing complete) vs. "deployed" (live in Production)?
My first option would be to use a Tag to mark this. You can query and filter through them.
Another option would be to customize the work item types with an additional field, but this route is a bit more complex.
Change your Definition of Done to include: Deployed. Doing that you will have code working in production. If is needed more work, is not done.
But I guess you´re asking about how to have a new status. You can modify the workflow template to include this new state. In older versions of TFS you only can do that before to create the project, not in an started project. I don´t know in the latest version.
Is there any possibility to create a custom Work Item Type in TFS 2010 that is read-only after the first save?
We would like to implement a very simple code review solution based on a custom review work item associated to a changeset.
The idea is that after the work item is created, it can not be altered afterwards (not even by the original creator).
I've tried setting the System.ChangeDate to FROZEN but that isn't supported and unfortunately the first save is also a change, so setting it to EMPTY or READONLY doesn't work either.
Did you have a look at the community solution for code review for TFS 2010 http://teamreview.codeplex.com/
The most complete solution for Team System Code Reviews: a specific work item type and a Visual Studio add-in for a completely in IDE code review experience. TeamReview exploits the advantages of Team System and VSX to reduce waste and surface new business value from code reviews
HTH
Chees, Tarun
You might want to look at the work item type's workflow. You can make changes to fields in both the states and the transitions.
You could try to modify the transition from New to To Do (or whatever the first state is called for your WI).
In those transitions, you can freeze or make read-only the fields that you want to freeze.
Hope this helps,
Assaf.
We have a rule in TFS that requires all checkins to be associated with a work item. We have an automated daily build process that uses tf.exe to check in the files. However, I did not find any way to associate files with a work item.
I heard of tfpt, and have it installed, however, I did not have any success using it to associate files with a changeset either.
Is there another way to do this?
Thanks!
I'm pretty sure tf.exe / tfpt.exe cannot do this except through their UI. If you need to use the -noprompt parameter for automation then you're likely out of luck.
Luckily, it's not hard to use the API directly. MSDN link. Basically just build up an array of WorkItemCheckinInfo[] and pass it along with your request.
Team Foundation Power Tools has a command for dealing with work items.
tfpt.exe help workitem