Jira is often used by engineering and product teams and contains a lot of workflows within, and between these teams. This guide shows you how to configure the events most relevant for company's collabortive workflow analytics.
In this article, we create a webhook integration between Jira and Flowtrace and show how to configure the relevant events.
Creating a webhook for Jira organization or repository
Configuring the webhook to send individual events (optional)
To complete this integration you need:
Administrator rights to your GitHub project(s) and/or organization
Administrator access to Flowtrace
1. Creating a webhook for Jira account
Creating a webhook in Jira is easy. You can follow the complete instructions from Atlassian's own document.
Before you create a webhook you should consider your issue workflows, and project structure and how to best analyse most of your collaboration across them. We recommend creating an account wide webhook, which captures all projects and issues. You can alternatively create specific project webhooks using Jira's query language (JQL) for your needs. The process is same either way you choose to do it.
Name, URL, and Issues Selected using JQL
Fill in the name for your integration and defined the scope of issues you are planning to analyze. For URL you need to access Flowtrace integration page. By clicking "Copy webhook URL" in Flowtrace integration page you will get the unique URL for your Flowtrace integration.
2. Configuring the webhook to send events
Not all events in your Jira are of interest to your collaborative analytics. We recommend by minimun selecting all the issue events, and your sprint events. You can choose to send us only the events which are triggered by people and indicative of purposeful professional collaboration as well.
After you click create your webhook, you can test it by opening an issue, creating a comment, or doing another action which triggers an event. You can go to Flowtrace Integration page to confirm we have received the event via "Last active" field.