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
Return on Investment
- Limiting human errors by manual data transferring and data duplicating
- Teams could work with their favorite tool
- However, it requires additional administrative effort as well as a well defined process
Usability
Other Software Used
Jama Connect, Sparx Systems Enterprise Architect, PLANTA, Atlassian Jira





