The Create via Gateway template is only available in Editions that contain the Gateway add-on. See Tasktop Editions table to determine if your edition contains this functionality.

This integration connects teams working in different tools as they fulfill their roles in the software development lifecycle.  

As part of this integration, work items will flow between separate repository collections.

This integration connects teams working in different tools as they fulfill their roles in the software development lifecycle.  

As part of this integration, work items will flow between separate repository collections.

Additionally, the containers in which your work items reside will be mirrored across the collections according to your specification.

This integration creates traceability between artifacts across the software development lifecycle. New artifacts will be created in a repository collection when artifacts are sent to Hub via a Gateway collection, through an inbound webhook.

This integration creates traceability between artifacts across the software development lifecycle.  Already existing artifacts in a repository collection will be located and modified in a specified way when artifacts are sent to Hub via a Gateway collection, through an inbound webhook.

Learn More

This integration template is only available in editions that have access to the Git repository.  

This integration template is only available in editions that have access to the Git repository.  

This integration creates new work items such as changesets or code commits in a repository such as Jama, when they are sent to Hub via a read-only collection connecting to a repository such as Git.

These types of events are “fire and forget” - they create something new in your repository, but they don’t expect anything back. As such, they don’t mandate a full-blown two-way synchronization; a lighter one-way integration can do the trick.  

This integration flows information from an outbound only collection (such as Git Commits) to a field on an existing artifact in a work item collection (such as Jama Codes).

These types of events are “fire and forget” - they create something new in your repository, but they don’t expect anything back. As such, they don’t mandate a full-blown two-way synchronization; a lighter one-way integration can do the trick.  

This set of integrations flows Test Result information on a Test Run in ALM or Tosca.

To ensure proper test artifact hierarchy is preserved within each tool, Test Folders, Tests, Test Set Folders, Test Sets, and Test Instances are also synchronized.