Sprint - Sep 16 to Sep 27

[pauldambra]

Global Sprint Planning

3 things that might take us down

Urgent incident follow-ups

https://github.com/orgs/PostHog/projects/103/views/2

Team sprint planning

For your team sprint planning copy this template into a comment below for each team.

# Team ___

**Support hero:** ___

## Retro

<!-- Grab the high and low priority items from last time and add whether that item was completed or not -->

- 

## Hang over items from previous sprint

<!-- For each item, decide to re-prioritise (and add below) or deprioritise -->

- Item 1. prioritised/deprioritise

## OKR

1. OKR, status (red/yellow/green) and action points if yellow/red


### High priority

-

### Low priority / side quests

-

[pauldambra]

Team Replay

Support hero: @pauldambra

a few short bits of leave but generally folk in full time

Retro

High priority

✅ done
🟢 in progress, on track
🟡 in progress, off track
🔴 missed

High priority

Mobile

• Masking and redacting Jetpack Compose views (issue) @marandaneto
• Support person_profiles in Android and iOS @marandaneto
• RN session replay more automatic via npm, not copying code snippets @marandaneto

Error tracking

• Django integration for autocapture @neilkakkar
• Rewrite events lookup as subquery @daibhin
• Per exception alerting configuration (snoozing / ignoring / archiving) @daibhin
• Filter exceptions by assignee @daibhin
• Stack traces @neilkakkar
  • Decide with CDP on approach for tackling stack traces
  • Begin implementation...

Session replay

• 🟢 Network logs not capturing everything @pauldambra
  • will need follow-up since this is going to be really site dependent but made progress with posthog-js 1.160.3
• 🟢 Sessions >24 hours bug (browser online / offline events) @pauldambra
  • draft up at fix: teardown and restart recording on session id change posthog-js#1411
• 🟢 Dropped / compressed messages work revisited @pauldambra
  • lost some custom signal with rust capture / warp stream. but now accepting much larger messages. still getting some which means we do have messages >64MB, want to get examples of these so we can target next steps

Low priority / side quests

• Review Replay UX issues & decide on quick wins @daibhin
• New replay filters (click counts, random sessions, new users) @daibhin
• Filtering internal users issue (PoE confusion)
• Integrate session recordings into error playlist (quick version) @daibhin

OKR

1. OKR, status (red/yellow/green) and action points if yellow/red

• 📱Goal 1: People think of PostHog as a mobile solution 🟡
• 🪲 Goal 2: Error tracking in people's hands 🟢
• ⁉️ Goal 3: Hiring ✅
  • Neil's joining the team! 🟢
  • Richard joingin the team! 🟢
  • iOS Engineer 🔴

High priority

Mobile

Error tracking

Session replay

Low priority / side quests

[pauldambra]

oh no #24890