Tasktop Hub 22.2 Release

What’s New in Tasktop Hub 22.2

Posted by

Say hello to Tasktop’s latest product release from its Value Stream Management platform. Tasktop Hub 22.2 is out today, making end-to-end toolchain integration faster, easier, and visibly impactful.

The highlight of this release is the addition to Hub’s Metrics screen which now calculates the cost savings from your integrations. We’re also continuing on our mission to make Tasktop Hub easier to use and are introducing additional configuration improvements to simplify integration setup.

Read on to learn more!

ROI Metrics 

You know it and we know it: Tasktop Hub saves your organization time. But in the spirit of making work visible, we’re bringing those savings front and center. New ROI metrics bring the value of Hub’s tool integration to the Metrics screen. As an Administrator, it will help you quantify the tremendous time savings you gain with Hub so you don’t have to scramble to prove the value come budget time. 

Calculated ROI on Tasktop Hub

For more information, check out our video and our docs site.

Configuration Improvements

We’re always trying to improve your day-to-day work by making things *just* a little bit easier. With the 22.2 release, there are two new configuration options that will help you speed things along without losing track of the details.

First, we’ve given you more options for change detection and full scan settings. You already had the option to set defaults at the Global and Integration levels, but now, Repositories can be configured with their own settings as well.  The order of precedence will always be Integration → Repository → Global. That middle layer means Repository settings override the Global settings so administrators have the flexibility to create specific integration settings for tools that need to adjust the frequency of change detection or full scans.

This means you can create settings quickly and apply them more broadly, saving you time and manual work. Learn more in our docs or in the Change Detection FAQ.

Next, person reconciliation just got easier, with Hub’s new ability to set a default person for each Collection. If Hub encounters people in discrete Collections who can’t be reconciled based on name, ID, and/or e-mail, it will revert to this default user instead of sending you an error message. For more information, check out our docs.

Related resources for learning more:

Leave a Reply

Your email address will not be published. Required fields are marked *