PostHog / PostHog/posthog

Clarity about date range selection when defining action, using data table

Open
#24,554 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

When defining an action, it appears that the query only looks back 24 hours. But there's a date picker that says No date range override which makes me think it will show > 24 hours.

(So, when trying to define an action, only seeing a handful of event when I'm expecting to see thousands makes me think my DOM selectors are wrong, which it turns out they weren't.)

image

Easy fix would be to explicitly say it's only looking at a short window, or even better: select the Last 24 hour option in the time picker.

Also when clicking the Open as new insight button, it opens the same query in the data table view.

At this point it should definitely show the date range, as it just looks like a bug that it's only loading a sliver of data with no date range set.

image

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 by reproducing action definition in the data table and then use the “Open as new insight” button to compare the displayed date range. Done means the active date range is explicit, the default short window is clearly indicated or selected, and the opened insight preserves or shows that range.

Written by the indexing model from the issue text.

Assessment

Domain
analytics, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.