My TFS version is 2013.4 and I need EPIC workitem type in the Scrum 2013.4 process template.
I was trying to follow the instructions here but EPIC.XML is not found in the process template. Can anyone please let me know will I be able to make the following changes to get the EPICS? Where should I download the EPIC.XML file to import it?
https://blogs.msdn.microsoft.com/tfssetup/2015/09/16/configuring-the-epics-for-upgraded-team-projects-in-team-foundation-server-tfs-2015/
TFS 2013 did not have an epic work item type. Upgrade to a modern version of TFS.
Although you may be able to backport the work item type into prior versions of TFS, you won't have any of the additional features that were released in TFS 2015 around backlog management.
Related
My team is performing an analysis on which TFS version to upgrade to (from 2010).
One issue that we have faced daily is that TFS 2010 will log pending changes on files that are unchanged. For example, if I edit the JavaScript on HomePage.aspx, while leaving HomePage.aspx.cs and HomePage.aspx.designer.cs unchanged, the later two files will still log as pending changes, resulting with 3 files in the pending changes tab.
This post addresses this issue, and even has a semi-appropriate answer. But I'm wondering, has this issue has been fixed in terms of using TFS 'out of the box' with TFS 2017 or 2018? Do I really need to use TFS Power Tools with the latest version of TFS to get around this annoyance? I see many people saying that Power Tools doesn't solve the issue for all configurations.
That's Visual Studio behavior, not TFVC. I would expect that the behavior will remain the same regardless of the version of TFS you use.
That said, you should upgrade to 2018, period. There's no benefit to upgrading to a version that's already supplanted by a newer major release.
#Daniel is correct. This behavior remains no matter which version of TFS you are using. You could see HomePage.aspx.cs and HomePage.aspx.designer.cs belong to HomePage.aspx, TFS treats them as one file. If you check the history of HomePage.aspx.cs and HomePage.aspx.designer.cs, you'll find no new history produces, as during check-in, TFS detects there is no changes for these two files:
What are the best practices to migrate workitems say PBIs/Features manually from TFS to VSTS? And how to ensure we don't lose any linking to changesets or other linked child workitems?
Have referred the below link and the migration tool mentioned is deprecated and would like to know any other options which will help to migrate the data.
How to migrate work items from TFS to VS Team Services (VS Online)
The recommend way for now is using Migrate to Visual Studio Team Service, a way import your TFS Database into Visual Studio Team Services which definitely along with data.
However, currently only the following versions of TFS are supported for import with this tool:
TFS 2017 Update 3
TFS 2018
You may have to upgrade your TFS server to use. Alternative, the Microsoft official option is using public API-based tools.
Personally, even though Team Foundation Server Integration Tools has been deprecated. You could still use this solution in your case.
Besides, if you have no work item customization, then OpsHub is an
option. VSTS Sync Migration Tools is another way. But none offer a full fidelity migrations. Each tool has its own limitations.
In respect to the following question Is there a way to easily share Workspace settings (folder mappings) for Visual Studio Online / Team Foundation Server? and an entry I found regarding to this topic https://social.msdn.microsoft.com/Forums/vstudio/en-US/c9b16b30-4534-4781-a2e8-fb413a2df0af/power-tools-for-tfs-2017-with-vs-2017-rc?forum=tfsgeneral I wanted to ask if anyone knows how to achieve this very much needed functionality in TFS 2017?
Thanks.
Unfortunately we cannot create the workspace templates with VS 2017 for now.
According to release notes it says most of the previous Power Tools have been integrated into TFS 2017 that means no separate power tools for TFS 2017.
But the Team Utilities feature component is not integrated, that means these haven't shipped for Visual Studio 2017.
I have submitted a user voice here for you to suggest this feature, you can go and vote it up to achieve it in future.
Another similar thread for your reference: Team Members Team Utilities section in VS 2017
I noticed that I can change the order of the PBIs of the current sprint on visualstudio.com via Drag&Drop. At work we use TFS 2013 on our own server (I think the newest version Update 4) and that's not possible. Both use the SCRUM template.
Is this a configuration issue? It would help a lot if this would work at our own TFS too. What should I do?
The features available in VSO are beyond that of TFS 2013 update 4. The feature that you are referring to is planned for TFS 2015.
https://www.visualstudio.com/en-gb/news/release-archive-vso
For most customers, regardless of size, I recommend moving to VSO to get access to the latest and greatest features as they become available.
We are planning to upgrade from Tfs 2012 to Tfs 2013. Can anyone help me understand the difference in process templates between them? We use all three process templates for different projects.
The changes are very minor, except for:
The introduction of Portfolio backlogs.
Test Plans and test Suites are now Work Item Types (TFS 2013 update 3).
The AgileConfig and CommonProcessConfig files have been merged to a single file inside the template
The minor changes:
Git support for the Source Control options
Stackrank type fields are now hidden by default (because Agile task boards are now features of the Standard CAL).
Tag field support through the API.
The easiest way to visualize all differences is by comparing them through the TFS Team Project Manager which can be downloaded here.
TFS 2013 did not work well with our existing workspaces defined on remote network drives. TFS 2012 did work with this configuration.
After working several hours with our System Administrators, we gave up on trying to get the trying to get the existing network drive workspaces to work with the TFS 2013. Converting the workspaces to local drive locations enabled us to work with TFS 2013.