status
stringclasses 1
value | repo_name
stringclasses 13
values | repo_url
stringclasses 13
values | issue_id
int64 1
104k
| updated_files
stringlengths 11
1.76k
| title
stringlengths 4
369
| body
stringlengths 0
254k
⌀ | issue_url
stringlengths 38
55
| pull_url
stringlengths 38
53
| before_fix_sha
stringlengths 40
40
| after_fix_sha
stringlengths 40
40
| report_datetime
unknown | language
stringclasses 5
values | commit_datetime
unknown |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,149 | ["ee/api/test/test_hooks.py", "ee/models/hook.py", "ee/settings.py", "ee/tasks/hooks.py", "latest_migrations.manifest", "posthog/settings/web.py", "posthog/test/__snapshots__/test_plugin.ambr", "requirements.in", "requirements.txt"] | Remove django-rest-hooks dependency | ## Is your feature request related to a problem?
See [this](https://github.com/PostHog/posthog/pull/9139/files/2754c0fd6633c806def5c328d491421ae7de0c19#diff-7f0217a57a02b6ebd709f6aa7bf43760b2d5a53069aee2b7fea27fdad1caadf1) for more info.
## Describe the solution you'd like
> This is used by django-rest-hooks, the library we use to integrate with Zapier. Specifically, this fires our Zapier integration's Triggers. However, the only trigger that actually matters is the "action_performed" one, and that has been completely delegated to the plugin server for a while. We can remove this Python cruft then, along with django-rest-hooks, but first we need to make sure action_defined and annotation_created actually are unused, and roll out an update to https://github.com/PostHog/posthog-zapier that'd remove those two completely.
## Describe alternatives you've considered
Do nothing | https://github.com/PostHog/posthog/issues/9149 | https://github.com/PostHog/posthog/pull/13349 | 3a342070876d07b83b3d7755b3db84b7be14765b | 598baaf441f157f420804cfddb9251921aab5527 | "2022-03-21T16:32:40Z" | python | "2022-12-19T09:06:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,135 | ["frontend/src/scenes/insights/InsightsTable/InsightsTable.tsx"] | Export button on Trends messes with dashboard view | ## Bug description
A Trend on a dashboard looks like:
<img width="634" alt="image" src="https://user-images.githubusercontent.com/7115141/159272616-08b32989-d1f0-48a5-b065-8b2d58a9ad0d.png">
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
## Expected behavior
Export minds its place
## How to reproduce
1. Go to a dashboard with trend table
2.
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/9135 | https://github.com/PostHog/posthog/pull/9153 | 38f8697a2dbbe7f9952c3713a02a9a54597ab3f2 | 302fb8ec6e30b847fe1f74c23f8b862f9c7424eb | "2022-03-21T13:38:01Z" | python | "2022-03-21T18:42:06Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,127 | ["frontend/src/scenes/dashboard/dashboardCollaboratorsLogic.ts"] | Only show multiplayer icons for those with access | When a project member is removed, it makes sense to continue to show if they created a dashboard, but when looking at multiplayer icons, it might make sense to remove them - otherwise it gives the sense they still have access.
<img width="814" alt="image" src="https://user-images.githubusercontent.com/154479/159176354-ef7b9187-598f-468f-b82b-46211550f9ea.png">
| https://github.com/PostHog/posthog/issues/9127 | https://github.com/PostHog/posthog/pull/9405 | c7d373364e808418efd2423fef24e7999e4def35 | b3e07d992071f32244c7880a76327bc34f8f9ffe | "2022-03-20T18:11:09Z" | python | "2022-04-13T11:40:40Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,114 | ["frontend/src/scenes/insights/Insight.tsx", "frontend/src/scenes/insights/InsightTabs/FunnelTab/FunnelTab.tsx"] | [Funnels] Reduce query builder width on new funnel? | When building a new funnel, I want to be able to clearly see the results.
## Current
The query builder takes up 50% of the available width, limiting how much data I can see without scrolling horizontally. It's also hard to get value from the funnel preview since the bars are so wide, making it hard to get a glimpse of the full picture.
<img width="1376" alt="image" src="https://user-images.githubusercontent.com/154479/159034599-102f9c98-057e-403f-a900-fffa520cd7a0.png">
## Proposed
By reducing the width of the query builder (or at least setting a smaller max-width), we can see more data without having to scroll. (None of the form elements in the query builder seem like they need any more space than this.)
<img width="1374" alt="image" src="https://user-images.githubusercontent.com/154479/159035339-823b555f-4983-4341-8175-df658be47e20.png">
| https://github.com/PostHog/posthog/issues/9114 | https://github.com/PostHog/posthog/pull/9118 | 5f51268cda26e646644f3bf7843431d3ce54e62d | c042dc9daa82d17bbcc236e9fefc7bd3d25be20f | "2022-03-18T15:48:37Z" | python | "2022-03-18T18:29:43Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,099 | ["frontend/src/scenes/retention/RetentionContainer.tsx", "frontend/src/scenes/retention/RetentionLineGraph.tsx"] | Retention dashboard panel shows line graph in background | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
<img width="1273" alt="Screenshot 2022-03-18 at 07 59 29" src="https://user-images.githubusercontent.com/38760734/158960263-6545f01f-fd1c-40ee-aa83-85a0cc08caf8.png">
## Expected behavior
Just show one or the other - table or line graph
## How to reproduce
1. Add a retention panel to a dashboard
2.
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/9099 | https://github.com/PostHog/posthog/pull/9198 | 731d763cc575b51561895430d2d6164bf100c9a9 | b5fde5dab0e905a3df2f93575af2db30ac7707f2 | "2022-03-18T08:00:34Z" | python | "2022-03-23T10:21:58Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 9,093 | ["frontend/src/lib/components/LemonButton/LemonButton.scss", "frontend/src/lib/components/LemonSwitch/LemonSwitch.scss", "frontend/src/lib/components/LemonSwitch/LemonSwitch.tsx", "frontend/src/lib/components/PropertyGroupFilters/PropertyGroupFilters.tsx", "frontend/src/lib/components/icons.tsx", "frontend/src/scenes/dashboard/ShareModal.tsx", "frontend/src/scenes/events/EventsTable.tsx", "frontend/src/scenes/insights/TestAccountFilter/TestAccountFilter.tsx"] | "Filter out internal and test users" splits filter logic on insights | ## Is your feature request related to a problem?
I find the layout of having the 'filter out internal and test users' selector splitting the 'add filter group' logic to be jarring.
This filter logic is applied once in a binary fashion and you don't really need to think about how it stacks with other logic you apply. If I'm building some logic for different conditions, I want those conditions, along with the option to add any new conditions, to be contiguous so I can make sense of them easily, rather than having to mentally escape the internal user logic in the middle of that.
<img width="1210" alt="image" src="https://user-images.githubusercontent.com/56287180/158872386-6f6ac321-b05a-46e9-aa3b-a21c99b08b68.png">
## Describe the solution you'd like
Pin the 'filter out internal and test users' to the bottom or top of the filter area,
## Describe alternatives you've considered
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/9093 | https://github.com/PostHog/posthog/pull/9107 | a3bf9e07499a1f7b39635f2dd15cf93d50d40118 | 5f51268cda26e646644f3bf7843431d3ce54e62d | "2022-03-17T18:31:39Z" | python | "2022-03-18T16:27:55Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,834 | ["ee/clickhouse/queries/trends/clickhouse_trends.py"] | Calculate multi-line trends in parallel | ## Is your feature request related to a problem?
If you have a trend with multiple lines, clickhouse queries for each are run one-after-another. If each takes 10s to calculate, then user will need to wait >30s in total.
## Describe the solution you'd like
Run queries in parallel.
## Describe alternatives you've considered
## Additional context
cc @EDsCODE @neilkakkar This seems like a quick win query-api wise though not 100% sure on how best implement this. Would you be up for prioritizing this _next_ sprint?
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/8834 | https://github.com/PostHog/posthog/pull/8874 | 9e88ef390189ab50c509c9368b11917a5ad37d1c | df3ec955ab4b819d61420a843e3cd475be490474 | "2022-03-03T11:36:29Z" | python | "2022-03-08T21:26:49Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,833 | ["frontend/src/lib/components/TimezoneAware/index.tsx"] | Time descriptions can be wrong when returning to the events table | ## Bug description
If you open the events table the items have a human description e.g. "2 minutes ago"
If you leave the page open and then load new events in at the top of the table (at least with auto load turned on) we don't update the humanised descriptions so the first row can be "2 minutes ago" and the second "a few seconds ago" even though their timestamps are correct
## Expected behavior
the description of the timestamps makes sense
## How to reproduce
1. open the events page
2. turn on auto load
3. leave it in the background for long enough to receive new events
4. view the humanized descriptions
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8833 | https://github.com/PostHog/posthog/pull/9330 | 4519ffb295e8b65b64c401e1f3d504131581e176 | 1cb7daedac6bc182988a5279e49efcff10de6ce2 | "2022-03-03T11:34:48Z" | python | "2022-04-03T18:28:20Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,745 | ["frontend/src/scenes/insights/LineGraph/LineGraph.tsx"] | Annotations aren't shown on time-based bar charts | ## Bug description
If I create a time-based trend chart, then annotations are shown at the bottom on the x-axis as per this screenshot:
<img width="1149" alt="Screenshot 2022-02-24 at 10 11 37" src="https://user-images.githubusercontent.com/11316707/155504416-737e12d0-cecd-4529-8b78-fb21c85063ee.png">
If I switch the same chart to be a time-based bar chart the annotations disappear:
<img width="1133" alt="Screenshot 2022-02-24 at 10 12 18" src="https://user-images.githubusercontent.com/11316707/155504498-7a3c5be2-06d9-4c10-9a76-aadfdbe7baf8.png">
## Expected behavior
Annotations should be visible on time-based charts regardless of whether they are line or bar, as they relate to events which happened in a specific time period.
## How to reproduce
1. Create a trend insight that uses a line chart to visualize the results
2. Switch it to the bar chart type
3. Note that annotations disappear from the x-axis
## Environment
- [x ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [x ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
Initial report came from a customer
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8745 | https://github.com/PostHog/posthog/pull/8747 | 019c1f203a1713788883085fb60f2909263a2181 | c1a2bad819d808dd62c88498b7322472e7eec119 | "2022-02-24T10:15:48Z" | python | "2022-02-28T16:58:30Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,723 | ["frontend/src/scenes/ingestion/panels/AutocapturePanel.tsx"] | Step 2 of onboarding web flow on new instance is malformed | <img width="1214" alt="image" src="https://user-images.githubusercontent.com/391319/155289030-eadcf1d2-20a6-4b6d-955b-90d25761cd71.png">
Should look a bit nicer | https://github.com/PostHog/posthog/issues/8723 | https://github.com/PostHog/posthog/pull/8728 | cca06cc723680ea64831b379ffb267c15dcd1f45 | 2215733e7d35a114fc276a5496f6715acfe3e369 | "2022-02-23T09:07:00Z" | python | "2022-02-23T09:52:07Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,716 | ["ee/api/test/test_dashboard.py", "frontend/src/scenes/dashboard/ShareModal.tsx", "frontend/src/scenes/dashboard/dashboardLogic.ts", "frontend/src/types.ts", "posthog/api/dashboard.py", "posthog/api/insight.py"] | Dashboard owner has lost 'Edit permissions' for said dashabord | ## Bug description
I have lost edit permissions to a [dashboard I created](https://app.posthog.com/dashboard/28987), despite still being listed as the owner of the dashboard
## Expected behavior
I should still be able to edit the dashboard
## How to reproduce
I noticed this problem after adding a new insight, but this doesn't appear to be the cause of the issue. I've duplicated the dashboard to restore access and adding a new insight didn't appear to cause the issue
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8716 | https://github.com/PostHog/posthog/pull/8734 | cff1152e2561942cdf0df69b142d219294ef6360 | b679bc3d68a640e3329fcb4c2d65556268d56f1a | "2022-02-22T15:56:35Z" | python | "2022-02-23T10:33:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,514 | ["frontend/src/scenes/events/eventsTableLogic.test.ts", "frontend/src/scenes/events/eventsTableLogic.ts"] | Events & actions huge load | ## Bug description
If I try to visit Events & actions tab in posthog I can immediately see how my disk is trying to process it. After about 10 seconds I can see my events and it works as expected. And If I'm clicking on 'There are new events. Click here to load them' posthog loads them instantly.
But somehow things changed and now after visiting Events tab posthog breaks. In my Clickhouse I can see that it still working on some query by disk loading (`iostat -4` for example). In Clickhouses query logs I can see strange query:
```
SELECT
uuid,
event,
properties,
timestamp,
team_id,
distinct_id,
elements_chain,
created_at
FROM
posthog.events
where team_id = 1
AND timestamp > '2021-02-04 17:00:44.158000'AND timestamp < '2022-02-04 17:00:48.206451'
ORDER BY toDate(timestamp) DESC, timestamp DESC LIMIT 101
```
1. No space between conditions
2. Time range is a year. We have about 110 GB of data and it seems posthog can't wait much longer and stops working.
I've tried to upgrade to 1.32 version, but loading Events tab process still breaks with 502 error. Now I've downgraded posthog to 1.31 and in button 'Customize columns' I've pressed 'Reset to default' and it works well. If I will change the version to 1.32 - this error will remain.
## Expected behavior
Fields for selecting the time range in Events & actions tab. Set default value to 1 hour or something like that.
## How to reproduce
Not sure how to do it. In my case it happened randomly, but now repeats after upgrade to 1.32
## Environment
Self-hosted PostHog (ClickHouse-based), version/commit: [release-1.31.1](https://hub.docker.com/layers/posthog/posthog/release-1.31.1/images/sha256-d825dd3eec25935089800d329eb6d82a77bcf565de8d24e8e4db1a1b036b6ab3?context=explore)
| https://github.com/PostHog/posthog/issues/8514 | https://github.com/PostHog/posthog/pull/8537 | 7b461edcb91eae3ae331ee3827d95a8945daef57 | c30bb7886c4c17b55f262217ac77ee4987fe4003 | "2022-02-09T09:26:07Z" | python | "2022-02-11T10:43:47Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,478 | ["frontend/src/scenes/insights/sharedUtils.test.ts", "frontend/src/scenes/insights/sharedUtils.ts"] | Bug: Wrong insight type loading when editing from dashboard | ## Bug description
Spotted this for the first time on a call with @andyvan-ph, but he says it's happened a few times to him before so it's definitely replicable.
If you start from a dashboard with multiple types of insight and click 'Edit' on one type (e.g. Trends), then click Back to return to the dashboard and click 'Edit' on another type (e.g. Paths) then PostHog attempts to load a Trends insight again. I _think_ it's trying and failing to load it with the same information, because the insight will never successfully load if left -- but if you click to the correct type of insight, suddenly it loads instantly.
This is a little hard to explain, [so here's a video.](https://drive.google.com/file/d/18xpW3VMQoNtXb_66eK61fUA3L7HcLtvl/view?usp=sharing)
## Expected behavior
I'd expect it to load the correct insight.
## How to reproduce
1. Open a dashboard. Here's what I used.
2. Click 'Edit' on the Pageviews trends insight. Then click back to return to the dashboard.
3. Click 'Edit' on the Paths insight.
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
Taggin @andyvan-ph who can provide more examples and context, if needed.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8478 | https://github.com/PostHog/posthog/pull/8613 | 954bdd175f2dbe7be7c781553fbe745f88768a3f | 1aa27ddf20c00afe50901b18d9944329765ca046 | "2022-02-08T11:29:32Z" | python | "2022-02-15T21:45:35Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,468 | ["frontend/src/scenes/persons/personsLogic.test.ts", "frontend/src/scenes/persons/personsLogic.tsx"] | Person page will randomly pop up cohort loading issues | ## Bug description
^ that 500 will show a user facing error message. It shouldn't be loaded on the persons page anyway.
## Expected behavior
No error message
## How to reproduce
1.
2.
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8468 | https://github.com/PostHog/posthog/pull/8543 | 7503d2429eba661225f5bbade0591a4b1bec5e47 | 58c699fe7192c8c84400f425e3021e340a70a4c6 | "2022-02-07T18:02:56Z" | python | "2022-02-11T08:38:39Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,313 | ["frontend/src/scenes/experiments/Experiment.scss", "frontend/src/scenes/experiments/Experiment.tsx", "frontend/src/scenes/experiments/experimentLogic.tsx"] | Experimentation colors are confusing | ## Bug description
The colours in the "confidence bar" are inverted compared to the graph below:
## Expected behavior
I would expect all colors to be identical if representing the same thing.
## How to reproduce
1. https://app.posthog.com/experiments/21#
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8313 | https://github.com/PostHog/posthog/pull/8357 | 8af363e155eaf8c4427813872902b572df863a51 | 6ec22ce4523ac4849300dfc85fec2a419931c902 | "2022-01-27T13:56:26Z" | python | "2022-01-31T17:06:24Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,295 | ["ee/clickhouse/views/experiments.py", "ee/clickhouse/views/test/test_clickhouse_experiments.py", "frontend/src/scenes/experiments/Experiment.scss", "frontend/src/scenes/experiments/Experiment.tsx", "frontend/src/scenes/experiments/experimentLogic.tsx"] | Groups Support for Experimentation | ## Is your feature request related to a problem?
I want to run experiments on groups
## Describe the solution you'd like
Experiments support group target metrics, and the FF respects group selection.
## Describe alternatives you've considered
No groups :(
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/8295 | https://github.com/PostHog/posthog/pull/8463 | 31807bbc874666adac730b0083aa83c2fa0585f3 | d5a48fbd061d75dd16d3969b59b2e29d32a9679d | "2022-01-26T13:41:36Z" | python | "2022-02-09T15:32:54Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,243 | ["frontend/src/scenes/experiments/Experiment.tsx", "frontend/src/scenes/experiments/SecondaryMetrics.tsx", "frontend/src/scenes/insights/ActionFilter/ActionFilter.tsx", "frontend/src/scenes/insights/ActionFilter/ActionFilterRow/ActionFilterRow.tsx", "frontend/src/scenes/insights/InsightTabs/FunnelTab/FunnelExclusionsFilter.tsx", "frontend/src/scenes/insights/InsightTabs/FunnelTab/FunnelTab.tsx", "frontend/src/scenes/insights/InsightTabs/RetentionTab.tsx", "frontend/src/scenes/insights/InsightTabs/TrendTab/TrendTab.tsx", "frontend/src/scenes/session-recordings/SessionRecordingsTable.tsx", "frontend/src/scenes/trends/mathsLogic.tsx"] | Stickiness math is useless | ## Bug description
*Please describe.*
DAU for stickiness doesn't mean anything
## Expected behavior
Unnecessary math options shouldn't be visible. What are the other types of math supposed to return for stickiness?
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [x] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8243 | https://github.com/PostHog/posthog/pull/9197 | 126f9ce6fbda814b9dd662451293d3f0b0bd60c5 | e613f65fc2ea6a47af578af4ebce31aa45347032 | "2022-01-24T19:50:57Z" | python | "2022-03-23T14:46:16Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,236 | ["frontend/src/lib/experimental/FeedbackCallCTA.tsx", "frontend/src/scenes/insights/LineGraph/LEGACY_LineGraph.jsx", "frontend/src/scenes/insights/LineGraph/LineGraph.tsx", "frontend/src/scenes/trends/viz/ActionsPie.tsx"] | Legend toggling not working for pie charts | ## Bug description
Toggling keys in legend and table doesn't work for pie chart.
## Expected behavior
Toggling legend/table key checkboxes should show/hide corresponding sections of pie.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
| https://github.com/PostHog/posthog/issues/8236 | https://github.com/PostHog/posthog/pull/8279 | 7f4a8a11e0210337d1895b1dd44445820a03ee5b | ad6ef7d4f8533d373f10913651564f5f4b250b49 | "2022-01-24T16:16:07Z" | python | "2022-01-26T00:41:33Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,234 | ["frontend/src/scenes/organization/Settings/membersLogic.tsx", "frontend/src/scenes/saved-insights/SavedInsights.tsx", "posthog/api/organization_member.py"] | "created by" filter should show me first + order alphabetically | ## Is your feature request related to a problem?
It is very likely that I would want to filter a list of insights on whether I created it, and I don't want to scroll through a list to find it.
## Describe the solution you'd like
Put current user first (in bold) + order list alphabetically
## Describe alternatives you've considered
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/8234 | https://github.com/PostHog/posthog/pull/9019 | fec52bbfcf291df76aee53b12b43d621b1aa3c0f | 06bee0c86324e0a4b8c2e89978e660243dd0c437 | "2022-01-24T16:02:14Z" | python | "2022-03-14T20:06:25Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,187 | ["frontend/src/scenes/events/eventsTableLogic.test.ts", "frontend/src/scenes/events/eventsTableLogic.ts"] | Events table is slow to load | ## Bug description
The events table is slow to load.
## Expected behavior
Events table is not slow
## How to reproduce
1. Go to Events page
2. Wait
3.
## Environment
- [ X ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8187 | https://github.com/PostHog/posthog/pull/8537 | 7b461edcb91eae3ae331ee3827d95a8945daef57 | c30bb7886c4c17b55f262217ac77ee4987fe4003 | "2022-01-21T12:18:11Z" | python | "2022-02-11T10:43:47Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,078 | ["frontend/src/lib/components/EditableField/EditableField.scss", "frontend/src/scenes/insights/Insight.tsx"] | Insight description too long entry breaks formating and saving | ## Bug description
<img width="1328" alt="Screen Shot 2022-01-14 at 19 25 56" src="https://user-images.githubusercontent.com/890921/149566921-d3062a46-da88-4839-9179-119367858e51.png">
Save button doesn't work because (but this is not the most user friendly way to figure it out):
<img width="870" alt="Screen Shot 2022-01-14 at 19 29 42" src="https://user-images.githubusercontent.com/890921/149567070-089839b6-70c4-4d91-ace2-8cfa7a5760d1.png">
## Expected behavior
we see an error trying to edit the description to be too long can't scroll right
## How to reproduce
1. try to enter a really long word in the insight description
2. scroll right observe we can scroll past what we should
3. observe that save button doesn't work
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8078 | https://github.com/PostHog/posthog/pull/8290 | d81acd9fa31f92601d54121cb7fece997374a8ef | 97ca690e69ac0d66d46f63d4d4f730833e07ecec | "2022-01-14T18:34:23Z" | python | "2022-01-26T11:34:10Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,059 | ["cypress/support/e2e.js", "frontend/src/lib/components/DateFilter/DateFilter.tsx", "frontend/src/lib/components/DateFilter/DateFilterRange.scss", "frontend/src/lib/components/DateFilter/DateFilterRange.tsx", "frontend/src/lib/components/DateFilter/DateFilterRangeExperiment.tsx", "frontend/src/lib/components/DateFilter/dateFilterLogic.test.ts", "frontend/src/lib/components/IntervalFilter/intervalFilterLogic.ts", "frontend/src/lib/constants.tsx", "frontend/src/lib/utils.test.ts", "frontend/src/lib/utils.tsx"] | Insights date filtering/interval logic is confusing | ## Is your feature request related to a problem?
In insights you can select a time range and a group by interval. Combining these can lead to unexpected results.
For example, on Jan 14th selecting "week" interval and 30 days shows dates of 9th of January, 2nd January, 26th December, 19th December and 12th December.
This has couple of issues:
- Weeks start on Sunday not Monday, which is meh
- 12th december is over 30 days ago
- Changing the timerange to 90 days, the result for 12th december increases.
Same applies for e.g. choosing month interval
One combination which is also confusing is last 14 days with month interval.
Another thing is that choosing "last 7 days" shows 8 datapoints on the graph.
## Describe the solution you'd like
???
## Additional context
This feedback is given from the perspective of trends, but general problems apply everywhere.
Related issue: https://github.com/PostHog/posthog/issues/8031
cc @paolodamico @EDsCODE
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/8059 | https://github.com/PostHog/posthog/pull/10688 | a1c0aafa2961fa6966c3cfdaf4d265184e876c8a | 1dfaf539e583b973480110d8f4ae52850f8c2eec | "2022-01-14T11:36:32Z" | python | "2022-07-08T10:26:02Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,058 | ["frontend/src/scenes/experiments/Experiment.scss", "frontend/src/scenes/insights/Insight.scss"] | Funnel trends graph is not centered | ## Bug description
## Expected behavior
Thing is centered
## How to reproduce
1. Create a funnel trends graph
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
Probably issues with the new linegraph?
cc @alexkim205 @mariusandra @paolodamico for prioritization
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8058 | https://github.com/PostHog/posthog/pull/9067 | c9f44658ea7f047830f6a7da699e53e2fb7a7d27 | 9a053caaef8812dd7335ea181f50e33c99588d26 | "2022-01-14T11:33:27Z" | python | "2022-03-16T19:43:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,026 | ["frontend/src/scenes/funnels/FunnelLineGraph.tsx", "frontend/src/scenes/insights/LineGraph/LineGraph.tsx", "frontend/src/scenes/retention/RetentionLineGraph.tsx", "frontend/src/scenes/trends/trendsLogic.ts", "frontend/src/scenes/trends/viz/ActionsHorizontalBar.tsx", "frontend/src/scenes/trends/viz/ActionsLineGraph.tsx", "frontend/src/scenes/trends/viz/ActionsPie.tsx"] | New tooltips do not respect group types | ## Bug description
When analyzing something by groups, the new tooltips look like following:
## Expected behavior
Tooltip should say `Click to view organization(s)`
## How to reproduce
1. Go to insights
2. Aggregate by a group type
3. Hover
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
cc @alexkim205, @mariusandra @paolodamico Please keep groups in mind when designing for or implementing new features.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8026 | https://github.com/PostHog/posthog/pull/8095 | f1964d4ad960e5b24629987e987b94470d9b810c | 27bd02ba60f86a9e38c61982d4854c58eb680d41 | "2022-01-13T13:52:04Z" | python | "2022-01-19T22:08:46Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 8,014 | ["frontend/src/lib/components/EntityFilterInfo.tsx", "frontend/src/lib/components/InsightLabel/index.tsx", "frontend/src/scenes/insights/InsightTooltip/InsightTooltip.scss", "frontend/src/scenes/insights/InsightTooltip/InsightTooltip.tsx", "frontend/src/scenes/insights/LineGraph/lineGraphLogic.ts"] | Insights tooltip rendering problems | ## Bug description
If there's lots of lines the hover pane becomes not readable:
<img width="273" alt="Screen Shot 2022-01-12 at 23 58 27" src="https://user-images.githubusercontent.com/890921/149236765-b7447c3c-376c-417b-83e7-4f250ce39d09.png">
The ordering is hard to interpret:
<img width="424" alt="Screen Shot 2022-01-12 at 23 57 54" src="https://user-images.githubusercontent.com/890921/149237165-5bd9aa8d-173d-4bc7-9020-ed21c11b23f0.png">
^ I need to closely look at the table to know yellow is 1.29.1
## Expected behavior
For ordering we sort them based on the value or color the values if we want to keep them alphabetical as they are now so it's easily visually detectable which is which.
## How to reproduce
1. https://app.posthog.com/insights/DFGqpUoM?events=%5B%7B%22id%22%3A%22instance%20status%20report%22%2C%22math%22%3A%22dau%22%2C%22name%22%3A%22instance%20status%20report%22%2C%22type%22%3A%22events%22%2C%22order%22%3A0%2C%22properties%22%3A%5B%7B%22key%22%3A%22realm%22%2C%22type%22%3A%22event%22%2C%22value%22%3A%5B%22cloud%22%5D%2C%22operator%22%3A%22is_not%22%7D%5D%2C%22custom_name%22%3A%22self-hosted%22%7D%5D&actions=%5B%5D&display=ActionsLineGraph&insight=TRENDS&interval=week&breakdown=posthog_version&date_from=-30d&new_entity=%5B%5D&properties=%5B%7B%22key%22%3A%22realm%22%2C%22type%22%3A%22event%22%2C%22value%22%3A%5B%22cloud%22%5D%2C%22operator%22%3A%22is_not%22%7D%5D&breakdown_type=event&filter_test_accounts=true (too many items to show)
2. https://app.posthog.com/insights/QEsYvzvb?events=%5B%7B%22id%22%3A%22organization%20usage%20report%22%2C%22math%22%3A%22dau%22%2C%22name%22%3A%22organization%20usage%20report%22%2C%22type%22%3A%22events%22%2C%22order%22%3A0%2C%22properties%22%3A%5B%5D%2C%22custom_name%22%3A%22self-hosted%20unique%20users%22%7D%5D&actions=%5B%5D&display=ActionsLineGraph&insight=TRENDS&interval=day&breakdown=posthog_version&date_from=-90d&new_entity=%5B%5D&properties=%5B%7B%22key%22%3A%22realm%22%2C%22type%22%3A%22event%22%2C%22value%22%3A%5B%22cloud%22%5D%2C%22operator%22%3A%22is_not%22%7D%5D&breakdown_type=event&filter_test_accounts=true (ordering confusing to interpret)
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/8014 | https://github.com/PostHog/posthog/pull/8046 | b1f304754fa37a2f72fe4b3ad51f8ed6bdf707b7 | 22ea1cf6820748a58b1b521462cf11d17082d8b3 | "2022-01-12T23:08:26Z" | python | "2022-01-18T20:34:46Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,999 | ["ee/clickhouse/sql/events.py", "frontend/src/lib/components/PropertyFilters/components/PropertyValue.tsx", "posthog/api/event.py", "posthog/api/test/test_event.py"] | Make filter value completion not case sensitive | ## Is your feature request related to a problem?
When trying to create a filter for a query, value autocompletes are case sensitive. This throws up weird behaviors.
E.g, with the country name filter entering 'f' as the first letter autocompletes to 'Africa' (and, for some reason, the Isle of Man) and 'France is not listed as an option. Entering 'F' autocompletes to France.
## Describe the solution you'd like
Not case sensitive results, or else better filtering. Africa shouldn't come up if I only enter 'f'.
## Describe alternatives you've considered
## Additional context
<img width="886" alt="Screenshot 2022-01-12 at 13 40 00" src="https://user-images.githubusercontent.com/84011561/149151022-6648bc51-c0ff-4116-8611-cb64e88e9483.png">
<img width="887" alt="Screenshot 2022-01-12 at 13 40 11" src="https://user-images.githubusercontent.com/84011561/149151048-86098606-551b-4757-b133-f80b739c4974.png">
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/7999 | https://github.com/PostHog/posthog/pull/8020 | 9c19e7ec43874786cd8d34880414bf4d2f425453 | 066c172c81d3151b6879b8573b65fc039851d576 | "2022-01-12T13:40:40Z" | python | "2022-01-13T14:16:28Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,994 | ["frontend/src/scenes/insights/InsightTabs/TrendTab/TrendTab.tsx", "frontend/src/scenes/insights/InsightTooltip/InsightTooltip.tsx", "frontend/src/scenes/insights/InsightTooltip/insightTooltipUtils.tsx", "frontend/src/scenes/insights/LineGraph/LineGraph.tsx", "frontend/src/scenes/trends/viz/ActionsLineGraph.tsx"] | Lifecycle tooltips are missing key information | ## Bug description
A lifecycle graph looks currently like follows:
The tooltip is useless given it doesn't say which cohort the user belongs to. Also it should likely include the relevant date for the tooltip.
## Expected behavior
Tooltip says NEW/Returning/etc, includes date
## How to reproduce
Open a lifecycle graph
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7994 | https://github.com/PostHog/posthog/pull/8044 | 1974cbb3d2ee51dc9f86213b220008715777c954 | c30af1d483ba984c82846ea3e371e45e7f083be3 | "2022-01-12T08:26:22Z" | python | "2022-01-13T22:41:33Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,952 | ["frontend/src/lib/components/LemonTable/LemonTable.tsx", "frontend/src/scenes/dashboard/DashboardItem.tsx", "frontend/src/scenes/insights/InsightContainer.tsx", "frontend/src/scenes/insights/InsightsTable/InsightsTable.tsx", "frontend/src/scenes/project/Settings/index.tsx", "frontend/src/scenes/trends/Trends.tsx", "frontend/src/scenes/trends/viz/ActionsTable.tsx", "frontend/src/scenes/trends/viz/index.ts"] | Insight table in dashboards uses old insight | ## Bug description
When adding an insight with viz type "table" we use the old display mode instead of the new InsightsTable. This results in a broken experience (e.g. custom names are not respected)
## Expected behavior
The Table insights should look the same in insights and dashboards.
## How to reproduce
1. Add any table insight to a dashboard.
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [x] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
Originally reported by [user](https://posthog.slack.com/archives/C02G72Y6E9H/p1641547231016200)
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7952 | https://github.com/PostHog/posthog/pull/7954 | 8d22ae9b752cc20011b3f3524620778b66f381a6 | 63b95b3c8c39b0fe0994d84cc68e6c1e9d326b46 | "2022-01-07T17:59:08Z" | python | "2022-01-10T16:26:57Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,895 | ["posthog/async_migrations/utils.py"] | Async migrations: celery_task_id is not properly handled | ## Bug description
async migrations celery task id will always be "" through the migration
## Expected behavior
It will be set
## How to reproduce
1. Start a migration
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
The cause is a bad state machine: We set it in #trigger_migration but #mark_async_migration_as_running later in the chain always resets it.
cc @tiina303 and @yakkomajuri for prioritization
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7895 | https://github.com/PostHog/posthog/pull/7930 | 10d8c59146573e4f81d91158b70ad65f31877a53 | 4b2d3395b606e4a0b9bcf95accff1a291f58aa83 | "2022-01-05T09:57:14Z" | python | "2022-01-10T18:34:48Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,873 | ["frontend/src/lib/forms/Field.tsx", "frontend/src/scenes/authentication/Signup.tsx", "posthog/api/signup.py", "posthog/event_usage.py"] | Add a 'where did you first hear about us' text area to sign up flow | ## Is your feature request related to a problem?
We don't have a great grasp of where our users _actually_ first hear about us.
As much as we can try to attribute through UTM tags, the reality is people will have read an article about us on HackerNews and then later googled us.
If we can understand this better, we can focus our spend on dev rel and marketing properly.
## Describe the solution you'd like
A mandatory text area in the sign up flow when the organization is created (for cloud) that asks where users first _heard_ of us. It should be a free form text field so we get more open answers.
## Describe alternatives you've considered
Spend marketing money in the wrong places, potentially.
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/7873 | https://github.com/PostHog/posthog/pull/11581 | cc3acf8e504a6365cdd2a1897bff26a26c6824c7 | cc0f819fbaebd8330309a692abbb68ca3c7fabf1 | "2022-01-04T08:48:02Z" | python | "2022-09-01T13:54:34Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,857 | ["frontend/src/lib/components/CommandPalette/index.tsx", "frontend/src/scenes/insights/Insight.tsx"] | Pressing ESC analyzing an insight exits editing it | ## Bug description
Currently, when I press X analyzing a _new_ insight it exits the edit mode and only shows me the graph. This is annoying already.
If I have the quick action menu open at the same time it becomes even more so - if I try to exit the menu via ESC it exits both the menu as well as editing the insight.
## Expected behavior
Drop the ESC behavior on insights - I don't see it being useful.
## How to reproduce
1. Click + to add insight
2. Ctrl + K to open menu (optional)
3. Press ESC
4. See editing is stopped
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
cc @Twixes and @mariusandra for prioritization
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7857 | https://github.com/PostHog/posthog/pull/7864 | e674cd2a6d8f3822f7a6960ef97113b19f1c00f5 | cfec3f2d20dc546872ef5eabcbc0548d1a25d5af | "2021-12-31T09:52:04Z" | python | "2022-01-05T10:16:26Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,799 | ["frontend/src/scenes/insights/InsightTabs/FunnelTab/funnelStepTableUtils.tsx"] | Rename graph series feature failing for funnel steps 2 and above in posthog cloud (12 Dec 2021) | ## Bug description
`rename graph series` feature failing for funnel steps 2 and above in posthog cloud (12 Dec 2012).
**Context:**
When editing a funnel insight, renaming the 1st funnel works as expected, but when renaming subsequent funnel steps, changes aren't applied.
## Expected behavior
Renaming a funnel step should result in the funnel step being renamed
## How to reproduce
1. open https://app.posthog.com/insights
2. click on any **funnel** (that has more than one step)
3. click "edit" > "rename graph series" (icon)
4. rename any funnel step (excluding the first step)
## Environment
PostHog Cloud
##Screenshot
Many Thanks! :)
O and merry Christmas / happy holidays from Aus! | https://github.com/PostHog/posthog/issues/7799 | https://github.com/PostHog/posthog/pull/8005 | 05c5471f7c863f62a46244ecf4577d660b303a00 | f239d9bedefe4cb5fd7073ac447327b955a30959 | "2021-12-19T23:54:24Z" | python | "2022-01-14T11:04:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,796 | ["frontend/src/lib/components/TaxonomicFilter/TaxonomicFilter.scss", "frontend/src/lib/components/TaxonomicFilter/TaxonomicFilter.tsx"] | The ever-elusive tooltip | I saw an icon in this search bar and wanted to see what it meant, but I had trouble hovering it to access its tooltip.
**Repro:**
1. In Trends, add a breakdown
2. Type something like `utm`
3. Click `Person properties` (at least if no `utm` results exist)
4. See a keyboard icon you really want to click since it's not a standard convention and you have no idea what it means
5. Click around for a while until you trick it into opening!
(I'd expect these to work on hover, no click required)
| https://github.com/PostHog/posthog/issues/7796 | https://github.com/PostHog/posthog/pull/8816 | 3ad5609e56c0f833145e660c5750986f1cf0f3a2 | dda69eb438c168c9b554b71afc74fa271e361b61 | "2021-12-19T06:04:31Z" | python | "2022-03-03T08:32:45Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,789 | ["frontend/src/scenes/trends/trendsLogic.ts", "frontend/src/scenes/trends/viz/ActionsLineGraph.tsx"] | Incompleteness trend UI doesn't apply on custom date range | ## Bug description
*Please describe.*
- If you apply a specified time range (using the calendar select) in a trend graph, the in progress UI doesn't apply
*If this affects the front-end, screenshots would be of great help.*
<img width="390" alt="Screen Shot 2021-12-17 at 6 50 37 PM" src="https://user-images.githubusercontent.com/13127476/146625117-420c67f5-974f-4b0a-b2af-d535ec5a247b.png">
## Expected behavior
- should still show progress UI
## How to reproduce
1. Go to a graph
2. specify a custom time that should still be in progress
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7789 | https://github.com/PostHog/posthog/pull/7870 | 8d7614bc7c0443c5b2f99007a0e70ae57c38dc25 | 6fb7662cfa269c0bf42be2781a705bfa283174b2 | "2021-12-18T01:54:02Z" | python | "2022-01-04T17:30:35Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,756 | ["frontend/src/scenes/persons/personsLogic.test.ts", "frontend/src/scenes/persons/personsLogic.ts"] | Persons page loads the wrong recordings for a second | ## Bug description
If you do the following:
* From the persons list, click on person A
* Go back to the list
* Click on a person B
* See the recordings list load the recordings for person A, and then, after a second, loads the expected recordings for person B
## Expected behavior
I'd expect to only see the recordings for person B on the person B page.
## Additional context
@mariusandra, I can put a quick fix in for this specific case, but I have a feeling that it's related to 🔥TURBO MODE🔥™, and it might be worth fixing at that level (so we don't see the behavior popping up elsewhere). From a bit of debugging, it looks like the logic gets mounted with the old PersonUUID prop, and then, after a second, it gets mounted with the new prop and that's causing the issue.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7756 | https://github.com/PostHog/posthog/pull/7967 | f5317b11bc16189db15b891e74bf7951cc091e54 | 33e2520f66f88881fc89914b8eee6be98f0c8847 | "2021-12-16T19:49:03Z" | python | "2022-01-10T19:25:42Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,751 | ["cypress/integration/trends.js", "frontend/src/lib/components/DateDisplay/DateDisplay.scss", "frontend/src/lib/components/LemonTable/LemonTable.tsx", "frontend/src/scenes/insights/Insight.scss", "frontend/src/scenes/insights/InsightContainer.tsx", "frontend/src/scenes/insights/InsightsTable/InsightsTable.scss", "frontend/src/scenes/insights/InsightsTable/InsightsTable.tsx", "frontend/src/styles/global.scss"] | Insight trends with a lot of dates and breakdown lines are SLOOOOW | ## Bug description
This slowness is on the latest M1 Pro Mac on [this page](https://app.posthog.com/insights/TviShYmw?insight=TRENDS&display=ActionsLineGraph&interval=day&actions=%5B%5D&events=%5B%7B%22id%22%3A%22%24pageview%22%2C%22name%22%3A%22%24pageview%22%2C%22type%22%3A%22events%22%2C%22order%22%3A0%7D%5D&properties=%5B%5D&filter_test_accounts=true&legend_hidden=true&date_from=yStart&breakdown=%24browser&breakdown_type=event) and others like it. Later in the gif I keep trying to scroll left-right on the table, but nothing happens. Also no sidebar highlight are shown.
## Expected behavior
It shouldn't lag this much
## How to reproduce
1. Open new insight -> trends
2. Select ~365 days, by day
3. Apply a breakdown that gives you 10+ rows
4. Die of old age
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
I think the table below makes everything really slow
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7751 | https://github.com/PostHog/posthog/pull/7817 | 9a6b837066f29490b5cc9636522bbf6e65d3eb1c | c156b0be5d9a24a998cb67266259032f7e68049a | "2021-12-16T14:23:51Z" | python | "2021-12-21T22:19:23Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,708 | ["frontend/src/scenes/insights/InsightTabs/FunnelTab/funnelStepTableUtils.tsx"] | Left-to-right funnels ignore custom labels | ## Bug description
Left-to-right funnels ignore custom labels (they do not appear in the column headings for each step):
Whereas top-to-bottom appears to be working fine:
## Expected behavior
Left-to-right funnels should display custom labels as the column headers, instead of the event/action name, if they are present.
## How to reproduce
1. Create a funnel insight.
2. Rename a step (i.e. give a step a custom label).
3. Make the funnel left-to-right
4. Observe the custom label is not used. **<- BUG**
5. Make the funnel top-to-bottom
6. Observe the custom label is used.
## Environment
- [X] PostHog Cloud
| https://github.com/PostHog/posthog/issues/7708 | https://github.com/PostHog/posthog/pull/8005 | 05c5471f7c863f62a46244ecf4577d660b303a00 | f239d9bedefe4cb5fd7073ac447327b955a30959 | "2021-12-14T15:03:21Z" | python | "2022-01-14T11:04:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,682 | [".github/workflows/e2e.yml", "bin/e2e-test-runner", "cypress/integration/insights.js", "cypress/integration/person.js", "cypress/integration/retention.js", "cypress/integration/systemStatus.js", "posthog/demo/revenue_data_generator.py", "posthog/tasks/test/test_calculate_event_property_usage.py"] | Run e2e tests with Clickhouse backend | ## Is your feature request related to a problem?
we currently run e2e tests with postgres backend, potentially causing us to miss bugs as we are deprecating Postgres (#6662)
## Describe the solution you'd like
Run e2e tests with clickhouse
## Describe alternatives you've considered
## Additional context
I'll pick this up tomorrow
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/7682 | https://github.com/PostHog/posthog/pull/7705 | 83b8a7dc6bae21980ecafe20a185851863407b5d | 2adc6258d22f99896a7b420334865718252009e0 | "2021-12-13T18:20:43Z" | python | "2022-01-03T14:26:54Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,681 | ["frontend/src/lib/components/InsightLabel/index.tsx"] | Breakdown datapoint labels on trend graph are blank | ## Bug description
*Please describe.*
- there's no label for the datapoint on breakdown graphs
*If this affects the front-end, screenshots would be of great help.*
<img width="374" alt="Screen Shot 2021-12-13 at 11 01 45 AM" src="https://user-images.githubusercontent.com/13127476/145864438-b96778d9-774b-4c06-9158-610b9e3cc59b.png">
## Expected behavior
There should be labels
## How to reproduce
1. https://app.posthog.com/insights/8Z7lyS52/edit?insight=TRENDS&display=ActionsLineGraph&interval=day&actions=%5B%5D&events=%5B%7B%22id%22%3A%22%24pageview%22%2C%22name%22%3A%22%24pageview%22%2C%22type%22%3A%22events%22%2C%22order%22%3A0%2C%22math%22%3A%22dau%22%7D%5D&properties=%5B%5D&filter_test_accounts=false&breakdown=%24browser&breakdown_type=event&new_entity=%5B%5D
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7681 | https://github.com/PostHog/posthog/pull/7694 | 4f66c09e58cd94cc921daa5d3bb7ef000bea423e | e86c569a96f4b72a173e095f50215fb32a0bdc26 | "2021-12-13T18:01:22Z" | python | "2021-12-14T05:26:52Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,667 | ["requirements.in", "requirements.txt"] | Too many failed login attempts error | ## Bug description
It seems like error itself is breaking.
In the process of creating https://github.com/PostHog/posthog/issues/7666 I tried signing up under a few different email addresses. Eventually I hit this error, which is what I assume we want the error to appear as:
<img width="498" alt="Screenshot 2021-12-13 at 11 10 03" src="https://user-images.githubusercontent.com/84011561/145802098-3a642833-622b-4ba4-9f55-da7372d9c7e0.png">
A few minutes later, I retried to see if 15 minutes had passed - because I'm an optimistic sod who things time is just an abstract concept. This time I got the following error:
<img width="735" alt="Screenshot 2021-12-13 at 11 11 18" src="https://user-images.githubusercontent.com/84011561/145802253-53987cf4-a752-4fc2-b611-cc417819a208.png">
Retrying the process on a different computer and on mobile (not on Wifi) gave the same error as above.
## Expected behavior
I'd expect the first error to persist, rather than the second to appear.
## How to reproduce
1. Signup.
2. Signup.
3. Signup.
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
Error text: `{"type": "authentication_error", "code": "too_many_failed_attempts", "detail": "Too many failed login attempts. Please try again in 15 minutes.", "attr": null}`
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7667 | https://github.com/PostHog/posthog/pull/19914 | 224b6213e5ae739404c33209c45f3edc7f0c9931 | 0de378dfa787e782a89331ebe3fe6b8c68b61564 | "2021-12-13T11:12:28Z" | python | "2024-01-23T14:21:00Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,666 | ["requirements.txt"] | Impossible to create PostHog Cloud account | ## Bug description
This was originally reported by a user, via Hubspot: "I would like to signup for PostHog Cloud but I always get redirected to the login page. Is it currently not possible to sign up for PostHog Cloud?"
I was able to replicate this by visiting Posthog.com, clicking 'Get Started' (either CTA), choosing PostHog Cloud and arriving at a login screen.
The login screen doesn't give any information about creating new accounts, only logging in. I initially thought this could be a messaging issue and that entering new information would lead to a sign-up process. I tried this with a few different test email addresses that don't have existing and each time only got 'Invalid password' responses.
<img width="477" alt="Screenshot 2021-12-13 at 11 23 16" src="https://user-images.githubusercontent.com/84011561/145803809-b00119c7-9c41-48d1-9783-9eb6b22e7ad3.png">
## Expected behavior
Sign-up flow.
## How to reproduce
1. PostHog.com
2. Click get started
3. Try to create new account
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7666 | https://github.com/PostHog/posthog/pull/18632 | 69becac2009bb4d17fcb2a5bd90d2a2b9219873a | 5b44c3b4c30616d9c4a481e7924e023db91ffe4b | "2021-12-13T10:57:47Z" | python | "2023-11-22T14:25:41Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,645 | ["frontend/src/scenes/funnels/FunnelLineGraph.tsx", "frontend/src/scenes/funnels/funnelLogic.ts", "frontend/src/scenes/funnels/funnelUtils.test.ts", "frontend/src/scenes/funnels/funnelUtils.ts", "frontend/src/scenes/insights/LineGraph/LineGraph.jsx", "frontend/src/types.ts"] | Funnel trends broken | ## Bug description
- Date range not applied
- Conversion windows not respected
## Expected behavior
- Data points before the conversion window is completed should be incomplete data points
- The chart should contain the dates that the query says it contains
## How to reproduce
1. View this [funnel](https://app.posthog.com/insights/Y1k2Wbh9/edit?insight=FUNNELS&actions=%5B%7B%22id%22%3A%222674%22%2C%22type%22%3A%22actions%22%2C%22order%22%3A1%2C%22name%22%3A%22User%20Signed%20Up%20(Comprehensive)%22%2C%22math%22%3A%22dau%22%7D%5D&events=%5B%7B%22id%22%3A%22%24pageview%22%2C%22name%22%3A%22%24pageview%22%2C%22type%22%3A%22events%22%2C%22order%22%3A0%2C%22math%22%3A%22dau%22%2C%22properties%22%3A%5B%7B%22key%22%3A%22email%22%2C%22value%22%3A%22is_not_set%22%2C%22operator%22%3A%22is_not_set%22%2C%22type%22%3A%22event%22%7D%5D%7D%5D&display=FunnelViz&layout=horizontal&interval=day&properties=%5B%5D&filter_test_accounts=true&funnel_to_step=1&funnel_viz_type=trends&exclusions=%5B%5D&funnel_from_step=0) or this [Slack thread](https://posthog.slack.com/archives/C02283301EK/p1639160785465300)
2.
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7645 | https://github.com/PostHog/posthog/pull/7698 | e86c569a96f4b72a173e095f50215fb32a0bdc26 | 590e6d81cb934c9a97080d6b6ce21955a18410fc | "2021-12-10T18:28:40Z" | python | "2021-12-14T05:32:51Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,619 | ["frontend/src/scenes/retention/RetentionLineGraph.tsx", "frontend/src/scenes/retention/RetentionModal.tsx", "frontend/src/scenes/retention/RetentionTable.tsx", "frontend/src/scenes/retention/retentionTableLogic.ts", "frontend/src/scenes/retention/types.ts", "frontend/src/types.ts"] | Retention line graph modal white screen | ## Bug description
*Please describe.*
- trying to click on a datapoint for retention line graph doesn't work. It whitescreens
*If this affects the front-end, screenshots would be of great help.*
## Expected behavior
The modal should appear
## How to reproduce
1. Go to retention
2. Make the chart type line graph
3. click on a datapoint
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7619 | https://github.com/PostHog/posthog/pull/7818 | c156b0be5d9a24a998cb67266259032f7e68049a | 30bedd625a044cc036c3f5ed31e4197c5cfc2a61 | "2021-12-10T01:06:12Z" | python | "2021-12-22T01:23:22Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,617 | ["frontend/src/lib/components/DateFilter/DateFilter.tsx", "frontend/src/scenes/insights/InsightTabs/InsightDisplayConfig.tsx", "frontend/src/scenes/insights/insightLogic.tsx"] | New dates UX is confusing | ## Bug description
While the new ways to display dates does provide value, I think it introduced some confusion worth addressing. In particular, the way we display dates when collapsed.
<img width="346" alt="" src="https://user-images.githubusercontent.com/5864173/145492803-07316fd7-fe43-41f1-b472-d1754fda733f.png">
## Expected behavior
IMHO should still display the relative time information (e.g. "Last 7 days") because:
a) It's generally easier to parse than a date range (at least for quick analysis, you may want to understand the specific range later).
b) It's confusing to select "Last 7 days" and then see a date range which is a different text (don't make me think).
c) The default date range is now a random date range which immediately makes me think something is outdated.
## How to reproduce
Create an insight.
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
CC @clarkus @corywatilo for input.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7617 | https://github.com/PostHog/posthog/pull/7757 | 6fb7662cfa269c0bf42be2781a705bfa283174b2 | b916ffad37d9a7005e3d897256e463f5611c010d | "2021-12-09T23:43:28Z" | python | "2022-01-05T00:04:23Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,611 | ["frontend/src/lib/components/LemonTable/LemonTable.scss"] | No space between feature flag key and description on wide screen | ## Bug description
There's no spacing here between the key and description:
## Expected behavior
A little bit of whitespace between would make it look a lot sharper. We'll likely want to keep that on the same row allowing us to see more rows on the page.
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
User request https://posthogusers.slack.com/archives/C01GLBKHKQT/p1639073353229800
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7611 | https://github.com/PostHog/posthog/pull/7627 | 1696ed5950bbe11756ba5f21633b32ff773681a9 | aabef6311a0af1935940945f8bcba045c7e0edb8 | "2021-12-09T18:46:03Z" | python | "2021-12-10T09:14:45Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,593 | ["frontend/src/scenes/insights/Insight.scss", "frontend/src/scenes/insights/InsightTabs/InsightDisplayConfig.tsx"] | New InsightDisplayConfig has scroll bars in smaller screens | ## Bug description
## Expected behavior
Multi-row
## How to reproduce
1. Go to insights
2. Resize screen
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
cc @mariusandra / @paolodamico for prioritization
cc @alexkim205 who implemented the feature
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7593 | https://github.com/PostHog/posthog/pull/7610 | aabef6311a0af1935940945f8bcba045c7e0edb8 | ec033443741c52020a04cb84338f9ebf2879ad98 | "2021-12-09T08:47:11Z" | python | "2021-12-10T09:25:06Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,588 | ["frontend/src/scenes/funnels/funnelLogic.test.ts", "frontend/src/scenes/funnels/funnelLogic.ts"] | Can't open persons from funnel step if not in edit mode | ## Bug description
Example [insight](https://app.posthog.com/insights/79cntdyB?insight=FUNNELS&actions=%5B%5D&events=%5B%7B%22id%22%3A%22%24pageview%22%2C%22name%22%3A%22%24pageview%22%2C%22type%22%3A%22events%22%2C%22order%22%3A0%7D%2C%7B%22id%22%3A%22%24pageview%22%2C%22type%22%3A%22events%22%2C%22order%22%3A1%2C%22name%22%3A%22%24pageview%22%7D%5D&display=FunnelViz&interval=day&properties=%5B%5D&filter_test_accounts=true&funnel_to_step=1&funnel_viz_type=steps&exclusions=%5B%5D&funnel_from_step=0)
Normal mode:
<img width="874" alt="Screen Shot 2021-12-08 at 23 55 56" src="https://user-images.githubusercontent.com/890921/145304515-b14d602b-9d1d-4380-b899-df22f32b9c44.png">
Edit mode:
<img width="804" alt="Screen Shot 2021-12-08 at 23 56 03" src="https://user-images.githubusercontent.com/890921/145304504-04f1420d-dfb9-4ee4-a6f1-453aa16d9990.png">
## Expected behavior
In both normal and edit mode I can open the list of persons.
## How to reproduce
1. Go to [insight](https://app.posthog.com/insights/79cntdyB?insight=FUNNELS&actions=%5B%5D&events=%5B%7B%22id%22%3A%22%24pageview%22%2C%22name%22%3A%22%24pageview%22%2C%22type%22%3A%22events%22%2C%22order%22%3A0%7D%2C%7B%22id%22%3A%22%24pageview%22%2C%22type%22%3A%22events%22%2C%22order%22%3A1%2C%22name%22%3A%22%24pageview%22%7D%5D&display=FunnelViz&interval=day&properties=%5B%5D&filter_test_accounts=true&funnel_to_step=1&funnel_viz_type=steps&exclusions=%5B%5D&funnel_from_step=0)
2. Clicking on the bar doesn't work & the completed persons isn't highlighted nor clickable (in normal mode, in edit mode it is)
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
Suspect it's this https://github.com/PostHog/posthog/blob/44c5491f077dbb6f368ac7151bb3272032b83b3d/frontend/src/scenes/insights/InsightTabs/FunnelTab/FunnelStepTable.tsx#L184 together with `insightMode === ItemMode.Edit` as part of is modal active condition from https://github.com/PostHog/posthog/pull/7415
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7588 | https://github.com/PostHog/posthog/pull/7609 | dbc805b4bda68a6dbfb63bae5f0f620764ab7c2f | 41dad99cd67fb1441d45cb9b240d0b1712ab0284 | "2021-12-08T22:57:24Z" | python | "2021-12-13T15:35:55Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,543 | ["cypress/integration/trends.js", "frontend/src/lib/components/DateDisplay/DateDisplay.scss", "frontend/src/lib/components/LemonTable/LemonTable.tsx", "frontend/src/scenes/insights/Insight.scss", "frontend/src/scenes/insights/InsightContainer.tsx", "frontend/src/scenes/insights/InsightsTable/InsightsTable.scss", "frontend/src/scenes/insights/InsightsTable/InsightsTable.tsx", "frontend/src/styles/global.scss"] | Details table in Trends slows down the page | ## In what situation are you experiencing subpar performance?
The details table in Trends is an AntD table, so it doesn't much our recent UI style, but more importantly it can be a real resource hog. For insights with many data points it can slow down the app, even to the point of the tab ceasing to respond. Just try loading trends with daily resolution over all time on PostHog Cloud.
This should be significantly improved by moving the table to `LemonTable`, which is lighter.
## How to reproduce
1. Create an Trends insight with hundreds of data points.
2. Watch the page slow down as the details table with hundreds of data points takes up a lot of resources.
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog, version/commit: 1.30.0
#### *Thank you* for your performance issue report – we want PostHog to go supersonic!
| https://github.com/PostHog/posthog/issues/7543 | https://github.com/PostHog/posthog/pull/7817 | 9a6b837066f29490b5cc9636522bbf6e65d3eb1c | c156b0be5d9a24a998cb67266259032f7e68049a | "2021-12-06T20:52:43Z" | python | "2021-12-21T22:19:23Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,535 | ["ee/api/test/test_authentication.py", "ee/settings.py", "posthog/api/authentication.py", "posthog/api/test/test_authentication.py", "posthog/api/test/test_signup.py", "posthog/urls.py", "posthog/utils.py", "posthog/views.py"] | Ability to restrict users to SSO login only | ## Is your feature request related to a problem?
We manage around 20 3rd party tools that our internal users can log into using G Suite (part of your enterprise / scale offering). When a user leaves, we need to disable their account. Currently we need to do this in G Suite and then any of the 3rd party tools where password login is still possible.
## Describe the solution you'd like
When a user leaves, we disable their account in G Suite and their account in PostHog becomes disabled too. Essentially, the ability to restrict specific users in PostHog to only be able to login via SSO (defaulting to this setting).
## Describe alternatives you've considered
Manually removing their account, and being the enemy of our IT manager.
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/7535 | https://github.com/PostHog/posthog/pull/9002 | c0a2abd6d721a14ee8cfb7fc9193a12cc04aa729 | 36ed41f7c0c20b8aba48181156741766b47034f7 | "2021-12-06T19:25:25Z" | python | "2022-03-16T13:46:49Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,530 | ["ee/clickhouse/queries/test/test_trends.py", "ee/clickhouse/queries/trends/clickhouse_trends.py"] | Bring back proper error messages when queries error | ## Bug description
Right now we say 'There are no matching events for this query' which is super misleading as in reality the query has errored
## Expected behavior
We used to have a big red error message that showed up, which would at least be more informative and could help users optimise their queries (smaller timeframes etc)
## How to reproduce
1.
2.
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7530 | https://github.com/PostHog/posthog/pull/7557 | 67fa03163fda91fb64282d7f4cc728f8461386df | 180be5413251295988408dba7fb071f6035915d4 | "2021-12-06T18:03:35Z" | python | "2021-12-07T16:55:33Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,430 | ["frontend/public/posthog-logo-default.svg", "frontend/src/scenes/authentication/WelcomeLogo.tsx"] | Change "PostHog Self-Hosted" logo to just "PostHog" | It makes total sense that on app.posthog.com the login screen has a "PostHog Cloud" logo – PostHog Cloud is a brand that represents _the_ multi-tenancy PostHog solution.
However it's weird for me that on self-hosted the login screen's logo says "PostHog Self-Hosted".
<img width="272" alt="Screen Shot 2021-11-27 at 16 12 30" src="https://user-images.githubusercontent.com/4550621/144054389-0d187a44-775f-452e-a680-cb59818ad460.png">
Self-hosted is not a brand – that's just PostHog. IMO we should be using the base logo without "Self-Hosted" here. | https://github.com/PostHog/posthog/issues/7430 | https://github.com/PostHog/posthog/pull/7822 | bdfe09a06b3ae5041cfcc48b864af6ebaf7cad33 | 5ec51aae2c3d74216898e44a2585776fed6551c8 | "2021-11-30T13:42:23Z" | python | "2021-12-22T11:39:39Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,411 | ["frontend/src/scenes/insights/insightLogic.test.ts", "frontend/src/scenes/insights/insightLogic.tsx"] | Bug loading some saved insights | ## Bug description
This has happened to me with different saved insights. I try to open them (as shown on the recording), and I just get an empty state, it also says it was recently refreshed. Yet, when I refresh the entire page, the insight loads correctly.
## Expected behavior
Insight should load correctly from the start.
## How to reproduce
Try opening a saved insight. If it was refreshed recently the bug will not show, you need to find an older insight.
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7411 | https://github.com/PostHog/posthog/pull/7451 | ba405c823caa52d729d4904aa891a6b76f0214cf | f4060127fc8ca713ff84c29a57d562b93ed977a2 | "2021-11-29T18:28:02Z" | python | "2021-12-08T14:18:44Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,371 | ["requirements.txt"] | Person modal takes forever to load in trends | Originally reported in #6513. | https://github.com/PostHog/posthog/issues/7371 | https://github.com/PostHog/posthog/pull/16695 | 30d7144831022a813b30374376e53d19142dd3fb | b9e745e0f1b1694bb07713bcb1bf6975fe221018 | "2021-11-25T21:39:35Z" | python | "2023-07-25T10:50:10Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,347 | ["frontend/src/lib/utils/eventUsageLogic.ts", "frontend/src/scenes/funnels/funnelLogic.ts", "frontend/src/scenes/insights/insightLogic.test.ts", "frontend/src/scenes/insights/insightLogic.tsx"] | Incorrect reporting on Insights | ## Bug description / Expected behavior
While exploring the app today, I found some important issues with reporting on insights:
1. When an insight is viewed from the "View mode" (i.e. when accessed by clicking on a saved insight) we don't trigger "insight viewed" or "insight analyzed". In the event, we should include an attribute that indicates the view mode too.
2. When opening an insight (funnel or otherwise) from saved insights into "View mode" we trigger `correlation viewed` & `correlation properties viewed` automatically even though correlation isn't actually viewed. CC @neilkakkar
3. We don't report when a user has "compare previous" enabled
## How to reproduce
1. Open an insight from the saved insights list with the JS console open. See events triggered.
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog (ClickHouse-based), version/commit: 1.30.0
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7347 | https://github.com/PostHog/posthog/pull/7439 | 92c28d0160a586137b2ede24d049141418a496fb | 1712645c5a5f2b2ec4048d74d62f4298f039e94b | "2021-11-25T00:18:18Z" | python | "2021-11-30T19:33:25Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,316 | ["frontend/src/lib/components/LemonButton/index.tsx", "frontend/src/lib/components/LemonRow/LemonRow.scss"] | Small overflow in project selection dropdown | ## Bug description
## Expected behavior
No overflow onto gear icon
## How to reproduce
1. Click on the project selection dropdown in production
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
cc @mariusandra for prioritization
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7316 | https://github.com/PostHog/posthog/pull/7334 | 12a2804ee927c6b8aa996fc8a346d84634495c1c | dd4950aca66556aa24caa3de20b935ab66ba60cc | "2021-11-24T08:46:19Z" | python | "2021-11-24T14:23:28Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,315 | ["frontend/__snapshots__/components-prompts--modal-prompt.png", "frontend/__snapshots__/lemon-ui-lemon-skeleton--presets.png", "frontend/src/lib/api.ts", "frontend/src/lib/lemon-ui/LemonModal/LemonModal.scss", "frontend/src/scenes/data-management/definition/DefinitionView.tsx", "frontend/src/scenes/data-management/definition/definitionLogic.ts", "posthog/api/event_definition.py", "posthog/api/property_definition.py", "posthog/api/test/test_event_definition.py", "posthog/api/test/test_property_definition.py"] | Allow cleaning up events and properties | ## Is your feature request related to a problem?
As a team accumulates data, they will have events/properties that are no longer in use that clutter their app.
Example from our team:
## Describe the solution you'd like
Under event/properties stats allow 'hiding' events/properties from view.
## Describe alternatives you've considered
Alternatively, go the route of "verified" events/properties (as He@p) does - show those first. See also https://help.heap.io/category/heap-administration/data-governance/
## Additional context
Note: Existing reports, etc should still work well even with 'removed' events/properties.
Related: https://github.com/PostHog/posthog/issues/7126
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/7315 | https://github.com/PostHog/posthog/pull/14877 | 8d00ed5605236b892af286b74c8607dfbf358f05 | c0d698db499d030aa0eee4d5189ae3db16554c3b | "2021-11-24T08:32:35Z" | python | "2023-03-23T21:50:08Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,300 | ["frontend/src/scenes/organization/Create/index.tsx", "frontend/src/scenes/organization/CreateOrganizationModal.tsx", "frontend/src/scenes/project/Create/index.tsx", "frontend/src/scenes/project/CreateProjectModal.tsx", "frontend/src/scenes/scenes.ts"] | Switching to a project with inadequate permissions locks out the user with no obvious way to recover | ## Bug description
As you can see below, I have adequate permissions for "PostHog App + Website" and "HogFlix Demo App", but clicking on the project named "Demo" causes PostHog to try to create a new project in the organization. I am then shown a warning which cannot be closed.
Because I don't have permission to create a project, but my `@current` project has been changed, logging out and back in under a different browser environment does not help, either.
https://user-images.githubusercontent.com/4645779/143066777-92bc0ba1-8a92-45d5-8c1d-04428e7a4afb.mp4
## Expected behavior
Perhaps clicking "Demo" is indeed supposed to create a new project — if it is not supposed to, there is a deeper problem.
It should be easier to recover from this error; even if the modal was closable it would be an improvement. Right now the solution is to visit some random 404 page on `app.posthog.com` and then change the project back to one with appropriate permissions.
## How to reproduce
1. Use a non-admin account or temporarily downgrade your org membership level via Django admin
2. Try to select "Demo" project
3. Notice the lock-out
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
| https://github.com/PostHog/posthog/issues/7300 | https://github.com/PostHog/posthog/pull/7305 | 38b1a08f7b6c7d3409034d334a5e0609cd233e1d | e619b6e1ca390556d59edec596f66d321f827904 | "2021-11-23T16:54:22Z" | python | "2021-11-24T12:49:20Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,292 | ["frontend/src/scenes/experiments/experimentsLogic.tsx", "frontend/src/scenes/insights/InsightsNav.tsx", "frontend/src/scenes/saved-insights/SavedInsights.tsx"] | Request: Better tooltips on insight tabs | ## Is your feature request related to a problem?
It has always bothered me that tooltips are inconsistently used in the Insights section. I think tooltips are great and that consistency is even better. Once a user discovers the tooltips we _do_ have, I think it's natural that they'd expect them to be consistent -- and they may expect this before hand.
Currently, our tooltips look like this:
```
Trends: (no tooltip)
Funnels: (no tooltip)
Retention: (no tooltip)
User Paths: (no tooltip)
Stickiness: Stickiness shows you how many days users performed an action within a timeframe. Example: If a user performed an action on Monday and again on Friday, it would be shown as "2 days".
Lifecycle: Understand growth by breaking down new, resurrected, returning and dormant users.
Sessions: View average and distribution of session durations.
```
## Describe the solution you'd like
Tooltips should be short, explanatory, consistent and optional. We shouldn't bury essential information there about how to use a tool (e.g. examples). I'd propose changing them to:
```
Trends: Visualize and breakdown how actions or events vary over time.
Funnels: Discover how many users complete or drop out of a sequence of actions.
Retention: See how many users return on subsequent days after an intial action.
User Paths: Trace the journeys users take within your product and where they drop off.
Stickiness: See what keeps users coming back by viewing the interval between repeated actions.
Lifecycle: Understand growth by breaking down new, resurrected, returning and dormant users.
Sessions: View the average and distribution of session durations.
```
## Describe alternatives you've considered
We could delete them all. Or leave as-is.
## Additional context
I have had a look at trying this myself (Marcus and I were discussing as an example a few weeks ago during a coding tutorial) but implementing _new_ tooltips seemed very difficult. So here we are.
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/7292 | https://github.com/PostHog/posthog/pull/7441 | eed62dad9fc4a7cdf660cdb910b70ec2888f4475 | da42c4be402b3bac84cd75db7bdcc9651025ea52 | "2021-11-23T13:54:12Z" | python | "2021-12-02T11:10:10Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,285 | ["frontend/src/lib/components/IntervalFilter/IntervalFilter.tsx", "frontend/src/lib/components/IntervalFilter/intervalFilterLogic.test.ts", "frontend/src/lib/components/IntervalFilter/intervalFilterLogic.ts", "frontend/src/lib/components/IntervalFilter/intervals.ts"] | Insight time selector resets are annoying | ## Bug description
I am running some analysis for the year to date, I start by looking at the analysis on a daily basis. I change to weekly, the time selector resets to 30 days, I change to monthly the time selector resets to 90 days.
## Expected behavior
The time selector stays on year to date.
## How to reproduce
1. Run an insight for the year to date
2. Change the breakdown to weekly/monthly
## Environment
- [ ] PostHog Cloud
- [x] self-hosted PostHog (ClickHouse-based), version/commit: 1.30.0
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7285 | https://github.com/PostHog/posthog/pull/7758 | f0ee9c1f71fb9f28056c72eca1b1ffac510eccbb | 9a2d5c0d37a17da70cada0f00cb8959371b7890f | "2021-11-23T10:36:07Z" | python | "2021-12-17T12:41:23Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,284 | ["frontend/src/lib/hooks/usePeriodicRerender.ts", "frontend/src/scenes/insights/ComputationTimeWithRefresh.tsx", "frontend/src/scenes/insights/InsightContainer.tsx", "frontend/src/scenes/insights/insightLogic.ts"] | Insight refresh disabled state is misleading | ## Bug description
I am running an insight and I want to refresh it, I get a tooltip that says that insights can be refreshed every 3 mins, but the refresh button remains disabled after 3 mins has passed.
## Expected behavior
I can refresh the insight.
## How to reproduce
1. Run insight
2. Wait 3 mins
3. Try to refresh
## Environment
- [ ] PostHog Cloud
- [x] self-hosted PostHog (ClickHouse-based), version/commit: 1.30.0
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7284 | https://github.com/PostHog/posthog/pull/9018 | b8fcbc51828909d772381253bedc8f3671f7c378 | fec52bbfcf291df76aee53b12b43d621b1aa3c0f | "2021-11-23T10:30:08Z" | python | "2022-03-14T20:05:02Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,193 | ["frontend/src/scenes/session-recordings/player/seekbarLogic.ts", "frontend/src/scenes/session-recordings/player/sessionRecordingPlayerLogic.ts"] | Error: [KEA] Can not find path "scenes.session-recordings.player.sessionRecordingPlayerLogic" in the store. | Sentry Issue: [POSTHOG-49X](https://sentry.io/organizations/posthog/issues/2794164856/?referrer=github_integration)
```
Error: [KEA] Can not find path "scenes.session-recordings.player.sessionRecordingPlayerLogic" in the store.
at reduce ([native code])
at None (../src/scenes/session-recordings/SessionPlayerDrawer.tsx:58:21)
at map ([native code])
at m (../src/scenes/session-recordings/player/PlayerEvents.tsx:74:17)
at o (../src/scenes/session-recordings/player/PlayerEvents.tsx:83:62)
...
(8 additional frame(s) were not displayed)
``` | https://github.com/PostHog/posthog/issues/7193 | https://github.com/PostHog/posthog/pull/7195 | 9b14556ae4db13e7beea3a0d74c029c67d537eaf | 91da31775d92c5078ba29754e9a3789827b0cf57 | "2021-11-18T01:26:14Z" | python | "2021-11-19T00:46:36Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,121 | ["cypress/integration/insights.js", "frontend/src/lib/hooks/useUnloadConfirmation.ts", "frontend/src/lib/utils.tsx", "frontend/src/scenes/insights/Insight.tsx", "frontend/src/scenes/insights/insightLogic.ts", "frontend/src/scenes/insights/insightSceneLogic.tsx", "frontend/src/scenes/sceneLogic.ts"] | Warn when leaving an insight with unsaved state | ## Is your feature request related to a problem?
Currently when you edit an insight, it's possible to leave the page in the middle of editing e.g. an insight name. All changes are thereupon lost.
Given user needs to manually "confirm" every change for titles, this can lead to annoying back-and-forth.
## Describe the solution you'd like
`window.confirm` or equivelent
## Describe alternatives you've considered
Autosaving titles
## Additional context
cc @paolodamico @clarkus
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/7121 | https://github.com/PostHog/posthog/pull/9091 | 78bc48cf94497b5c9a62aa3f2fba5e324e1187c8 | cca71901a616fe1ae698f8b280d45a011e42ee81 | "2021-11-15T14:16:45Z" | python | "2022-04-07T17:56:43Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,118 | ["frontend/src/lib/components/ChartFilter/chartFilterLogic.ts"] | Trends graph type selector shows as "Steps" when changing from Funnels | ## Bug description
This is a small UI bug. When you go from funnels to trends, the "chart type" dropdown still shows steps.
## Expected behavior
The "chart type" dropdown shows "Linear"
## How to reproduce
1. Insights
2. New insight -> Funnels (in dropdown)
3. Change to trends
4. Shows as "Steps" in the graph header:
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [x] self-hosted PostHog (Postgres-based, legacy), version/commit: e0fe499a0544a9a6ba914efcb1e58ed1fe1e3422
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7118 | https://github.com/PostHog/posthog/pull/7127 | 3d97ddceaea2e53abea6e788e3e351aacc2cd2ac | cff71f81cabf363857a53d6dbb2ffeaf4bd79550 | "2021-11-15T13:07:26Z" | python | "2021-11-16T09:49:57Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,091 | ["frontend/src/layout/navigation/SideBar/SideBar.tsx", "frontend/src/layout/navigation/TopBar/TopBar.tsx", "frontend/src/layout/navigation/navigationLogic.ts"] | Lemonade sidebar different open/closed states depending on resolution | ## Is your feature request related to a problem?
If I have the sidebar open, and make my screen smaller, the menu appears weirdly.
The opposite happens if I reload and make the screen bigger:
## Describe the solution you'd like
I think we should have two separate open/closed states for the sidebar, for the two different layouts.
## Describe alternatives you've considered
Closing the sidebar manually each time I resize my window.
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/7091 | https://github.com/PostHog/posthog/pull/7676 | 1fe276f78fb5e2055fba9d0ba946e9ec20853e19 | 44d7b4c356c8d5303f00e51a0810c4f78ed20c5b | "2021-11-12T09:24:07Z" | python | "2021-12-13T19:50:53Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,090 | ["frontend/src/layout/navigation/SideBar/SideBar.tsx", "frontend/src/layout/navigation/TopBar/TopBar.tsx", "frontend/src/layout/navigation/navigationLogic.ts"] | Persist the lemonade sidebar's position | ## Is your feature request related to a problem?
It won't stay closed
## Describe the solution you'd like
It'd persist my preference between reloads
## Describe alternatives you've considered
Closing it every time
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/7090 | https://github.com/PostHog/posthog/pull/7676 | 1fe276f78fb5e2055fba9d0ba946e9ec20853e19 | 44d7b4c356c8d5303f00e51a0810c4f78ed20c5b | "2021-11-12T09:20:58Z" | python | "2021-12-13T19:50:53Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,086 | ["requirements.txt"] | Correlation analysis property dropdown does not handle long property names well | ## Bug description
## Expected behavior
Better handling
## How to reproduce
1. Open correlation analysis
2. Open properties dropdown w/ a long property name
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
cc @clarkus @neilkakkar
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7086 | https://github.com/PostHog/posthog/pull/44 | e043ceb02e57a0b0ff4cb1ab427f02ba29a629dc | b9d70ea0b9fab9ef28067a6eacb67b94d917cf44 | "2021-11-12T07:38:21Z" | python | "2020-02-09T23:32:20Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,077 | ["frontend/src/layout/lemonade/Breadcrumbs/Breadcrumbs.scss"] | Scrolling overflow issue in lemonade | ## Bug description
I can scroll out of view in the lemonade view.
## Expected behavior
I should not be allowed to go out of bounds.
## How to reproduce
1. See recording above.
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7077 | https://github.com/PostHog/posthog/pull/7080 | b32a77fb564fc432284305676a84ca7fbcbb7feb | 89af87f40e28eb08213facdd57c2cd1facbfa164 | "2021-11-11T20:53:27Z" | python | "2021-11-11T22:50:30Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,063 | ["frontend/src/scenes/sceneLogic.ts"] | Feature flags side nav is not active when editing a feature flag | ## Bug description
See title
## Expected behavior
I'd expect this navigation item to be active
## How to reproduce
1. Go to feature flags
2. Click to edit a flag
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
cc @Twixes - I think you're currently patching stuff like this?
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7063 | https://github.com/PostHog/posthog/pull/7067 | f319948b2e1735ef26378ee7d64930c93377679e | bc06c274724a1fd53f2108883f37246d2a2df29f | "2021-11-11T12:35:35Z" | python | "2021-11-11T14:02:51Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,030 | ["frontend/src/lib/components/PayCard/PayCard.scss", "frontend/src/lib/components/PayCard/PayCard.tsx"] | Correlation analysis upsell modal is not closable | ## Bug description
If you try to click X it will still open pricing page
## Expected behavior
No X or it being closable
## How to reproduce
See screenshot
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog (ClickHouse-based), version/commit: latest
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
cc @neilkakkar @hazzadous @paolodamico
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7030 | https://github.com/PostHog/posthog/pull/7047 | 9ad6e3f27179db953e16ff1d0e10dd2899da6829 | d8493fe0eb7cf41478174b685fb11ee437271aa0 | "2021-11-10T14:03:36Z" | python | "2021-11-11T07:42:36Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 7,021 | ["cypress/integration/paths.js", "frontend/src/scenes/paths/NewPaths.tsx"] | Cannot Save Paths | ## Bug description
Cannot save paths because there is a circular reference in the JSON to be saved
## Expected behavior
Paths save
## How to reproduce
1. go to a new or existing Paths insight locally or on cloud
2. try to save it
3. see that nothing happens
4. go to the console and see the error
## Environment
- [X] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/7021 | https://github.com/PostHog/posthog/pull/7026 | fb148d6244a9d8d8f2e655702e5ea0f062298343 | 33f239998199401b902fbfd355365305800187ab | "2021-11-10T11:33:23Z" | python | "2021-11-10T16:58:39Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,964 | ["frontend/src/scenes/insights/Insights.scss", "frontend/src/scenes/insights/InsightsNav.tsx"] | Insight tabs do not extend to the full width of the content area | ## Bug description
The tabs are only wide enough to contain the available options. The intended behavior is for the tabs to take up the full width of the content area. In this example the tab bar should be the same width as the subsequent content.
<img width="1303" alt="Screen Shot 2021-11-08 at 2 01 06 PM" src="https://user-images.githubusercontent.com/254612/140825261-7a0a49d5-11d7-4e47-82e1-3d730918a7c9.png">
## Environment
- [x] PostHog Cloud
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/6964 | https://github.com/PostHog/posthog/pull/7071 | ff07577a471aca3311287c64dd1b14f3bb3a5f31 | 4b74b5a11c55318dac9b8b50ae28a7c1bae51dfe | "2021-11-08T22:02:56Z" | python | "2021-11-11T18:49:08Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,954 | ["frontend/src/lib/components/HelpButton/HelpButton.scss", "frontend/src/lib/components/HelpButton/HelpButton.tsx", "frontend/src/lib/components/LemonButton/LemonButton.scss", "frontend/src/lib/components/LemonButton/index.tsx", "frontend/src/scenes/billing/BillingSubscribed.tsx"] | Help utility menu out of place in new designs | ## Bug description
The help utility menu is using a different placement than other items in the component.
<img width="410" alt="Screen Shot 2021-11-08 at 9 08 12 AM" src="https://user-images.githubusercontent.com/254612/140787478-7f5c4848-1f9e-45ae-9bbd-e4585f57673b.png">
## Expected behavior
All items in the component should use the same vertical offset and alignement.
## How to reproduce
1. Log into cloud using chrome
2. Toggle on the new UI
3. Observe the icon placement
## Environment
- [x] PostHog Cloud
| https://github.com/PostHog/posthog/issues/6954 | https://github.com/PostHog/posthog/pull/6956 | edf6c9b1e9df85b92f54d0193f6a0d1f1a1cba09 | b017209a6eda5af945dd0258e7697be6a2011e3b | "2021-11-08T17:15:01Z" | python | "2021-11-08T19:12:36Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,934 | ["cypress/integration/paths.js", "frontend/src/scenes/paths/NewPaths.tsx"] | Paths don't load in Turbo mode | ## Bug description
Crash when opening paths from a saved insights list, or a dashboard. Same error both times:
```ts
export function pageUrl(d: PathNodeData, display?: boolean): string {
const incomingUrls = d.targetLinks
.map((l) => l?.source?.name?.replace(/(^[0-9]+_)/, ''))
.filter((a) => {
try {
new URL(a)
} catch {
return false
}
return a
})
.map((a) => new URL(a))
const incomingDomains = Array.from(new Set(incomingUrls.map((url) => url.origin)))
console.log(d)
// the next line crashes
let name = d.name.replace(/(^[0-9]+_)/, '')
if (!display) {
return name
}
```
Logging `d` shows the `name` contains the object itself.
Where does that come from?
## Expected behavior
The page should just open
## How to reproduce
1. Enable turbo mode
2. Click on a path from the saved insights or any dashboard scene
3. Kaboom
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
Reloading makes the insight appear, so not a P0, but should be fixed nevertheless..
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/6934 | https://github.com/PostHog/posthog/pull/7026 | fb148d6244a9d8d8f2e655702e5ea0f062298343 | 33f239998199401b902fbfd355365305800187ab | "2021-11-07T21:45:56Z" | python | "2021-11-10T16:58:39Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,801 | ["frontend/src/scenes/insights/InsightContainer.tsx", "frontend/src/scenes/insights/Insights.scss", "frontend/src/scenes/trends/Trends.tsx"] | Graphs should have a max height | ## Typical screen size
When viewing a graph at a typical screen size, the graph looks great:
## Tall screen
But if you have an abnormally tall window, the graph feels way too tall:
So on a viewport with a height around 1440px, it "looks" like a bug because the graph stretches way off the screen when it seems like it should fit without having to scroll.
## Solution
Maybe set a max height on the graph? | https://github.com/PostHog/posthog/issues/6801 | https://github.com/PostHog/posthog/pull/7065 | a0ebb9f4f52a16600cbd48805e2a1b151bde7863 | 1cd92515f543923e55b7912aeafeb4092ff2b0c1 | "2021-11-02T19:34:37Z" | python | "2021-11-11T16:43:13Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,799 | ["frontend/src/scenes/trends/viz/ActionsPie.tsx"] | [insights] Pie chart with last24hrs applied shows wrong persons when clicked | ## Bug description
*Please describe.*
- person numbers don't match when you click on a pie chart with last 24 hours applied
- ***They do work when you have the interval set to hourly before you switch to the pie chart
## Expected behavior
- numbers should match
## How to reproduce
1. https://app.posthog.com/insights?insight=TRENDS&actions=%5B%5D&events=%5B%7B%22id%22%3A%22cohort%20created%22%2C%22name%22%3A%22cohort%20created%22%2C%22type%22%3A%22events%22%2C%22order%22%3A0%2C%22math%22%3A%22dau%22%7D%5D&properties=%5B%5D&filter_test_accounts=true&exclusions=%5B%5D&funnel_from_step=0&funnel_to_step=1&compare=false&new_entity=%5B%5D&interval=hour&date_from=-24h&display=ActionsLineGraphCumulative
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/6799 | https://github.com/PostHog/posthog/pull/6824 | d631de1c3700810db95feb10f915c1eadcc0bf20 | 039c283b1cf2b2855b9cb2642e01656b4376023f | "2021-11-02T19:21:04Z" | python | "2021-11-04T15:22:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,721 | ["frontend/src/scenes/authentication/PasswordInput.tsx"] | Can we add password reveal button in the login page? | ## Is your feature request related to a problem?
Not actually, just little tweaking can do the work
*Please describe.*
I think we need a password reveal (eye) button in the login page as after filling login with wrong credentials it throws the error as "Invalid email or password" so in this case a user might need to see his/her password in order to know whether his password is wrong or he just simply is trying to login with wrong email address.
## Describe the solution you'd like
I don't think anything is there to describe the solution as it is quiet straight forward.
## Describe alternatives you've considered
## Additional context
If everything is okay, i'm willing to work on this
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/6721 | https://github.com/PostHog/posthog/pull/7296 | 76fc8cb7958f970c30d5d66f8efc29334d2e19d3 | 504263342e595e32a267fbe0cfe8e4412258bd43 | "2021-10-28T15:36:07Z" | python | "2021-11-24T06:05:38Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,633 | ["frontend/src/scenes/plugins/plugin/pluginLogsLogic.ts"] | Project set as undefined in plugins page | ## Bug description
Plugin logs weren't loading for me so I checked and saw that the request was being sent to:
```
https://app.posthog.com/api/projects/undefined/plugin_configs/2507/logs?limit=50
```
Notice the `undefined` in there - seems the project is being set incorrectly, _at least_ on the plugins page.
## Expected behavior
Form a correct request and give me my logs!
## How to reproduce
1. Go to the plugins page
2. Click on plugin logs
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/6633 | https://github.com/PostHog/posthog/pull/6634 | 6ab4b2673a9d2f17f79db314183eff1b3470f6ec | d307429732927ffafc4ebd4a22f53c34e32fd963 | "2021-10-25T13:05:56Z" | python | "2021-10-25T14:15:41Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,551 | [".github/workflows/docker-release-image-publish.yml", ".github/workflows/foss-release-image-publish.yml", ".github/workflows/foss-sync.yml"] | Ability to version lock the posthog-foss docker image | ## Is your feature request related to a problem?
As a developer, I would like to ensure that my docker image of posthog-foss is locked to a specific version, so I can control upgrades better and ensure sameness across dev, test and production environments.
## Describe the solution you'd like
Version locking as docker tags, preferably with semantic versioning like the posthog image has (maybe it can even use the same versions?)
## Describe alternatives you've considered
I could use the image build hash to lock my docker image to a specific version, but that's not a very good solution.
## Additional context
Currently, only the 'latest' tag is available: https://hub.docker.com/r/posthog/posthog-foss/tags
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/6551 | https://github.com/PostHog/posthog/pull/6584 | c87aae2338b01ebac1403a263eb7bd3d7279167c | 49dc208570460fce8785c0933633c6e33b4278d0 | "2021-10-19T14:56:26Z" | python | "2021-10-21T14:49:25Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,546 | ["frontend/src/lib/components/AppEditorLink/UrlRow.tsx", "frontend/src/scenes/project/Settings/index.tsx", "posthog/api/decide.py", "posthog/api/test/test_decide.py"] | Allow for permitted URL domain wildcarding | ## Is your feature request related to a problem?
*Please describe.*
A user has thousands of URLs matching `*.blahblah.com` (for example), and are only able to add a few dozen by hand. It would be nice for them if they could wildcard those domains or to not have to whitelist domains at all. Their primary concern was that session recordings for these domains would not be retrievable unless they were added to the permitted URLs list (and also session recordings before adding it to the domain would be irretrievable)
<img width="1275" alt="Screen Shot 2021-10-19 at 9 23 48 AM" src="https://user-images.githubusercontent.com/25164963/137918568-ecc72abd-be6b-410c-84d9-63870b19d2f8.png">
## Describe the solution you'd like
A way to make it easier to apply similar domains together
## Describe alternatives you've considered
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/6546 | https://github.com/PostHog/posthog/pull/6660 | d46a98f74d849b2868fbe145fdb4b6ec453dfc89 | 8908753a0670e9952eda40dcb4f66e4f68121ea6 | "2021-10-19T13:09:35Z" | python | "2021-10-27T11:22:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,541 | ["frontend/src/scenes/insights/ActionFilter/ActionFilterRow/ActionFilterRow.tsx", "frontend/src/scenes/insights/ActionFilter/entityFilterLogic.ts"] | Can't add step to funnel if I remove the first step | ## Bug description
I'm on a funnel:
If I accidentally delete the first step:
Then I can't add any step to the funnel
## Expected behavior
I should be able to add a step to the empty funnel
## How to reproduce
1.
2.
3.
## Environment
- [X ] PostHog Cloud
- [X] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/6541 | https://github.com/PostHog/posthog/pull/6556 | 716e8f1943ae119e9929cede184aa30ba8f6be64 | 10a4a6a6623b3d3eb77c4c6bccb15b79a338e833 | "2021-10-19T11:14:41Z" | python | "2021-10-21T16:44:32Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,483 | ["frontend/src/scenes/session-recordings/player/Seekbar.scss"] | Recording playback bugs + internal feedback | An issue to track feedback + issues on the new recording playback experience.
🐛 Bugs:
- [x] The new progressive loading logic behaves non-intuitively for long recordings. Try skip ahead ~40 minutes here: https://app.posthog.com/recordings?sessionRecordingId=17c82b1e00d5e-0fbae39a44ef0f-123b6650-1aeaa0-17c82b1e00e11e9 (from @macobo)
- [x] If playback catches up to buffering, the player pauses and doesn't restart. Repro's consistently for me if my speed is set to 16x - especially if I throttle the connection (from @rcmarron)
- [x] If you use the "Skip back X seconds" to move from buffering to non-buffering, the "buffering..." sign never goes away
- [x] Hard to repro, but sometimes the player gets stuck in a "always buffering" state (the recording is playing in the background, but the buffering sign is still shown). I think it only happens on recordings where the entire recording is returned in a single request. #6969
- [x] If you click the thumb in the player repeatedly, it jumps backward a couple of times.
https://user-images.githubusercontent.com/4813045/139320274-4494aee8-b769-4c36-af55-fea28467a157.mov
- [x] If you click on recent recording (<1min ago and <1min duration), timestamp is NaN:NaN:NaN #6969
- [x] Clicking 1 pixel above or below seekbar doesn't seek the thumb #6962
🗣 Feedback:
- https://github.com/PostHog/posthog/issues/6473 | https://github.com/PostHog/posthog/issues/6483 | https://github.com/PostHog/posthog/pull/6962 | b78499d61a40da06ba740eff1dedcf3b10578610 | 23ce7aaf163563717193e1942421ad08931f4921 | "2021-10-15T15:25:10Z" | python | "2021-11-08T22:37:37Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,285 | ["frontend/src/scenes/dashboard/Dashboard.tsx", "frontend/src/scenes/dashboard/DashboardItem.tsx", "frontend/src/scenes/dashboard/DashboardItems.scss", "frontend/src/scenes/dashboard/DashboardItems.tsx", "frontend/src/scenes/dashboard/dashboardLogic.test.ts", "frontend/src/scenes/dashboard/dashboardLogic.tsx", "frontend/src/scenes/insights/EmptyStates/EmptyStates.tsx", "frontend/src/scenes/insights/Insight.scss", "frontend/src/styles/global.scss", "frontend/src/styles/style.scss"] | Dashboard (or insight) fails to load | ## Bug description
I quite frequently have problems where either an Insight or Dashboard does not load. In this case, the dashboard does not load.
## Expected behavior
The Dashboard or Insight should load.
If the error is caused by a network issue of some sort (but, as mentioned, this happens a lot) then a different message in the center of the screen may be better.
## How to reproduce
The following video shows the Dashboard as empty. However, it should not be empty.
https://user-images.githubusercontent.com/328367/136211017-d9c85863-f8f9-4fda-a727-0ad2054b0c9b.mp4
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/6285 | https://github.com/PostHog/posthog/pull/7427 | a64b808a633508398ca6091796f2f51616e7523c | df88b7daa40e2edd844e3a9e45736136df4292f3 | "2021-10-06T13:25:56Z" | python | "2021-12-01T14:30:42Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,282 | ["frontend/src/lib/components/CommandPalette/commandPaletteLogic.ts"] | Suggestion: Changing the language on search results for dashboards | A very minor suggestion, but can we perhaps change the language used for the suggested results around dashboards in PostHog's search feature?
Currently the language we use is 'Go to [Feature Name] [Item Name]'. The only item names which appear to come up in search suggestions are around dashboards, but this can create results which are hard to parse, eg.:
_Go to Dashboard Tiina Test
Go to Dashboard Default
Go to Dashboard 🚀 A Product Dashboard_
It can also lead to results which could be confusing and indicate a different result, depending on the name of the dashboard, eg:
_Go to Dashboard Plugins_ (Could suggest either a dashboard about plugins, or plugins that work with the dashboard)
_Go to Dashboard Default
Go to Dashboard Logins
Go to Dashboard Content_
Icons are used to mitigate some of these issues, but not all.
A simple solution would be to change the language to 'Go to [Feature Name]: [Item Name]', with the colon only appearing if an item name is shown. This would me existing terms remain as they are (e.g. _'Go to Persons'_), but dashboards become clearer (e.g. _'Go to Dashboard: Plugins', 'Go to Dashboard: Tiina Test'_).
<img width="587" alt="Screenshot 2021-10-06 at 13 57 07" src="https://user-images.githubusercontent.com/84011561/136206680-d495e7d9-baa1-40fc-a30b-a651467a79ad.png">
| https://github.com/PostHog/posthog/issues/6282 | https://github.com/PostHog/posthog/pull/6291 | 96760e0096f9a482dd486e37b787e927a7e0f444 | 3520b553a45ce00aed7d7b50d27996e0db5d33e3 | "2021-10-06T12:55:56Z" | python | "2021-10-07T07:44:14Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,237 | ["frontend/src/scenes/authentication/Login.tsx", "frontend/src/scenes/authentication/PasswordInput.scss", "frontend/src/scenes/authentication/PasswordInput.tsx", "frontend/src/scenes/authentication/Signup.tsx", "frontend/src/scenes/authentication/__stories__/Login.stories.tsx", "frontend/src/scenes/authentication/__stories__/login-self-hosted-saml.json"] | Small spacing inconsistency in new sign up / sign in workflows | ## Bug description
I noticed some label spacing mis-alignments during the demo this morning. In the account creation portion of the flow, it looks like the labels are using slightly different markup patterns and have different styling applied. See the screenshots attached:
**Sign in**
<img width="1634" alt="Screen Shot 2021-10-04 at 12 13 48 PM" src="https://user-images.githubusercontent.com/254612/135910508-9508d042-42e9-47da-b4ce-e051963a92a5.png">
**Create account**
<img width="1365" alt="Screen Shot 2021-10-04 at 12 14 27 PM" src="https://user-images.githubusercontent.com/254612/135910527-93ac604d-5fb8-40d7-8084-2f7529d1753f.png">
## Expected behavior
It's a minor issue, but I would expect field spacing to be consistent across workflows. The spacing used on the sign in workflow feels more on target to me.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/6237 | https://github.com/PostHog/posthog/pull/6472 | 4477c81f1f3ca7dbfce99e0bd66c2424d724582b | faa6377a57a77c4f3e11fb10f51cd42b1ec092ef | "2021-10-04T19:16:42Z" | python | "2021-10-15T22:11:16Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,202 | ["frontend/src/toolbar/actions/ActionsList.tsx", "frontend/src/toolbar/actions/actionsLogic.test.ts", "frontend/src/toolbar/actions/actionsLogic.ts"] | Make toolbar with many actions accessible | ## Is your feature request related to a problem?
Client reported:
```
Official feature request. A search box for actions in the post hog tool bar:
250ish actions is a lot to scroll through
I would go so far to say that the toolbar experience is challenging to use when you can’t find the action that you want to update by scrolling through the list.
This is an example of where the action selector was quite weak in our application. Giving a more hardened selector fixed the issues i was facing:
But I used the posthog application instead of the toolbar as it gave me a search box.
```
Slack link: https://posthogusers.slack.com/archives/C026SNNE430/p1633035664131700
## Describe the solution you'd like
More accessible UI for actions
## Describe alternatives you've considered
## Additional context
cc @clarkus
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/6202 | https://github.com/PostHog/posthog/pull/6587 | e4939b767e9a8427e9ef059bbdad4f62fa6a3bd9 | 9e552d51e482be10716428797b7e064076a91ec8 | "2021-10-01T07:31:25Z" | python | "2021-10-21T08:37:14Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,192 | ["frontend/src/scenes/events/EventsTable.tsx", "frontend/src/scenes/events/eventsTableLogic.test.ts", "frontend/src/scenes/events/eventsTableLogic.ts"] | More closely associate actions loading spinner with table | When creating an Action and after saving the definition, it isn't clear that a query is being run. This makes it hard to tell if the definition is incorrect, or if a query is actively being run.
## After saving a query (with a definition that should return data)...
### For several seconds, you get this:
### Clicking (browser) refresh, I see a loading icon just below the action name:
## Two UX issues:
1. After a few seconds, the table below _does_ end up populating, but there's no spinner in the area, so unless you know where to look for the spinner (just under the action name), it looks like the definition doesn't return any data
2. After initially saving a definition, it doesn't appear the query is being run. I had to refresh the browser to get the spinner, showing me _something_ was happening
(This is on Cloud) | https://github.com/PostHog/posthog/issues/6192 | https://github.com/PostHog/posthog/pull/6256 | 27f9481716191ba26cafaa6932c82b7ee6dfa308 | ad17f9c7beb33cb3622d31bf281cd9c061bd909a | "2021-09-30T15:25:22Z" | python | "2021-10-06T14:34:01Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,180 | ["frontend/src/scenes/insights/InsightsTable/InsightsTable.tsx"] | Can not sort trends "table" insight | ## Bug description
This doesn't work when the insight type is "trends" -> "table".
## Expected behavior
It should sort
## How to reproduce
1. Open insights/trends
2. Break down by something
3. Look at the table graph
4. Try to sort
5. See that it doesn't work
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
This works on the table under a normal ("linear" chart) trends insight.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/6180 | https://github.com/PostHog/posthog/pull/6232 | 7c68e1d1546fc4172b9d480858f4ceac98709fef | aa0ab19c5b5de9c24fe7f30b8c3c43c7948e5bb0 | "2021-09-29T14:57:11Z" | python | "2021-10-04T20:55:52Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,144 | [".github/workflows/benchmark.yml", ".gitignore", "ee/benchmarks/README.md", "ee/benchmarks/__init__.py", "ee/benchmarks/asv.conf.json", "ee/benchmarks/benchmarks.py", "ee/benchmarks/helpers.py", "ee/clickhouse/materialized_columns/util.py"] | Benchmarking suite for query performance | ## Is your feature request related to a problem?
Currently knowledge on query optimization in clickhouse is pretty centralized. This means that when rewriting queries a lot of manual work needs to be made by a select few to ensure we don't lose performance in our wide product.
## Describe the solution you'd like
Have a benchmarking suite.
## Describe alternatives you've considered
Winging it
## Additional context
Some requirements:
- Run benchmark against master + labeled branches, indicate when performance changes
- Use database time over runtime for more accurate measurements
- Use dedicated server (over CI) for running the clickhouse node
- Have a good and representative dataset that we can filter in various ways as we improve performance. Generated datasets require a lot of maintanence and will invalidate previous measurements.
Initial proposal:
- Use [Airspeed velocity](https://asv.readthedocs.io/en/stable/using.html) library to do the benchmarks
- Set up a clickhouse installation with a copy of some of our teams data (or anonymized data) to run against
- Set up tests. Use fixed time-frames in benchmarks when possible.
- Integrate it with PRs, e.g. as with https://github.com/sympy/sympy/pull/21757/files, also run against master. Set concurrency=1
- Publish results somewhere
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/6144 | https://github.com/PostHog/posthog/pull/6187 | 4ae063d0e612ac657b82b68a4191aead3a26fe64 | 437b2982cdfd8a0dea45a7b0e2d1a0624a18b807 | "2021-09-28T10:45:29Z" | python | "2021-10-01T12:20:58Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,131 | ["frontend/src/lib/components/ObjectTags/index.tsx", "frontend/src/scenes/insights/InsightMetadata/InsightMetadata.scss", "frontend/src/scenes/insights/InsightMetadata/InsightMetadata.tsx", "frontend/src/scenes/insights/InsightMetadata/index.ts", "frontend/src/scenes/insights/InsightMetadata/insightMetadataLogic.test.ts", "frontend/src/scenes/insights/InsightMetadata/insightMetadataLogic.ts", "frontend/src/scenes/insights/InsightMetadata/utils.test.ts", "frontend/src/scenes/insights/InsightMetadata/utils.ts", "frontend/src/scenes/insights/Insights.tsx", "frontend/src/scenes/insights/insightLogic.tsx"] | Updates to saved insights meta fields | ## Is your feature request related to a problem?
There's been quite a bit of feedback on the latest iteration of insights. We're going to roll back to a previous solution that isolates editing names, descriptions, and tags to inline actions.
## Describe the solution you'd like
Use inline actions to trigger editable states for descriptive fields. The insight should still default to a unique name.
https://www.figma.com/file/gQBj9YnNgD8YW4nBwCVLZf/PostHog-App?node-id=3245%3A33481
## Describe alternatives you've considered
None I really think we should do this.
## Additional context
#5616 #5416 #5702 #3408 #6048
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/6131 | https://github.com/PostHog/posthog/pull/6159 | fda8313be69836cf32d14ffc6a9ebbdbc462aa84 | c2a1f30a56c2307d86123aa919c94a1be107c63c | "2021-09-27T20:19:20Z" | python | "2021-10-05T10:56:34Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,109 | ["frontend/src/scenes/funnels/FunnelBarGraph.tsx", "frontend/src/scenes/funnels/funnelUtils.ts", "frontend/src/scenes/insights/InsightTabs/FunnelTab/FunnelStepTable.tsx", "frontend/src/scenes/insights/InsightTabs/FunnelTab/funnelStepTableUtils.tsx"] | Funnels UI minor improvements | ## Is your feature request related to a problem?
While using funnels I noticed a few things to improve on the new layout.
<img width="1311" alt="" src="https://user-images.githubusercontent.com/5864173/134848856-f67b03ec-ab12-458b-8e51-2186bb1e4de8.png">
## Describe the solution you'd like
Edit: I'll address this in a separate issue.
- [ ] The tooltip is hard to read as there's a ton of stuff going on, maybe we can add some icons, a bit more spacing and then maybe things on parenthesis could have a smaller font and muted color. CC @clarkus for thoughts.
Edit: Below addressed in #6133
- [x] The checkbox has a foreign blue hue, ideally we would want to match the series color.
- [x] We've changed the main bar color from the main primary color but I think this helped make more obvious that you can click on the bar.
- [x] We use "Comp. rate" & "rate" interchangeably in the table header.
- [x] The average time can get into 2 lines in some cases which doesn't look great.
- [x] The tooltip's title shows a "None" (probably a breakdown value) but it doesn't make sense in this context.
- [x] The "Baseline" label can be confusing if you don't have a breakdown.
## Describe alternatives you've considered
Not applicable.
## Additional context
CC @alexkim205
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/6109 | https://github.com/PostHog/posthog/pull/6133 | a0775d7faedb5b45d19c045ca2737369aef3c1f5 | 77d3d66754ab6a299a10907ab25f85d9b43bb553 | "2021-09-27T05:23:59Z" | python | "2021-09-28T20:12:30Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,101 | ["frontend/src/scenes/insights/InsightContainer.tsx", "frontend/src/scenes/insights/InsightTabs/InsightDisplayConfig.tsx"] | Changing the time range for an insight results in triggering the edit view | ## Bug description
Changing the time range for an insight shouldn't trigger the edit view.
## Expected behavior
This should modify the time range in place and not prompt for the user to edit the insight.
## How to reproduce
1. Go to a saved insight
2. Change the time range
3. Observe that you're taken to the edit mode
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
https://user-images.githubusercontent.com/254612/134700019-a63b98b9-3ef7-4171-ad3d-a81d1d22fb5f.mov
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/6101 | https://github.com/PostHog/posthog/pull/6129 | 4e47a6ddeb6b93c4a7f92e2aaaf261ec96825b36 | 9315a0d76ac97d6a2f511c4985d2da7359239759 | "2021-09-24T15:22:59Z" | python | "2021-09-28T04:11:49Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,001 | ["ee/clickhouse/queries/funnels/funnel_time_to_convert.py", "ee/clickhouse/queries/funnels/test/test_funnel_time_to_convert.py", "ee/clickhouse/views/test/test_clickhouse_insights.py", "frontend/src/lib/utils/eventUsageLogic.ts", "frontend/src/scenes/funnels/funnelLogic.ts", "frontend/src/scenes/funnels/funnelUtils.ts", "frontend/src/scenes/insights/Histogram/Histogram.tsx", "frontend/src/types.ts"] | Gridlines show over bars in time conversion | ## Bug description
<img width="696" alt="Screen Shot 2021-09-16 at 2 37 41 PM" src="https://user-images.githubusercontent.com/13460330/133689529-c4fffc7f-53f8-494e-b7a8-7fb656fd50e6.png">
## Expected behavior
Bars and labels always show on top of axes and gridlines.
## How to reproduce
1. https://app.posthog.com/insights?insight=FUNNELS&properties=%5B%5D&filter_test_accounts=false&events=%5B%7B%22id%22%3A%22%24pageview%22%2C%22name%22%3A%22%24pageview%22%2C%22type%22%3A%22events%22%2C%22order%22%3A0%7D%2C%7B%22id%22%3A%22%24pageview%22%2C%22name%22%3A%22%24pageview%22%2C%22type%22%3A%22events%22%2C%22order%22%3A1%7D%2C%7B%22id%22%3A%22%24pageview%22%2C%22name%22%3A%22%24pageview%22%2C%22type%22%3A%22events%22%2C%22order%22%3A2%7D%5D&actions=%5B%5D&exclusions=%5B%5D&interval=day&funnel_from_step=0&funnel_to_step=1&new_entity=%5B%5D&funnel_viz_type=time_to_convert&display=FunnelViz
## Environment
- [X] PostHog Cloud
- [X] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [X] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/6001 | https://github.com/PostHog/posthog/pull/6002 | 9aa06a8b9572dbc09e8bfa4e2b91b56e8d1dce2f | e85fde39214f9eb26b959cf0d2d419cfa8d49e73 | "2021-09-16T21:41:45Z" | python | "2021-09-17T09:36:15Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 5,946 | ["frontend/src/lib/constants.tsx", "frontend/src/scenes/funnels/funnelLogic.test.ts", "frontend/src/types.ts", "posthog/api/insight.py", "posthog/api/test/__snapshots__/test_dashboard.ambr", "posthog/models/insight.py"] | Dive dashboard launch | We worked on this during the offsite, but there are a couple of things that are still needed to productionize it:
1. move it to ee & release for all paid customers
2. product design: currently we just prepend the dashboardItem we came from, but dashboards can have layouts, which would get messed up if we did it this way. It would be great to be able to see where we came from (e.g. to know when the spike in the graph happened exactly that made me click on the dive link, but I don't know how to design it)
3. Code changes based on ^
4. Blog post (including a diving hedgehog @lottiecoxon) - I propose with the different user stories we used in our demo
cc @samwinslow @jamesefhawkins anything else I'm missing?
| https://github.com/PostHog/posthog/issues/5946 | https://github.com/PostHog/posthog/pull/8946 | aa5f741da5c566a926a1085a682c7791fbcff3ba | 7438d0443cfb7131f299b79e3fc7e88fa6a4e876 | "2021-09-14T16:23:10Z" | python | "2022-03-14T12:04:36Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 5,924 | ["frontend/src/scenes/dashboard/DashboardItem.tsx", "frontend/src/scenes/dashboard/DashboardItems.scss"] | Inconsistent options for Viewing / Configuring dashboard items | Funnels are currently the only dashboard item type with this large "Configure" banner. It pops up on hover, which in my opinion is a bit annoying as it blocks content behind it. In the example below, if you're using a mouse which doesn't support horizontal scroll, it's impossible to view the whole funnel because the scrollbar is covered.
<img width="874" alt="Screen Shot 2021-09-13 at 11 01 53 AM" src="https://user-images.githubusercontent.com/4645779/133108008-7c5fb05a-e622-4be5-853c-340b1fa3dc83.png">
I think we should have a standard way to indicate common actions on dashboard items. One way I explored this during the hackathon was this:
<img width="442" alt="Screen Shot 2021-09-13 at 10 57 23 AM" src="https://user-images.githubusercontent.com/4645779/133108327-fa167c81-ac2f-404c-81a3-32ef64959f2c.png">
... which looks better to me than:
<img width="438" alt="Screen Shot 2021-09-13 at 10 55 45 AM" src="https://user-images.githubusercontent.com/4645779/133108669-a5a620fb-90f7-4f26-a30c-dfab0b53d870.png">
But my solution still isn't perfect as it causes the title to truncate.
Cc'ing @clarkus as this is most of all a design question.
| https://github.com/PostHog/posthog/issues/5924 | https://github.com/PostHog/posthog/pull/5953 | 3a44053bbd34283042dc26681d1a121dd7cc992e | 78027ca061caf530f21dff27f7f86307c598dfd8 | "2021-09-13T15:07:43Z" | python | "2021-09-15T14:56:22Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 5,922 | ["frontend/src/lib/components/CopyToClipboard.tsx", "frontend/src/lib/components/InsightLabel/InsightLabel.scss", "frontend/src/scenes/insights/InsightTooltip/InsightTooltip.scss", "frontend/src/scenes/insights/InsightTooltip/InsightTooltip.tsx", "frontend/src/scenes/persons/Person.tsx", "frontend/src/scenes/persons/PersonsTable.tsx", "frontend/src/scenes/trends/PersonModal.tsx"] | Person modal users misaligned | ## Bug description
The users here are strangely right-aligned:
## Expected behavior
I'd expect them to be left-aligned
## How to reproduce
1. Identify some users
2. Click on trends
3. See some problems
## Environment
- [ ] PostHog Cloud
- [x] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [x] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
1. Long distinct IDs get cut correctly:
2. This is also off:
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/5922 | https://github.com/PostHog/posthog/pull/5931 | 8040467bea6224290ad9379041065194ffb8b4ad | dc199a96763501ed11f4332574b9e4dc91f1e90f | "2021-09-13T14:59:57Z" | python | "2021-09-14T09:21:15Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 5,917 | ["frontend/src/scenes/dashboard/DashboardItems.scss"] | Dive dashboard icons have unsightly background color | ## Bug description
Minor issue — only affects those with dive dashboard feature flag. These icons should inherit background color of the button, or have it transparent.
<img width="632" alt="Screen Shot 2021-09-13 at 8 21 50 AM" src="https://user-images.githubusercontent.com/4645779/133082642-f9048686-c6c1-4238-8543-12f0a9c9b333.png">
## Expected behavior
## How to reproduce
1.
2.
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/5917 | https://github.com/PostHog/posthog/pull/5970 | 2f7aa20f2b3089a8c82690aee9dfe96f6e39645f | 929fe43a87a165cec9ccba0984c08025143f5e70 | "2021-09-13T12:23:32Z" | python | "2021-09-16T11:35:02Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 5,876 | ["ee/clickhouse/queries/column_optimizer.py", "ee/clickhouse/queries/event_query.py", "ee/clickhouse/queries/test/test_event_query.py", "posthog/queries/test/test_trends.py"] | Trends 500 when entity is action with person filter | ## Bug description
Sentry error: https://sentry.io/organizations/posthog/issues/2588698757/events/62db81be9cbe44638988eda3dc72ad8c/?project=1899813
## Expected behavior
Don't fail
## How to reproduce
1. Create an action with a person filter (e.g. `User Signed Up (self-hosted)` on cloud)
2. Try to graph that action
3. See no results, error in backend
## Environment
- [x] PostHog Cloud
- [ ] self-hosted PostHog (ClickHouse-based), version/commit: _please provide_
- [ ] self-hosted PostHog (Postgres-based, legacy), version/commit: _please provide_
## Additional context
`ClickhouseEventQuery._determine_should_join_persons` does not resolve action type entity properties. Rather than do it there we can likely piggy-back off of `ColumnOptimizer` here.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/5876 | https://github.com/PostHog/posthog/pull/5879 | 82ef50a1e78dc72281275136398d9a0d2fc972ca | ec374a8f305ae330d4d490d9da7083b1f7653de0 | "2021-09-09T13:08:42Z" | python | "2021-09-10T08:22:45Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 5,858 | ["frontend/src/layout/navigation/TopNavigation.tsx", "frontend/src/layout/navigation/navigationLogic.ts", "frontend/src/scenes/organization/Create/index.tsx", "frontend/src/scenes/organization/CreateOrganizationModal.tsx", "frontend/src/scenes/project/Create/index.tsx", "frontend/src/scenes/project/CreateProjectModal.tsx"] | Sort project list by name | ## Is your feature request related to a problem?
In the project dropdown list, projects are not sorted. This is annoying when I need to find a project or when I need to go through the projects one by one (e.g. to update a shared setting, like the list of test users to exclude).
## Describe the solution you'd like
Sort the project list alphabetically.
## Describe alternatives you've considered
Manually scanning the list.
## Additional context
Our organization uses a lot of projects, so this may be unique to us or a small number of users.
| https://github.com/PostHog/posthog/issues/5858 | https://github.com/PostHog/posthog/pull/5861 | f36c5f40b7471d77a3fa8301dc6af65207e7b3b5 | c9d27d7983e383b1d6ba37efb734c60e04fddc6e | "2021-09-08T15:28:05Z" | python | "2021-09-08T17:50:35Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 5,853 | ["ee/api/test/test_authentication.py", "posthog/api/signup.py"] | Allow any SAML-sourced user to provision automatically | ## Is your feature request related to a problem?
Currently if you login with SAML and you don't have an account on the PostHog instance one of two things happen: a) either a new account is created **if the email matches the domain whitelist** or b) you get turned down at the door. Yet after some thought, the point of SAML is that you manage user provisioning in a separate centralized system, so we shouldn't have the extra domain check.
## Describe the solution you'd like
If a user logins through SAML and their account doesn't exist, create it automatically, regardless of whether it matches the domain whitelist.
## Describe alternatives you've considered
Keeping as is.
## Additional context
There's a complicating factor which is that SAML login is instance-based yet user signup is organization-based, so there's the edge case of an instance having multiple orgs. Should the user then be signed up to all organizations?
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/5853 | https://github.com/PostHog/posthog/pull/5910 | 6fd1321b12c103269a2e8e4a496e4c924d9ff756 | 1012be975ab6c5b0c70c84ffec5687763cabad33 | "2021-09-08T08:39:14Z" | python | "2021-09-13T10:04:46Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 5,839 | ["ee/api/test/test_authentication.py", "posthog/api/signup.py"] | Fix team member invites with SAML | ## Bug description
When opening an invite link and then using SAML to sign up, you don't actually accept the invite, and you're only allowed to sign up if your email address's domain matches the domain whitelist. This happens because for some reason the session state (where the invite ID is stored) is not kept throughout the SAML flow. During the callback to PH, the state appears blank.
## Expected behavior
When opening an invite link and using SAML to sign up, I expect to be able to sign up as with any other SSO and get rejected if my email address does not match the one on the invite.
## How to reproduce
1. Create an invite link
2. Try signing up with SAML
3. See a signup error message
## Environment
- [ ] PostHog Cloud
- [X] self-hosted PostHog, version/commit: _please provide_
## Additional context
@Twixes would you be able to pick this up? Think you have strong context on social login to figure it out (is not particularly a SAML problem).
#### *Thank you* for your bug report – we love squashing them! | https://github.com/PostHog/posthog/issues/5839 | https://github.com/PostHog/posthog/pull/5910 | 6fd1321b12c103269a2e8e4a496e4c924d9ff756 | 1012be975ab6c5b0c70c84ffec5687763cabad33 | "2021-09-07T13:59:07Z" | python | "2021-09-13T10:04:46Z" |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.