# Which mobile crash reporting tools integrate with project tracking platforms for automated issue creation?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Hello G2 community, I’m looking into crash reporting tools that can automatically move useful issues into Jira, GitHub Issues, or another project tracker without forcing teams to copy context manually.</p><ol>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/sentry/reviews"><strong>Sentry</strong></a><strong>:</strong> Integrates with GitHub, Jira, GitLab, and Azure DevOps, while linking errors to suspect commits. Does its automation create tickets with enough context to act immediately?</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/rollbar/reviews"><strong>Rollbar</strong></a><strong>:</strong> Can send detailed errors to Jira and use custom conditions to decide when tickets are created. How well has its grouping prevented duplicate issues?</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/raygun/reviews"><strong>Raygun</strong></a><strong>:</strong> Provides detailed root-cause information, although reviews are less explicit about automated ticket creation.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/google-firebase-crashlytics/reviews"><strong>Firebase Crashlytics</strong></a><strong>:</strong> Connects with Jira and Slack and also integrates with Android Studio.</li>
</ol><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">What threshold does your team use before a crash automatically becomes a tracked ticket?</p>

##### Post Metadata
- Posted at: about 2 months ago
- Author title: Marketer
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;&lt;span style=&quot;color: rgb(0, 0, 0);&quot;&gt;An automated ticket from a crash report is only useful if it has enough context attached that someone doesn&#39;t have to go dig through logs anyway. I&#39;d test that handoff specifically before trusting the integration.&lt;/span&gt;&lt;/p&gt;

##### Comment Metadata
- Posted at: about 12 hours ago
- Author title: Marketing



### Comment 2

&lt;p&gt;Affected users feels like a much better threshold than raw crash count. I’d also want severity or release context in that rule, though, because a low-frequency crash in checkout or login could deserve a ticket immediately. Have you seen teams combine affected-user thresholds with specific app flows or new-release detection without making the automation too complicated?&lt;/p&gt;

##### Comment Metadata
- Posted at: 4 days ago
- Author title: Writer



### Comment 3

&lt;p&gt;On thresholds, the pattern that seems to hold is basing it on affected users rather than crash count. One user hitting the same crash in a loop generates a lot of events and very little business impact, while a crash hitting fifty people once matters immediately. Sentry and Rollbar both let you set conditions that way, and it changes what the ticket queue looks like.&lt;/p&gt;

##### Comment Metadata
- Posted at: 5 days ago
- Author title: Tech Consultant



### Comment 4

Rollbar&#39;s custom conditions for ticket creation are the most useful feature here. Without thresholds, automated Jira issue creation turns into alert spam. The grouping quality is what determines whether engineers open the ticket or start ignoring the integration entirely.

##### Comment Metadata
- Posted at: about 2 months ago
- Author title: Writer





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4