List view
Currently, we ask developers to set up their Java code mappings manually (because the SDK cannot determine it): https://docs.sentry.io/platforms/java/source-context/#setting-up-code-mappings Unfortunately, many stack traces do not contain in-app frames, thus, many Sentry features are not available (e.g. SCM linking, suspect commit). This tracks using the code mappings derivation system to automatically add the code mappings and stack trace rules to mark in-app frames as such. This will automatically enable the following Sentry features : - Suspect Commits - GitHub pull request comments - Auto-assignments (if Codeowners imported) - Stack trace linking - Code coverage (if the customer also has an account) This will only be available to customers with the GitHub integration installed. You can read more about the system here: https://blog.sentry.io/code-mappings-and-why-they-matter/
No due date•61/61 issues closedThis project will move any projects using the mobile grouping configuration as defined here: https://github.com/getsentry/sentry/blob/44d816f0b9a9450fdf47136313b3a4b955ceab84/src/sentry/grouping/strategies/configurations.py#L160-L188
No due date•2/2 issues closedThis will include same-root and trace-connected issues in the Similar Issues for the Issue Details page.
No due date•8/8 issues closed- No due date•10/17 issues closed
- No due date•1/1 issues closed
[GH Epic](https://github.com/getsentry/sentry/issues/52911) [Internal Product Doc](https://www.notion.so/sentry/Simplify-Issue-Details-e46fa194b0ef4256aa753ca9d6f4cd78) ### Problem: What problem is this solving? We want to make Issue Details more actionable for our users, so that they can go from alert/stream → debugging/triaging → fix as quickly as possible. We’ve added a lot of content to Issue Details, but haven’t taken a step back to prioritize & streamline what’s displayed. ### What are we aiming to do? - Provide a framework for quick iteration of the issue details UI - Improve the actionability of issue details - Promote consistency of experience - Make sure the experience per platform is great
No due date•33/34 issues closed- No due date•8/8 issues closed
- No due date•2/2 issues closed
- No due date•6/6 issues closed
- No due date•6/6 issues closed
- No due date•18/18 issues closed
- No due date•15/15 issues closed
- No due date•30/30 issues closed
- No due date•2/3 issues closed
Automatically detect severe regressions for backend projects for Sentry, create issues and display advanced change analysis output.
Due by September 29, 2023•26/30 issues closed- No due date•1/1 issues closed
Future work for discord integration
No due date•10/13 issues closed- No due date•22/22 issues closed
Come up with a POC model that lets us look at an incoming event, predict how severe/important it is (based on how people have engaged with similar events in the past), and decide whether or not to alert on it.
No due date•17/20 issues closedWith the new 2023 grouping config, we started incurring a higher processing cost per saved event. In order to bring it back under controlled a series of code changes will be perform to improve the understandability of the code and its performance.
No due date•20/20 issues closedhttps://www.notion.so/sentry/Tech-Spec-Notify-on-Disabled-Integration-Spec-e7ea0f86ccd6419cb3e564067cf4a2ef?pvs=4
No due date•19/19 issues closed- No due date•15/15 issues closed
- No due date•7/13 issues closed
Make common searches more accessible and discoverable for users. [notion page](https://www.notion.so/sentry/Search-Shortcuts-fka-Assignee-Filter-on-Issue-Stream-648954e782d04805bc64f1983e5cbd16?pvs=4)
No due date•13/13 issues closed- No due date•31/31 issues closed
- No due date•10/10 issues closed
Added new language/platform specific stack trace grouping enhancements rules that should make the default grouping experience better. This includes JavaScript, Python, PHP, Go, Java and Kotlin.
No due date•19/19 issues closed- Due by June 15, 2023•16/16 issues closed
- No due date•1/1 issues closed
- No due date•24/24 issues closed
This is a placeholder milestone for tracking post-v1 work for escalating issues. See the RFC: https://github.com/getsentry/rfcs/blob/main/text/0078-escalating-issues.md There's also discussions about escalation in here: https://github.com/getsentry/sentry/discussions/43039 V2 will focus on moving ongoing issues (upcoming) into the state archived-until-escalating after an issue being in the `ongoing` state for 14 days.
No due date•21/21 issues closed- No due date•53/53 issues closed
This will allow marking an issue as archived until escalating.
No due date•131/131 issues closed- No due date•8/8 issues closed
This is the work post-MVP release for the Codecov Integration, with UI and performance improvements and a new CTA.
Due by March 31, 2023•32/32 issues closedRelated to https://github.com/getsentry/sentry/discussions/42399
Due by February 17, 2023•36/36 issues closed- No due date•2/2 issues closed
This will track work that are known issues that will be handled after the GA. See related RFC: https://github.com/getsentry/rfcs/blob/main/text/0016-auto-code-mappings.md
No due date•15/15 issues closedVarious improvements to configuring Code Mappings by a customer. This milestones is simply to track the various related PRs.
No due date•16/16 issues closedPython is in EA already. We will first add JS to EA and then GA both of them. For JS, this will only apply to stacktraces that have source maps applied, otherwise, it is not possible to derive code mappings. Read https://github.com/getsentry/rfcs/pull/16 for more details.
Due by December 16, 2022•22/22 issues closedThis adds the ability of deriving code mappings automatically for all orgs using Python and Github at first. See RFC for details: https://github.com/getsentry/rfcs/blob/main/text/0016-auto-code-mappings.md
Due by November 25, 2022•16/16 issues closedThis milestones add support for creating Python code mappings automatically for orgs with the Github integration installed. This milestone initially focuses on Python projects. Future work described in this RFC: https://github.com/getsentry/rfcs/blob/main/text/0016-auto-code-mappings.md
No due date•26/26 issues closed- No due date•51/51 issues closed
See Discover graphs in Slack when you share a Discover chart URL.
No due dateSee Top 1 through 10 events, and toggle "Other" to see how the top n events compare with the remaining events.
No due dateOpen a Dashboard widget in Discover. Add a Discover Query to a Dashboard.
No due date•5/5 issues closedIn order to do development for Sentry, we need to spin up various Docker containers. Apple is moving away from Intel based chipset to arm64 chipsets (aka Apple Silicon). This milestones track all work required to make sure we can still use these development services on Apple's arm64 architecture.
No due date•13/13 issues closedApple started moving away from their Intel based chipset to arm64 chipsets (aka as Apple Silicon). In order to do Sentry development on this new architecture we need to do various changes to Sentry's development environment. Some of these changes include using a different Python version (arm64 support was added on Python 3.8.10), upgrading Python packages and hosting some Python wheels that third-party maintainers are not yet releasing.
No due date•19/19 issues closed- No due date•13/13 issues closed
- No due date•10/10 issues closed