Planview TaskTop Hub - a good choice for an integration tool
Use Cases and Deployment Scope
Planview TaskTop Hub plays an important role to archieve a seamless exchange between different endtools in our processes requirement management and quality assurrance. With Planview TaskTop Hub, we've implemented the integration between two different Jama Connect instances, Jama Connect and Jira. The coming use case will be the integration between Jama Connect and a modeling tool.
Pros
- Data mapping through a end-tool neutral model
- Flexible and diverse possibilities for data transformation
- Easy to start a new integration
- Having competent consultants (such as Andreas P) and technical support engineers (such as Christoph T)
- Powerful feature - extension
Cons
- Being dependent to availability and quality of REST API provided by Endtools
- Diagram in Enterprise Architect (EA) being synced as Base64 image. But Base64 Image can not be displayed in Jira. The concept of Integration EA-> Jama -> Jira won't be able to work fully
- License model, in certain extent, is an obstacle for customers to expand their integration concept
- Planview TaskTop Hub does not have functionality to delete a synced item. It can only create and edit items
Likelihood to Recommend
Planview TaskTop Hub is very well suited to implement the integrations to synchronise data such as requirement, task, bugs. We have very good experience with the integration between Jama and Jira as well as between two Jama instances. In the context test management, related to Test steps in a test case, it's quite complicated. Test Case synchronization between two Jama instances works with Steps. But we aren't able to implement the synchronisation of Test Cases including Steps to such Plugin of Jira like Xephyr.
