Digital.ai TeamForge vs. Planview Hub

CollabNet TeamForge is more well-suited for technically knowledgeable users such as developers, systems analysts, QA but not for non-technical users due to the technical data used throughout the tool. CollabNet TeamForge is appropriate for most applications development. In any industry especially suited for high demand software delivery environments.

Incentivized

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.

Incentivized

• Code security.
• Code migration.
• Agile tie-in.

Incentivized

• 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

• I would like to see personalization for managing artifacts, that is, allowing the user to customize pages and save personalized settings and then save them as bookmarks.
• I would like an improved subversion browser such as a graphical user interface rather than a basic file explorer.
• I would like built in features for CollabNet TeamForge integrated with subversion so that i can associate my private code branches and code changes.

Incentivized

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

Incentivized

Planview TaskTop Hub supports our use cases. I think its continuous development goes in the right direction.

Incentivized

A great integration tool, which comes with a wide range of supported end tools. Planview TaskTop Hub works with an integration concept that maximizes the scalability and flexibility of integrations across more than just two tools. For example, from our experience, we started with the integration between Jama Connect and Jira. We were able to extend our integration concept to a new tool, Pro Cloud Server, by ourselves. The element was synced within 10 minutes.

Incentivized

We're hosting Planview TaskTop Hub by ourselves. The availability was good until now. A part of that, we have a strict plan for the quality control on any update of both Hub and End tools to avoid as much as possibily any disruptions.

Incentivized

Planview TaskTop Hub does generate traffic for some end tools. It is still in an acceptable range. For certain kind of retry to resolve issue in synchronizing relationships, an additional manual attention was required.

Incentivized

They always answer the phone when we put a call in, any time. They have consistently sent out contractors when needed and were there every step of the way when we switched over from ClearCase to TeamForge years ago. The support is what you really pay for when you buy into TeamForge.

Incentivized

I was considering giving a rating between 9 and 10. Overall, the support has been very good so far. However, I have noticed that the members of the support team have varying levels of know-how about Planview TaskTop Hub. When a ticket about a complex technical issue reaches a member such as Christoph T., Sr. Customer Engineer, the analysis is done thoroughly, and a sustainable solution is provided. With other members of the support team, the experience might be different.

Incentivized

We've received a good, in-deep training from Christoph T. during the implementation phase.

Incentivized

The integration documentation was sufficient.

Incentivized

We had a very good collaboration with the enabling team from Tasktop in 2018. The enablement program was adequately structured, starting with building an integration concept based on use cases of the synchronized data. The training provided a good foundation for us to operate and maintain the tool. The tool administration and architecture were straightforward.

Incentivized

CollabNet TeamForge is superior to Mercury mainly because it has a subversion change management tool integrated with the product. CollabNet TeamForge offers more complexity but with more flexibility for managing and tracking projects. I think
CollabNet TeamForge is more comprehensive than either Mercury and JIRA. They're all user friendly tools with short learning curves but CollabNet TeamForge is most efficient in my experience.
JIRA was recently adopted for particular applications and is currently being evaluated by various technology teams.

Incentivized

Jira Align does not synch items outside of JIRA and Azure Dev Ops; TT Hub is specifically utilized to address connections to various other SDLC application.

Incentivized

We don't need to deploy Planview TaskTop Hub in other units but we could extend the integration to cover the new data, new data type and new projects.

Incentivized

• Unfortunately, I do not have access to ROI information.

Incentivized

• We track monthly updates and each month there are typically over 30,000 updates being made which we know is saving time.