A new release of Tasktop Integration Hub, 19.1, is available today, including support for Jira Cloud API changes related to GDPR, a new connector for XebiaLabs XL Release, and features that make it easy to move project routings between integrations and provide one final update to twinless artifacts.
Below are the release highlights. For full details on new product features, supported artifacts and endpoints, check out the release notes and connector documentation.
Support for Jira Cloud API Changes Related to GDPR
Atlassian recently introduced a number of changes to its products and APIs to improve user privacy in accordance with GDPR. These changes to user identification affect all Tasktop customers with integrations for Jira Cloud (on-premise Jira products are not affected).
The new release supports these changes to ensure seamless operation of your Jira integrations when Atlassian completes their GDPR updates at the end of March.
If your organization uses Jira Cloud, upgrading to the latest version of Tasktop Integration Hub is mandatory by March 29. Tasktop admins can access the upgrade through their my.tasktop.com account or by contacting Tasktop Support. Our product documentation provides detailed instructions on upgrading and updating extension scripts related to user identification.
It’s important to note that Zephyr Cloud will also be affected by these changes, but the company has yet to confirm the date that its corresponding updates will go live. For this reason, Zephyr users should not upgrade their Tasktop instance at this time. Instead, we are asking our customers with Zephyr Cloud integrations to contact us at their earliest convenience to discuss the right time to upgrade.
New Product Support: XebiaLabs XL Release
Tasktop supports hundreds of DevOps tools through our Gateway integration style – a RESTful API for fire-and-forget events – which is suitable for many release automation and orchestration functions. We’re now introducing the Synchronization integration style for XebiaLabs’ popular XL Release tool. This new connector enables point-and-click configuration for sophisticated synchronization use cases between XL Release and nearly 60 software delivery tools that house long-lived collaboration work items, such as features, stories, requirements, tests, defects, problems and incidents.
Tasktop can synchronize release artifacts – including start and end dates, status, descriptions and tags to other tools – from XL Release to other tools, with several benefits:
- Eliminate duplicate data entry and human error. Release information is populated automatically from the source to other tools
- Create visibility into release status for practitioners that don’t normally use XL Release, like product owners, project managers and developers
- Create traceability between artifacts and releases by flowing the information through Tasktop Integration Hub’s models
In our newest demo video we show how releases created and managed in XL Release are synchronized to an Agile Planning tool like Targetprocess. From there, product owners can assign features to the release and percolate the work down to the developers in Jira. The product owners can also view changes to the release status as it progresses, directly from within their tool of choice.
Twinless Artifact Update
When Tasktop Integration Hub synchronizes artifacts between two repositories, it first creates a twin for the source artifact in the destination repository. Then, over the lifecycle of the artifacts it keeps both twins in sync.
But what happens when the artifact in one of those repositories is deleted or no longer meets the criteria to flow? The remaining twin will stop receiving updates, without the practitioners knowing why. Meaning they may continue to do work on something that is no longer valid.
This new feature ensures that when one of those twins is deleted or no longer meets the criteria to flow, the other twin is notified. Admins can set a rule that sends one final packet of information to the other side to explain, for example you can add a comment like “this artifact was deleted”, or set the status to Closed or Invalid.
Easily Move Project Routings between Integrations
There may be rare scenarios when you must move routes from an existing integration to another integration. For example, you may realize you can combine multiple integrations into one or actually need to split one integration into two. You may also be in the process of upgrading Micro Focus (HPE) ALM, which requires moving integrated projects to a new server.
This new feature allows you to easily migrate routes to a new integration without redoing all the work, providing they are similar in style, artifact type and repository.
Also in Version 19.1
- Set up your Jama integrations faster with the ability to route outbound artifacts by component, instead of set by set
- Ensure that your repository connections meet your organization’s security standards. In 19.1, the Tasktop admin can set an optional requirement that Tasktop access external tools via HTTPS or with an SSL certificate
Want to know more about Tasktop Integration Hub?
Request a highly-personalized product demo to see the myriad benefits that Value Stream Integration can bring to your software delivery teams and business.
