JIRA webhooks based integration

The TeamForge Integration for JIRA® Webhooks collects issue data from your JIRA Server or JIRA Cloud for purposes of associations, traceability, and event reporting.

Overview

This integration relies on JIRA’s webhooks mechanism to send issue data to TeamForge EventQ for purposes of associations, traceability, and event reporting. Being webhooks-based, there is no adapter or software to install; simply configure TeamForge and JIRA webhooks to communicate with each other and start creating associations, traceability, and events reports based on JIRA data within TeamForge. With no adapter to install, TeamForge Webhooks Integration for JIRA is ideal for use with JIRA Cloud.

Viewing associations and traceability

Because there’s no need to install plugins, there is no mechanism to visualize associations between TeamForge objects and JIRA issues from within JIRA. To visualize associations, please use the Source Code tool in TeamForge.

Prerequisites

This integration is subject to limitations imposed by JIRA Webhooks and JIRA Cloud, see Atlassian ^® Documentation for specifics. In particular:

TeamForge HTTP or HTTPS access must be configured on ports 80 or 443 respectively. JIRA Cloud does not support alternate port configurations for webhooks.
If using HTTPS, TeamForge must be configured with a valid SSL certificate signed by a certificate authority to be an eligible JIRA Cloud webhooks consumer. Self-signed certificates are not supported by JIRA Cloud. This is a limitation JIRA Cloud imposes on webhooks consumers.

TeamForge Integration for JIRA Webhooks is a point-to-point integration, therefore the following ports must be configured for access:

Port	From	To	Description
443/80	JIRA web server	TeamForge web server	JIRA sends webhooks payload to TeamForge