Skip to content
Codeskop

Crash, error and API monitoring for the whole team

How a bug moves through Codeskop

One checkout crash, from the customer's report to the release that recovers. Five people, one issue, and no screenshots pasted into chat.

Start for free See every feature

  1. 1Support

    A customer says checkout crashed

    Support looks the customer up by their user ID (or by email, if a workspace owner or admin has turned on email lookup) and opens their latest session: the failed payment call, then the crash. They comment on the issue with what the customer reported and @mention QA.

    user_48213 · latest sessionAndroid · 2.4.1
    1. ScreenCartActivity
    2. Eventcheckout_started
    3. API call failedPOST /v1/orders · 502
    4. CrashNullPointerException in CheckoutActivity

  2. 2QA

    QA reproduces it on a test build

    Following the steps in the journey, QA makes it happen on a build with a test key. The crash arrives in the test environment with the same stack trace, and QA confirms it on the issue for the team to see.

    ActivityIn progress
    • Assigned to Amina

    • Sam · 2 min ago

      Reproduced on the test build after a failed order call. Amina can you take a look?

    • Status changed to In progress
    • Ticket ENG-88 created

  3. 3Product

    Product weighs the impact

    The issue shows how many users it hit. The checkout funnel shows how many of the users who dropped at payment had this crash or the failed call. Product moves it to To do and assigns it to a developer.

    Checkout funnelLast 30 days
    • Cart viewed100%
    • Checkout started64%
    • Order completed41%

    Why users dropped off at checkout

    Users who left had failed calls to POST /v1/orders and a crash in CheckoutActivity.

  4. 4Developer

    A developer fixes it, with the evidence attached

    The assignee hears about every new comment. They create a ticket in Jira, Linear, GitHub Issues, Asana or ClickUp with the stack trace and steps already written, or ask Fix with AI for a draft pull request to review. Status moves to In review, then Completed.

    New ticketENG-88

    Crash on checkout submit

    Summary
    Crash · critical · 52 events, 31 users · first seen 2 days ago
    Stack trace
    at CheckoutActivity.onSubmit (CheckoutActivity.kt:118)
    Where it happens
    2.4.1 · Pixel 7 · Android 14
    What the user did first
    CartActivity → checkout_started → POST /v1/orders 502

  5. 5Engineering lead

    The lead watches the release recover

    Release health showed the bad release regress. Now it shows the fixed release's crash-free users climb back above it, a regression rule alerts the team if the issue ever comes back, and Monday's digest sums up the week for everyone.

    Release healthProduction
    • v3.4.198.91% crash-free users−0.61 pts vs previous · 3 new issuesRegressed
    • v3.4.099.52% crash-free users+0.05 pts vs previous · 1 new issue
    • v3.3.299.47% crash-free users2 new issues

By plan

What each step needs

The shared issue, with comments and @mentions, is on every plan. The deeper context comes with Starter and Growth.

  • Every plan

    Crash and error reporting, users affected, the test environment, comments, @mentions, assignment, status, the activity timeline, release health, the weekly digest and email alerts for one project.

  • Starter and above

    Alerts (including regressions) in Slack, WhatsApp and webhooks, network capture and ANRs.

  • Growth and above

    Finding a user, the user journey, the Users tab, product analytics, tickets and Fix with AI.

See pricing, or the pages for QA teams, product managers, support teams, engineering leaders and developers.

Frequently asked questions

Which plan do we need for the whole story?

Growth and above covers every step, including the user journey, funnels, tickets and Fix with AI. The core of it (crash reports, users affected, comments, @mentions, assignment and status) works on every plan, including Free.

Does everyone on the team need a seat?

Everyone who joins is a team member: Free includes up to 5, Starter up to 15, and Growth and above unlimited. Seats aren't billed.

Do product and support need to read stack traces?

No. They see users affected, app versions and devices, the user's journey and the discussion on the issue. Developers get the stack trace in the same place.

Can we keep our ticket tracker?

Yes. Tickets go to Jira Cloud, Linear, GitHub Issues, Asana or ClickUp (Growth and above), and the issue links to the ticket so nobody files it twice.

Does Codeskop merge fixes by itself?

No. Fix with AI opens a draft pull request only after a person reviews and approves the proposed change, and it never merges anything. Your normal review and CI take over.

Know what broke. Fix it faster.

Bring your whole team into the same issues.

Set up in minutes. Free plan for up to 5 team members, no credit card required.

Start for free View pricing