We have TFS 2015 (on-premise) and Microsoft Teams in the cloud.
I am trying to find the TFS plug-in (all I can see is Azure DevOps) and want to be able to show TFS information inside of Teams.
I see lots of articles on how this use to work? But can't find it in my list of plugins to add into the system.
Is there something we need to do at a server level?
Thanks
There is an official extension-- Microsoft Teams Integration.
With using this, you are able to see activity about your Azure DevOps or Team Foundation Server projects directly in your Microsoft Teams channel, for example:
Work item updates
Pull requests
Code commits
Builds
Release deployments and approvals
Work item updates
Azure DevOps Kanban board
However, as the link declare clearly, it only work with Team Foundation Server 2017 Update 2 and above. It's not able to do this with TFS2015. You need to upgrade your TFS version. With higher version, you could also get more released new features in TFS.
Related
I'm looking at integrating TFS with JIRA. I Want to run my test cases in TFS but when i raise bugs i want them to automatically update on the JIRA board. Is there anything out there that can make this possible?
Also would it automatically block the test case and link the bug in JIRA with it?
There is no such kind of build in feature or extension. However, you could raise bugs in TFS/Azure DevOps first when you run your test cases. Then synchronize your bugs with issues in Jira. It's not able to directly link the bug in JIRA with TFS test cases.
You could choose to use TFS4JIRA Azure DevOps integration.
TFS4JIRA is migration, integration and synchronization tool, which
bridges TFS / Azure DevOps and Jira (Server/DC/Cloud). Integrate
Azure DevOps with TFS4JIRA, to view your project or issue-associated
Azure DevOps check-ins in Jira, as well as synchronize changes made to
the issues and integrate Azure Jira work items.
Create your individual TFS4JIRA sync profiles and define the project collections which you want to work with.
Map your issue types, work item types, fields, values.
Hierarchy and subtasks synchronisation supported.
Enable your profile and, voila! – the synchronizer is making sure that Jira and Azure DevOps exchange information in the background.
If you already have some bug/issue work items in JIRA and want to import them to TFS on-premise server. There is an extension named Jira to Azure DevOps/TFS work item migration tool. It is used to Azure DevOps work item migration tool lets you export data from Jira and import it as work items in Azure DevOps or Microsoft Team Foundation Server. Here is the download page.
In our company there exist in different teams two different systems to manage the issues: Mantis and TFS. Now we have a project where a team must handle changes in both systems.
Is there a programm or a tool where tickets of TFS and Mantis can be viewed. At best there is the posibility to define relations between the tickets and prioritize them independently of the system the tickets come from.
I didn't see there is any exist tool to integrate TFS and Mantis. But there is a source control integration plugin framework for MantisBT, which supports for Github, Gitlab, Bitbucket, Gitweb, Cgit, Subversion, Mercurial, etc. You could refer to the plugin and implement TFS integration:
https://github.com/mantisbt-plugins/source-integration
Or you can use Mantis Bug Tracker REST API and TFS REST API to program your own tool.
We have 2 TFS servers, one is inside the firewall, and the other one is outside the firewall. Because of security reasons, we still need to keep it this way. But the question is: is there a way to Sync these 2 TFS servers, say at every night?
Say we have servers TFS1 and TFS2, right now, we only want to Sync from TFS1 to TFS2, not bidirectional synchronization. If possible, we want to have complete synchronization.
I searched some time, but I could not find a good solution. It seems all recommendations are for old version TFS.
Are there any solutions for the latest TFS? existing products? Or, some information about API that we can use to make a tool for this?
Thanks
There is nothing changed with sync two TFS servers for the latest TFS version. Just as Daniel and many other expert suggested:
TFS generally lives in 1 instance and 1 only. TFS is a production
environment for the development team. It doesn't make sense to have
two TFS systems and have them synchronize to make this separation.
Having your teams work on two different TFS environments at the same
time is a very strange requirement.
Source Link
The best solution in your case, negotiating with your IT team, set up a safe and stable way to allow your top Management users to connect the internal TFS. You could also set up SSL for your TFS server to improve the safety.
It will also save you a lot of time costs for maintaining two servers syncing.
If you insist on syncing two TFS servers take a look at this similar question: Sychronising work between two TFS servers
Another way is using VSTS instead of your external TFS. Microsoft has documentation on this exact scenario which can be found here: Migrate to Visual Studio Team Services : Move from Team Foundation Server (TFS) to Visual Studio Team Services (VSTS) and bring your data along.
This link also contains the download link for the migration tooling which you will want to use
Currently the following versions of TFS are supported for import:
TFS 2017 Update 3
TFS 2018
TFS 2018 Update 1
how to migrate a single project alone (where project collection contains 30+ projects) from TFS to VSTS with all history, build-definitions, changesets
Microsoft has documentation on this exact scenario which can be found here: Migrate to Visual Studio Team Services : Move from Team Foundation Server (TFS) to Visual Studio Team Services (VSTS) and bring your data along.
This link also contains the download link for the migration tooling which you will want to use
Currently the following versions of TFS are supported for import:
TFS 2017 Update 3
TFS 2018
TFS 2018 Update 1
As described in About VSTS and TFS, Scope and scale data, the
long term direction for VSTS is to support grouping of accounts within
organizations. This would lead to:
VSTS accounts that serve as the equivalent of TFS project collections and VSTS organizations that serve as the equivalent of
TFS deployments.
This is why the TFS Database Import Service only supports importing single TFS collections as single VSTS accounts.
If you need to migrate individual team projects you will need to use
one of the other options—manual copy or public API based
migrations.
Source Link
It's very clear why you could not use TFS Database Import Service to migrate at team project-level directly.
You can also have a try for VSTS Sync Migration Tools,it allows you to bulk edit and migrate data between Team Projects on both Microsoft Team Foundation Server (TFS) and Visual Studio Team Services (VSTS). Note this without history. How to please refer: TFS 2017 Migration To VSTS with VSTS Sync Migrator
If you insist on keeping all history, the only way is using TFS Database Import Service, you may take the workaround as Daniel suggested.
Is Microsoft still working on both products? Has development on TFS been dropped in favour of VSTS?
For context, we are using TFS right now and VSTS clearly has better integration. Specifically with Microsoft Teams and ZenDesk which is important to getting our workflow process in a more manageable state. However, VSTS doesn't have anywhere near the configuration or reporting that we require.
Will either product eventually have the full feature set or will we have to choose and build our own integrations or reporting?
Now Azure DevOps and Azure DevOps Server, but the rest of the story remains intact.
Visual Studio Team Services (VSTS) and Team Foundation Server (TFS) are based on the same codebase. VSTS is deployed to the cloud every 3 weeks or faster. TFS has received a major upgrade yearly (2015, 2017, 2018) and a major update pack every 3 to 4 months (2015.0-3, 2017.0-3, 2018.0-1).
Most new features are released to Visual Studio Team Services first and are integrated into Team Foundation Server with a bit of a delay. Some features are available in VSTS which depend on cloud resources, so they're not likely to move to TFS anytime soon.
With regards to reporting, this has been a bit of an Achilles' heel of VSTS. It has never had the Report Server and Analysis Cube capabilities of TFS. It does offer integration with PowerBI and that integration is quickly getting better.
You can see the overview of feature availability between cloud (VSTS) and server (TFS) on the Feature Timeline, as you can see a lot of new things happening, most of them are hitting VSTS first.
Microsoft offers a support lifecycle for Team Foundation Server and currently, it looks like Microsoft won't abandon their on-premise customers anytime soon. TFS 2018 has an extended support lifecycle all the way to 2028:
Products Released Lifecycle Start Date Mainstream Support End Date Extended Support End Date Service Pack Support End Date Notes
Visual Studio Team Foundation Server 2018 11/15/2017 1/10/2023 1/11/2028