It's all about the answers!

Ask a question

TFS integration with RTC


Rao Shines (15945062) | asked Dec 02 '14, 8:03 a.m.
 Team,

We are using Rational ALM for change management and TFS for Source Code Management, can we integrate TFS and RTC to link TFS Changesets with RTC Workitems.

Thanks in Advance. 

Comments
Frank Ning commented Jan 09 '15, 10:38 p.m. | edited Jan 10 '15, 6:17 p.m.

 Not really answering the question but this is also the dream I had for years. Not sure when it can come true. It seems that IBM avoid answering this question in a promising way...

One answer



permanent link
Geoffrey Clemm (30.1k33035) | answered Jan 10 '15, 6:22 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Jan 10 '15, 6:24 p.m.
Rational supports the OSLC standard for linking to work items (in both RTC and ClearQuest). 
If Microsoft added support for the OSLC standard to TFS, then you would have your linkage (to RTC work items, CQ records, and any other change management system that supported the OSLC standard).
In general, you need ask your vendor (in this case, Microsoft) to support its side of an inter-operation standard.

Comments
Frank Ning commented Jan 10 '15, 8:38 p.m.

 Teja was NOT asking for work item integration. Neither did I. Many people have been looking for the SCM integration between TFS and RTC. That is, how can we migrate TFS SCM into RTC by keeping versions and change histories. Do we have answer from IBM after a few years? What is the proposal from IBM for customers on TFS moving to RTC???


Geoffrey Clemm commented Jan 11 '15, 10:21 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Quoting from Teja's question: "can we integrate TFS and RTC to link TFS Changesets with RTC Workitems".   So Teja's question clearly was about work item integration. 

Frank's question is very different (a form of which he has asked recently in https://jazz.net/forum/questions/171369 ), and the answer is very different ... Microsoft of course cannot be expected to provide functionality to migrate from their product (TFS) to a different vendor's product (RTC).  Building a version history importer that really works at scale is very complex and expensive, and there has not been sufficient demand for either Rational or third party vendors like TaskTop to build a custom one from TFS to RTC.  So you can either write a custom one for your needs (using the command lines of TFS and RTC) ... this is the most common approach, or try the two step approach of using one of the TFS-to-SVN migration tools, and then the SVN-to-RTC migration tool.

Your answer


Register or to post your answer.