Use grouping stacktrace frames when generating a Jira ticket #100069
Description
Problem Statement
When we use the Jira integration in Sentry to create tickets, the preview stacktrace it includes will use in-app frames if available. If there are no in-app frames but there are frames used for grouping, it ignores them and simply includes the top 4-5 frames. This makes the preview unhelpful because there's no way to see context without having to go to the Sentry event and find the part of the stacktrace that is relevant.
Solution Brainstorm
Ideally the Jira integration would cascade through different priorities for producing a preview stacktrace similar to how grouping uses different rules and levels when displaying in the portal.
- In-app frames
- Frames used for grouping
- ???
- Frames from the top
Product Area
Issues