# Issue Trackers

{% hint style="warning" %}
Some organizations restrict access to their issue tracker by IP address. If you need to allow access to BugSplat, add the IP addresses [23.22.79.2](https://www.whatismyip.com/23.22.79.2/?iref=home), [3.93.104.250](https://us-east-1.console.aws.amazon.com/ec2/home?region=us-east-1#ElasticIpDetails:AllocationId=eipalloc-0da0d84b88eed6812), and [34.194.164.107](https://us-east-1.console.aws.amazon.com/ec2/home?region=us-east-1#ElasticIpDetails:AllocationId=eipalloc-0cd966956c064a2e4) to your whitelist.
{% endhint %}

BugSplat connects with popular defect trackers, allowing users to create new issues with a few clicks directly from a crash or stack key.

This allows teams to build issues that contain full crash information, like symbolic call stacks, as well as other crash-specific data that can help your team crush bugs faster. Issues created from BugSplat also include hyperlinks that allow users to quickly navigate between issues and the crash or stack key associated with them.

**Note** you can see our doc for automatically creating issues in your defect tracker from BugSplat databases [here](/introduction/development/integrating-with-tools/issue-trackers/automatic-issue-creation.md).

{% content-ref url="/pages/-MeRm\_QW\_0YKfGsAKMST" %}
[Azure DevOps](/introduction/development/integrating-with-tools/issue-trackers/azure-devops.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MeRp\_ze4F1HvmoZNY7R" %}
[GitHub Issues](/introduction/development/integrating-with-tools/issue-trackers/github-issues.md)
{% endcontent-ref %}

{% content-ref url="/pages/mCciyckqm4gBXS1tS5LS" %}
[GitLab](/introduction/development/integrating-with-tools/issue-trackers/gitlab.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MeRmPwjeAY34HTF9ob3" %}
[Jira](/introduction/development/integrating-with-tools/issue-trackers/jira.md)
{% endcontent-ref %}

{% content-ref url="/pages/6nWUxwaYMEvyym07q4sW" %}
[Favro](/introduction/development/integrating-with-tools/issue-trackers/favro.md)
{% endcontent-ref %}

{% content-ref url="/pages/BHocNLPys1J6XtI42UAl" %}
[Monday.com](/introduction/development/integrating-with-tools/issue-trackers/monday.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MeRqI7K25052Hxio3Hi" %}
[YouTrack](/introduction/development/integrating-with-tools/issue-trackers/youtrack.md)
{% endcontent-ref %}

### Additional Features

{% content-ref url="/pages/AsZctUH6CXVz19ZwXSjH" %}
[Automatic Issue Creation for Defect Tracker Integrations](/introduction/development/integrating-with-tools/issue-trackers/automatic-issue-creation.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bugsplat.com/introduction/development/integrating-with-tools/issue-trackers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.