![]() Non-Developer's Short Guide to Using Excel with TFS/VSTS Work Items For them it's easy to get the Excel features without installing Team Explorer or Visual Studio. However, often there are non-developers on your team who need to work with lots of work items. In those cases, it makes sense to use Excel.įor developers who install Visual Studio, you're good to go. Excel can be faster when you're editing and making changes to lots of fields or copying in data from another source.By pulling down a group of work items, you can work when you don't have Internet access to your TFS server or VSTS. However, Excel provides two nice advantages. This will open the Edit work items dialog where you can modify multiple fields at the same time as well as add Notes for History. For example, if you wanted to change a common field on multiple work items, you can select them in the UI (say a few Tasks on the Sprint Backlog, and select Edit: The web interface in TFS and Visual Studio Team Services (VSTS) has become rather amazing, so you won't often need to use Excel. That said, do you still need Excel integration? However, starting with the 2015 release of TFS, Microsoft starting providing an installer package with just the bits you need to make Excel (and God forbid Microsoft Project) work with TFS or VSTS. TLDR If you just want the step-by-step on how to work with Excel and work items without installing Team Explorer, jump down to the Non-Developer's Short Guide to Using Excel with TFS/VSTS Work Items on this page.įor years, if you wanted to work with Team Foundation Server (TFS) Work Items from Excel, you had to install the Team Explorer package which basically gave you the Visual Studio Shell plus the extra bits to integrate with Office. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |