DAST

Raising GitHub issues automatically

• Last updated: November 5, 2026

• Read time: 5 Minutes

Add triggers to an action to raise GitHub issues automatically for the Burp Suite DAST issues that match them.

Adding a trigger for GitHub issues

Without a trigger, you raise GitHub issues from an action by hand. A trigger raises a GitHub issue when a scan finds a Burp Suite DAST issue that matches its severities, confidences and sites. An action can have several triggers.

To add a trigger, you need the Modify settings permission. You also need permission to view the sites and issues of every site or folder that you select. Burp Suite DAST hides sites that you cannot view. It also hides any trigger that covers only those sites.

To add a trigger:

1. Click the settings icon in the top-right corner.
2. Click Integrations.
3. On the GitHub tile, click Edit.
4. For your connection, click Manage actions.
5. For the action, click Manage triggers.
6. Click Add trigger.
7. Under Threshold for raising a ticket, select at least one Severity and at least one Confidence.
8. Under Select sites, select the sites and folders that the trigger applies to. A folder covers everything beneath it.
9. (Optional) To include the Burp Suite DAST issues that you already have, select Raise tickets for all issues from the most recent successful scan.
10. Click Save.

Editing and deleting a GitHub trigger

To edit a trigger, click Manage triggers for the action, then click the trigger.

To delete a trigger:

1. Click Manage triggers for the action.
2. Click the Delete trigger icon for the trigger.
3. Click Delete.

You cannot undo a deletion. Burp Suite DAST records changes to triggers in the user activity log.

Burp Suite DAST issues that raise a GitHub issue

• The Burp Suite DAST issue must be in a site that the trigger covers, directly or through a folder.
• The severity and confidence of the Burp Suite DAST issue must both be selected on the trigger. Burp Suite DAST uses the values that you set on an issue, if you changed them.
• Burp Suite DAST issues that you mark as false positives never raise GitHub issues. Burp Suite DAST issues that a newer scan replaces never raise them either. If you try to save a trigger for a false positive, then Burp Suite DAST shows a False positives can't raise tickets automatically error.
• Burp Suite DAST evaluates each Burp Suite DAST issue as it processes a scan. A trigger therefore affects the next scan, not the Burp Suite DAST issues that you already have.

The GitHub issue uses the repository and fields of the action. Burp Suite DAST also adds the severity and confidence labels of the Burp Suite DAST issue to the GitHub issue.

Avoiding duplicate GitHub issues

Burp Suite DAST raises at most one automatic GitHub issue for a Burp Suite DAST issue, per connection, per repository:

• If the Burp Suite DAST issue already has a GitHub issue on that connection in that repository, Burp Suite DAST raises nothing. A GitHub issue that you raised through Burp Suite DAST counts, whether you raised it by hand or automatically. A GitHub issue that you added with Link to existing ticket does not count.
• If two actions on the same connection use the same repository and both match, the action created first raises the GitHub issue.
• Actions that use different repositories each raise their own GitHub issue. Two connections also raise their own GitHub issues.
• If Burp Suite DAST loses a response from GitHub, it searches the newest 1,000 GitHub issues and pull requests in the repository for the GitHub issue that it already raised. If it does not find the GitHub issue, it does not raise a second one. It checks again later.

Raising GitHub issues for Burp Suite DAST issues you already have

To raise GitHub issues for the Burp Suite DAST issues that you already have, select Raise tickets for all issues from the most recent successful scan when you save a trigger. Burp Suite DAST raises GitHub issues for the Burp Suite DAST issues in the most recent successful scan of each site. It applies the same rules and duplicate checks as automatic raising.

The option applies only to the trigger that you save. Burp Suite DAST does not store the option, so select it each time you need it. Burp Suite DAST raises these GitHub issues gradually in the background and shows no progress. For a large number of sites, this may take a while.

Troubleshooting automatic GitHub issues

If an action cannot raise a GitHub issue for a severity and confidence that one of its triggers covers, then the action shows a Can't raise automatically message with the reason. Fix the action before the next scan.

If Burp Suite DAST fails to raise a GitHub issue, the connection shows the reason for the latest unresolved failure:

Reason	What it means
Ticket refused. Check the action's settings.	GitHub refused the GitHub issue. Someone may have renamed, moved or archived the repository, or turned off issues. If the milestone is no longer valid, then the action shows a The chosen milestone isn't valid. Choose it again. error.
Credentials rejected. Check them and try again.	The personal access token of the connection expired, or someone revoked it.
The account is missing permissions. Check them and try again.	The token lacks a permission, or lacks access to the repository.
No compatible service at this URL. Check the URL.	Burp Suite DAST cannot use the connection URL. The This URL redirects elsewhere. Check the URL., Can't connect to this URL. Check the URL and network. and This URL can't be used. Enter a public https URL. errors mean the same.
Unexpected response. Try again later.	GitHub returned an error, or reached its rate limit. Burp Suite DAST waits until the rate limit resets. For a secondary rate limit, it waits a minute.
Tickets couldn't be raised. Try again later.	Burp Suite DAST recorded no more specific reason.

Burp Suite DAST retries a failed GitHub issue in the background with a growing delay. The delay starts at a few minutes and doubles up to once a day. For rejected credentials and missing permissions, it waits at least an hour. It does not retry a GitHub issue that GitHub refuses. To retry the waiting GitHub issues right away, fix the problem and save the connection.