Major Upgrade: Making Issues Even More Actionable

by Jason St. Pierre, Product Manager


Having deep, actionable data as a developer is the key to building great apps. This is something we’ve kept in mind ever since we embarked on solving crash reporting. The real power of a crash reporting service is to distill mountains of information, organize crashes into groups and prioritize these crashes by impact. In Crashlytics, we already surface the most prevalent issues for you — but we didn’t stop there.

Today, we’re taking crash reporting to the next level by giving you enhanced visibility into an issue’s lifecycle. Now, you’ll be able to better manage your view into issues across versions from the first version that the crash occurred to the most recent version we see it causing a problem. We’ll even tell you if and when the same problem regressed along the way.

Optimal organization of your data

Previously, new issues were scoped to a particular version. Now, your dashboard will automatically merge the data about an issue occurring across versions so you can see that issue in a single row along with the range of versions it affects.                                                                                                    

With this upgrade, and with minimal effort, you’ll have an even deeper understanding of the impact of these issues. You can still filter by a particular version to see how that version is impacted, and when you filter to just one version on the dashboard, we’ll let you know if an issue is also occurring on the other versions.

Total visibility into an issue’s life cycle

Within a crash report, you now have a pristine visual representation of the lifecycle of a specific bug or issue across all versions. You’ll be able to see all of the versions a particular crash is occurring on, which gives you a complete picture of how an issue is affecting your builds. If you need to identify the most affected version, or get a breakdown on the number of crashes by build, your new dashboard has you covered.

By being able to access the impact of bugs and issues across multiple versions, you can fully understand the lifecycle of your app’s bugs or issues. You can see how long an issue has been persistent and its severity to focus on those that matter most, and ship the most important updates.

More powerful: Regression detection & issue ignore functionality

With cross version issue support we also added two new features: regression detection and the ability to ignore issues. Regression detection alerts you when you close an issue, and the same issue appears on a new version later. Don’t worry -- we’ll notify you when an issue creeps back up after you’ve closed it as these regressions are usually warning signs you'll want to pay close attention to.

Sometimes there are things that aren’t regressions, they are just issues you know are going to occur. You may choose not to fix them because they aren’t issues in your code. Now, you can lock and ignore issues that you know will be present for many versions. By having this added control, you can now further fine tune your dashboard to bubble up the true, critical information that needs your immediate action.

Enhanced Answers integration

Besides managing issues, the team at Answers upgraded our integration to allow you to see crash-free users and sessions by versions on your Answers dashboard. Now, you can dive into each build and see the crashes affecting its stability. Learn more about this upgrade in Answers’ August update.

We couldn’t be happier to get these upgrades into your hands and help you to continue to build awesome apps. Log in to check out the new issues dashboard, or sign up if you don’t have Crashlytics yet!