Skip to main content

​
Configuring Jira

1
Click on Enable button for Jira
2
Click on Connect button on the modal
3
Select the Jira team that should be associated with the QA Wolf team
4
Click on Accept button.
5
Set all the Project fields to the project we want to integrate with.
6
Enable all toggles.
7
Extra customization fieldsa. Custom fields expects an JSON that will be merged with the default fields when creating an issue. It is useful for Jira projects with required custom fields.b. Custom description field name is used to define a custom field name for the description field. Some Jira projects have alternative names for the description.

​
Configuring Linear

Update 8/8/23: There was a bug in our Paragon workflow that prevented us from receiving Linear Issue events from new Linear teams. The updated Paragon workflow will register for Linear Issue events for all teams, existing and new. Customers that are already connected (as of 8/8/23) to Linear will not receive events for new Linear teams. To get events for all new and existing Linear teams, disconnect and reconnect to the customer’s Linear org. Please make sure that we have access to their linear org (check 1Pass) before disconnecting their org. Otherwise, you will need to coordinate with the customer to reconnect their Linear.
1
Click on Enable button for Linear
2
Click on Connect button on the modal
3
Configuring for a team:a. Type the Team name exactly as in Linear (it is case sensitive).b. Enable all toggles.c. (Optional) set Label UUID and Assignee UUID to set a label and assignee for newly created issues.

​
Configuring Asana

1
Click on Enable button for Asana
2
Click on Connect button on the modal
3
Enable bug reports and select the workspace and project in which bug reports are going to be created.

​
Configuring Webhooks

​
Basic Setup

Good when you only want to be notified when bugs are opened
1
On the team settings page, enable the webhook integration
2
Click on connect
3
Define a webhook title
4
Define the webhook URL and enable “Notify when bug report is opened”
5
When an issue is created, your endpoint will receive POST requests with a JSON body (Content-Type: application/json). Here’s the expected structure and an example payload.

​
Expected JSON Body Fields

The primary data is in the request body:
  • id (string): Unique bug report ID.
  • title (string): Bug report title.
  • description (string): Detailed description (may contain newlines/links).
  • url (string): Link to view the bug report in QA Wolf.
  • event (string): bug-report-opened.

​
Example Payload

This example shows the full request structure your endpoint will receive:
JSON
{
  "id": "<QAWOLF_BUG_REPORT_ID>",
  "title": "Bug Report Title",
  "description": "🐞\n\nBug report description:\nYou can see it here.\n\nBug report:\nhttps://app.qawolf.com/test-client/bug-reports/...\n\nAffected workflows:\n\n\nIf you are aware of this bug you can set the priority to low which will prevent it from causing a run failure.",
  "url": "https://app.qawolf.com/bug-reports/...",
  "event": "bug-report-opened"
}

​
Authentication

If username and password are set, those will be used for basic HTTP authorization when performing the POST request against your webhook.

​
Complete Setup

Relevant when you want to be notified that bugs were closed.
Finish the Basic Setup before starting this.
1
Enable the “Notify when bug report is closed” toggle:
2
Make your webhook respond to the POST request a payload containing these fields:
  • externalId (string): ID of the issue for the QA Wolf bug report in your issue tracker. It will be used to notify the issues that must be updated in the future.
  • humanId (string): Human friendly issue ID that will be used on QA Wolf UI, Slack messages and other integrations.
  • url (string): Link to the issue.
3
When a bug report is closed, your endpoint will receive POST requests with a JSON body (Content-Type: application/json). Here’s the expected structure and an example payload.

​
Expected JSON Body Fields

The primary data is in the request body:
  • externalId (string): The ID of the issue associated with the closed bug report.
  • event (string): bug-report-closed.

​
Configuring Azure DevOps

1
Access https://dev.azure.com/ <ORGANIZATION_NAME>/_settings/organizationPolicy where <ORGANIZATION_NAME> is the DevOps organization name. (We may need to request an authorized user to do this).
2
Enable Third-party application access via OAuth
3
In QA Wolf, on the team settings page, enable DevOps for the team.
4
Click on the connect button.
5
Select “Azure DevOps Service”.
6
Insert the organization name and continue.
7
Go to configuration and set the target project.
Last modified on February 9, 2026