Planview TaskTop Hub - a good choice for an integration tool
Rating: 10 out of 10
February 06, 2025
LB
Vetted Review
Verified User
7 years of experience
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.
- 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
N/A
N/A
- 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
We’ve evaluated other integration tools—OpsHub, Jama Connect Interchange, and Symphony from agosense—and selected Planview TaskTop Hub because of its ease of use, scalability, and flexibility for managing and extending the integration concepts with new tools.
180
System/ Requirement Engineers, Product Managers, Technical Product owners, Developers, Project managers, Testers
3
Applications consultant, IT experts
- Synchronisation from requirements between requirements management tool and task management tool
- Synchronisation from Bugs between documentation tool and work management tool
- Synchronisation from model based requirements between modelling tool and requirements management tool
- Minimizing the silo effects through seamless, nearly real-time data exchange.
- Employees could stay with the tools which support best their works.
- Certain work concepts could be quickly implemented without tool-restrictions.
- Exploring potential provided by Enterprise Data Stream Add-on
- Exploring potential coming with Gateway Add-on
No
- Scalability
- Integration with Other Systems
- Ease of Use
Using the Model-concept, Planview TaskTop Hub is able to simplify the possibility to create and manage the integrations between different tools. Scalability was the most important factor in our decision to select Planview TaskTop Hub.
I think we would go the same way.
- Implemented in-house
Yes
- Concepting with a clear specification containing Requirements and Test Cases
- Proof of Concept (POC)
- Evaluation
- Training
- Rollout#
- Review and continuous lessons learned process
- Proof of Concept (POC)
- Evaluation
- Training
- Rollout#
- Review and continuous lessons learned process
Change management was a big part of the implementation and was well-handled
Implementing an integration tool requires a certain standardization in how data is handled in an end tool. The change management was supported by a working group involving team leaders, tool, and process experts. Sometimes compromises had to be made, and discussions took time. However, we achieved a good result: people work in different tools following standardized workflows, so that most of the time, the synchronizations were done without issues.
- It took time to standardize how the synchronized data is handled in an end tool, which is a part of an integration
- It took time and effort to have an adequate integration concept, which sustains for more than one projects
- Online Training
- In-Person Training
- A well-discussed and adequate integration concept could help to ease the configuration.
- Sometimes a compromise on the workflow on the end tool must be made to compensate the tool-weakness or limitations of REST API.
- Sometimes a compromise on the workflow on the end tool must be made to compensate the tool-weakness or limitations of REST API.
No - there is no facility to customize the interface
Some - we have added small pieces of custom code
Some extensions for data transformation
If one day I need to purchase premium support for Planview TaskTop Hub to ensure the integrations work, it would be time to evaluate other integration tools to replace it. The reason is that an integration tool plays a support role; it must be robust and easy to use. If this is not the case, the integration tool has not fulfilled its role.
Yes
The analyse and bug-escalation were done. And we've seen the reported bugs being fixed.
We were running an update on an end tool within the integrations. Prior to the update, the Planview TaskTop Hub Support team was informed. When a blocking issue within Planview TaskTop Hub occurred, I submitted a ticket. The support team provided a solution for the Planview TaskTop Hub in the form of an extension, which resolved the blocking issue within an hour during a call. I hope Planview can maintain this level of support for Planview TaskTop Hub in the future.
- Having Model as a central element of any integration
- Possibility to transform the data
- Possibility to extending the transformation through extension
- Terminating the synchronisation within an existing integration once the synced content was no longer active.
- Synchronisation of such a structure in treeform could be easier sometimes, it would be great.
No
- Jira
- Pro Cloud Server
Integration deep: Structure, artifact contents and traceability
The difficult part is to build up an integration concept based on the usage of the data and involving workflow on the synced data.
The difficult part is to build up an integration concept based on the usage of the data and involving workflow on the synced data.
- API (e.g. SOAP or REST)
- Javascript widgets
- Understanding the data structure and data usage - Having a well defined integration concept - Understanding the functionality and limitation of the end tools within the integration.
Yes
Until now, it works as wanted. Once a year we update our Planview TaskTop Hub. Any update for on premise Planview TaskTop Hub in our organisation comes with a strict quality evaluation of functions in a new release to minize any unexpected impacts of a new release. We haven't got any experience if the update in the cloud.
- Sufficient support for the new releases of end tools
- Some new features such as synchronisation of diagram from Enterprise Architect (through Pro Cloud Server) with Jama item
- Bug fixes within context Pro Cloud Server Synchronization and Container mirroring
No
Yes
From Professional to Enterprise