Allow flag conditions based on the datetime of when the decision request comes in
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Feature request
Is your feature request related to a problem?
Sometimes I want feature flags to return different based on the time of day that a request for a flag decision comes in. E.g., "after hours" type condition. I can't do that today
Describe the solution you'd like
Add event timestamp to Metadata section of feature flag conditions.
Describe alternatives you've considered
We end up having to hard code date handling.
Additional context
Debug info
- [x] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating feature-flag condition evaluation and the Metadata representation, then trace how a decision request timestamp could reach them. Done means conditions can access the request event timestamp and support time-based decisions without hard-coded date handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100