It's all about the answers!

Ask a question

RTC Mantis integration

Kristina Florea (3323) | asked Oct 06 '14, 5:31 a.m.
does anybody have experience integrating RTC with Mantis? If yes, please elaborate.
If not, what would be the recommended way (and with the least effort to migrate when upgrading) to implement such an integration?
The result of such integration/connector would be that on create a specific work item type in RTC, a task in Mantis should be created and linked. That will allow the developers to work with RTC, while the other stakeholders continue to use Mantis.

One answer

permanent link
Piotr Aniola (3.7k11738) | answered Oct 08 '14, 3:54 a.m.
Hello Kristina,

as far as I could tell, OSLC is not supported by Mantis:
This makes integration a bit tricky.

I suppose you could create a follow-up action that would trigger on workitem save. In the follow-up action you'd need to implement creating a task in Mantis (which, as far as I remember from using Mantis in the past) should be as easy as issuing a http request). You will find a workshop on how to create follow-up actions in RTC under the following link:

Ralph Schoon commented Oct 08 '14, 4:43 a.m. | edited Oct 08 '14, 4:44 a.m.

RTC also comes with a synchronizer API, that is part of the server SDK as well as the Plain Java Client Libraries. You can essentially write synchronizers similar to the ClearQuest Synchronizer if you have enough money to throw at it.

The questions from my perspective:

  1. Is there a partner (like TaskTop) that has it alread?
  2. Why would you want to create the integration?
  3. Why would one create it only for the customer?
  4. How much are they willing to pay for it and who is supposed to maintain it?
  5. Can you separate the domains of the tools and get along with linking URLs instead?

Kristina Florea commented Oct 09 '14, 5:02 a.m.

We already talked to Tasktop and is considering building one (has none at the moment) - depending on the business case(s) and the investment the customer is willing to make.
For now is useful to have a feasible concept and maybe ( (but not necessary) a quick and dirty implementation to demonstrate that it can be done (follow-up action?). The CQ Synchronizer was the example we gave so far (good to know that the synchronizer API are openly available - thx for that info).
And the customer might decide to do it himself - so the maintenance is on him.

The linking option is not so appealing - some automation is desired.


Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.