PostHog / PostHog/posthog

Feature Request: Display events and persons automatically in tables and SQL results

Open
#42,406 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature/data-table feature/sql-editor team/product-analytics
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Feature request

If tables/SQL results include an 'event' column or 'person' column (based on e.g. the event's UUID, the person's ID) allow users the option of having those results displayed 'nicely' - e.g. linking to the person profile/the event - like we do elsewhere in PostHog.

Additional context

From: https://posthoghelp.zendesk.com/agent/tickets/43657 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/45711)

Debug info
Kind: feedback

Target area: analytics

Report event: http://go/ticketByUUID/5578fc92-984b-4af2-9205-52c82e9d5fc9

Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/019ac026-984d-74d0-b5ad-748922cc1b20?t=4181

Exceptions: https://us.posthog.com/project/2/error_tracking?filterGroup=%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22key%22%3A%22%24session_id%22%2C%22value%22%3A%5B%22019ac026-984d-74d0-b5ad-748922cc1b20%22%5D%2C%22operator%22%3A%22exact%22%2C%22type%22%3A%22event%22%7D%5D%7D%5D%7D

Location: https://eu.posthog.com/project/13448/sql#q=SELECT%0A%20%20%20%20e.timestamp%2C%0A%20%20%20%20concat('https%3A%2F%2Feu.posthog.com%2Fproject%2F13448%2Fpersons%2F'%2C%20toString(e.person.id))%20as%20person_url%2C%0A%20%20%20%20concat('https%3A%2F%2Feu.posthog.com%2Fproject%2F13448%2Fevents%2F'%2C%20concat(e.uuid%2C%20'%2F'))%20as%20event_url%2C%0A%20%20%20%20e.properties.errorType%20AS%20errorType%2C%0A%20%20%20%20e.properties.scope%20AS%20scope%2C%0A%20%20%20%20e.properties.httpStatus%20AS%20h...&

Persons-on-events mode for project: person_id_override_properties_on_events

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the SQL results table renderer and existing person/event link handling in PostHog. Trace how result columns are identified, then verify queries containing event UUIDs and person IDs, including the user option for enhanced display. Done means matching values are displayed clearly and link to the corresponding event or person without changing ordinary results.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
analytics, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.