TrustRadius: an HG Insights company

Planview Hub Reviews & Insights

Score8.4 out of 10

12 Reviews and Ratings

Planview Hub Reviews

4 Reviews

Planview TaskTop Hub - a good choice for an integration tool

Rating: 10 out of 10
Incentivized

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.

Planview TaskTop Hub review

Rating: 8 out of 10

Use Cases and Deployment Scope

We use Planview TaskTop Hub to integrate AgilePlace and Azure DevOps. There are currently 18 integrations running between three segments for Epics, Features and User Stories in both Test Region and Production. It is used to manage scrum team efforts to create an end-to-end portfolio management solution between both tools. We soon will be adding Initiatives to get the full scope of work in the hierarchy. We use Planview TaskTop Hub to eliminate duplicate data entry and to automate traceability.

Pros

  • Allows for one- vs bi-directional field flow which is useful per segment
  • Allows for the relationship mapping of Parent/Child cards
  • Allows for customization of mapped fields

Cons

  • It would be great to copy collections and integrations.
  • Add a search field to the already mapped fields. Example Lane/State. We have to map over 250 lanes and oftentimes must scroll to view what are already mapped.
  • Ability to disassociate artifact pairs after an X amount of time.
  • Version history of scripts made available within the script itself. Add time/date stamps and what changes occurred.

Likelihood to Recommend

It is well suited for when there are separate Projects in ADO we are connecting. We use one Project in ADO for two separate segments work and we have seen issues come up with this route. Related mapping, for example, we cannot configure due to two segments work being in the same ADO Project.

Review of TT hub.

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

integrate software development platforms from Ideas to Releases to ensure that requirements are tracked throughout the process and tested against. This allows information to be understood at all levels of the organization and ensures that requirements are strictly adhered to going forward. It also allows the business to understand where in the development process each step is understood and accepted/rejected.

Pros

  • Tracks endpoints and identifies risks.
  • Tracks Duplicate information in end points of systems.
  • transitions requirements through the process effectively.

Cons

  • Troubleshooting issues.
  • Automatically fix broken end points or disregard them.
  • UI is a little clunky in areas.

Likelihood to Recommend

The product seems to function as designed and is utilized throughout the development process, and it works well.
Vetted Review
Planview Hub
10 years of experience

Tasktop HUB Review

Rating: 7 out of 10
Incentivized

Use Cases and Deployment Scope

We primarily use Tasktop HUB within our organization to facilitate the integration of work items in our technology development life cycle between multiple work item management tools. This allows us to use one tool to manage the required deliverables and reporting.

Pros

  • Response to support cases are quick and the resources are very knowledgeable.
  • Monthly calls with Planview reps to discuss current issues and opportunities for growth facilitates good communication channels between orgs.
  • Detailed support documentation to aid in development and troubleshooting.

Cons

  • I'd like to see more robust reporting capabilities available from the UI.

Likelihood to Recommend

If used correctly in the hub/spoke model it can be very effective. If not implemented in this manner, it can lead to a lot of customizations to accommodate.
Vetted Review
Planview Hub
26 years of experience