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 | 3,676 | ["docker-compose.yml"] | docker-compose should pin image versions | ## Bug description
When updating the containers in a docker-compose setup the containers can upgrade over major versions and break backwards compat. Eg. I wanted to update the posthog container but ran `docker-compose pull` which changed the postgres instance from version 12 to 13 - which then couldn't start due to the data not being backwards compat.
Pinning image versions such as `postgres:12-alpine` ensures the version will always be compatible. Likewise for any other images in use.
## Expected behavior
Updating images should not jump major versions and break posthog.
## How to reproduce
- Install with docker-compose
- Wait until postgres releases a new `latest` tag major version
- Try to update posthog
## Environment
- [ ] PostHog Cloud
- [x] self-hosted PostHog, version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3676 | https://github.com/PostHog/posthog/pull/4019 | 6b79a074649a8cf356a5716992d20d7c71d064ce | 4f1b208709d46520c60bbe39275f2ed42adadaec | "2021-03-16T20:42:04Z" | python | "2021-04-16T14:25:16Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,671 | ["frontend/src/scenes/dashboard/DashboardItems.scss", "frontend/src/scenes/dashboard/DashboardItems.tsx"] | Too much dancing (Feedback) | ## Is your feature request related to a problem?
The dance of the dashboards doesn't really feel great to me:
https://user-images.githubusercontent.com/38760734/111346692-609b8580-8676-11eb-956f-55392d05c64c.mov
It's too much movement and it takes up a lot of the screen (so essentially the whole screen feels like it's moving)
## Describe the solution you'd like
Less dancing.
## Describe alternatives you've considered
Keep 'em dancing.
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/3671 | https://github.com/PostHog/posthog/pull/3824 | 6b09a7cc6ab3eba464528456d62f104c6f2e4cb5 | 2143e5fe7acc8fa2378a1ab73bba0b47097c1256 | "2021-03-16T16:42:19Z" | python | "2021-04-09T19:03:19Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,606 | ["frontend/src/layout/navigation/Navigation.scss"] | Fix main nav bar scroll on Windows/Linux | ## Bug description
The main nav bar gets added a scroll bar which looks terrible on Windows & Linux. This also causes some jumpiness (nav bar appears to be resized) when scrolling.
## Expected behavior
Nav bar should behave the same as in macOS.
## How to reproduce
1. Open PostHog on Windows o Linux.
## Environment
- [X] PostHog Cloud
- [X] self-hosted PostHog, version/commit: _please provide_
## Additional context
Also reported by a user via email.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3606 | https://github.com/PostHog/posthog/pull/3989 | a4388159978416c2dd92c93e0a75460e06a5b739 | 0874d1708845c8ee844584e4ee4343d2262d8705 | "2021-03-09T15:07:39Z" | python | "2021-04-15T13:21:23Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,554 | ["frontend/src/lib/components/PropertiesTable.tsx", "frontend/src/lib/utils/stringWithWBR.tsx"] | It looks like not all text of a long event attribute is being displayed in the UI in the events properties screen | ## Bug description
It looks like not all text of a long event attribute is being displayed in the UI in the events properties screen
If i send an event like this
```
import posthog
from datetime import datetime
posthog.api_key = '<yourkey>'
posthog.host = '<your posthog>'
posthog.debug = True
# send an event
posthog.capture(
distinct_id='andy-laptop',
event='dev',
timestamp=datetime.now(),
properties={
'$current_url': 'dev',
'$pathname': 'dev',
'$host': 'dev',
'$ip': '127.0.0.1',
'host_collector_modules': '/proc/pressure|alarms||/proc/diskstats|/proc/softirqs|/proc/uptime|systemd|/proc/net/sctp/snmp|/proc/meminfo|||/proc/net/dev|/proc/net/stat/nf_conntrack|/proc/loadavg|ipc|/proc/net/sockstat/this_will_not_be_visible_in_the_ui'
}
)
```
In the UI i see:
So it seems like i cant see the `this_will_not_be_visible_in_the_ui` part of the string - looks like it has been truncated at about 190 characters.
## Expected behavior
It would be best to just wrap and display all the string text, or at least up to some much higher limit.
## How to reproduce
1. Send an event like above.
2. Go to events to look at the "host_collector_modules" attribute of the event you sent.
## Environment
- [ ] PostHog Cloud
- [X ] self-hosted PostHog, version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3554 | https://github.com/PostHog/posthog/pull/3578 | 2477ce940de5b733134fa3c591ef74125eaacaea | a8c2bd0cb14ebfe437f27d276de83dbc8775a39e | "2021-03-02T13:20:37Z" | python | "2021-03-04T15:12:24Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,526 | ["frontend/src/lib/utils.tsx"] | Copy button for code doesn't work on onboarding flow | ## Bug description
Copy button doesn't work for code in the onboarding flow
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3526 | https://github.com/PostHog/posthog/pull/3528 | 5bcb7eba368497de414842dbb471e50082ac1867 | 38331e696fc815cd832026d94588322af1bdf142 | "2021-03-01T16:14:02Z" | python | "2021-03-01T16:30:45Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,520 | ["posthog/api/test/test_dashboard.py", "posthog/models/dashboard_item.py"] | Dashboard shows wrong date when using overall | ## Bug description
When using the overall date filter on dashboards, after refreshing the dashboarditem will still show old data
## Expected behavior
Should show data that matches the overall filter
## How to reproduce
1. Add item to dashboard
2. Filter entire dashboard on date
3. refresh date
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3520 | https://github.com/PostHog/posthog/pull/3533 | bb6d4b43582561016489f15c648f4d87311394f9 | 5501d2c5597ef2e37f010aae209d743cd0b87924 | "2021-03-01T16:00:14Z" | python | "2021-03-02T11:34:02Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,410 | ["frontend/src/scenes/insights/ActionFilter/ActionFilter.js"] | Improve UX of reordering funnel steps | ## Is your feature request related to a problem?
You can already reorder funnel steps, but it isn't terribly obvious how.
## Describe the solution you'd like
Couple of options:
1. Make the bars to drag-drop more prominent
2. Add a drop shadow, allow dragging and dropping the whole div containing the step
## Describe alternatives you've considered
## Additional context
cc @EDsCODE
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/3410 | https://github.com/PostHog/posthog/pull/3412 | b25a72d0cfdab4772e6a4ecd4bfd669c9c1e77a6 | e50980c06a590edd4fb712ff367205e29005daef | "2021-02-19T15:52:11Z" | python | "2021-02-19T21:20:54Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,386 | ["frontend/src/lib/components/PropertiesTable.tsx", "frontend/src/scenes/events/EventsTable.js"] | <IconText /> tooltip does not trigger | ## Bug description
In the properties table you can hover over property types to see a textual representation of that.
However, for type string hover does nothing
## Expected behavior
Tooltip is shown
## Environment
All
## Additional context
I think this is caused by using custom icons here, as antd icons show properly. cc @paolodamico
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3386 | https://github.com/PostHog/posthog/pull/3404 | 279ab4dd8a1f2514da25bd677429d7acabe1cce8 | cb3127ea3b36f95474b003d48514dc88200ec5e9 | "2021-02-18T16:22:46Z" | python | "2021-02-19T11:41:30Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,384 | ["frontend/src/lib/components/SelectBox.scss", "frontend/src/lib/components/SelectDownIcon.tsx", "frontend/src/scenes/sessions/Sessions.scss", "frontend/src/scenes/sessions/filters/EditFiltersPanel.tsx", "frontend/src/scenes/sessions/filters/SearchAllBox.tsx"] | Slightly confusing UX for session filters | ## Bug description
<img width="1470" alt="Screenshot 2021-02-18 at 15 38 23" src="https://user-images.githubusercontent.com/47497682/108381121-6a5cd500-71ff-11eb-84c2-de4aaa74dce7.png">
My very first reaction on using this was I found the 'filter sessions by users, actions, events, ...' bar confusing, because it isn't a dropdown and looks like a text search (obviously it's a text search _within_ the dropdown)
## Expected behavior
* An icon on the right of the filter bar to indicate it's a dropdown
* The filter bar to be narrower so it feels more like a dropdown than a text search
ie so it's consistent with our insights filtering, which is what I was looking for as a first reaction:
<img width="157" alt="Screenshot 2021-02-18 at 15 40 38" src="https://user-images.githubusercontent.com/47497682/108381372-a7c16280-71ff-11eb-80ed-2594fe38098a.png">
| https://github.com/PostHog/posthog/issues/3384 | https://github.com/PostHog/posthog/pull/4151 | c257ecdef83985ceed41e625b1a90098ad175389 | 1564ed62609aa717c7cae3f13e05067a0beb65a1 | "2021-02-18T15:43:10Z" | python | "2021-04-28T23:41:44Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 6,889 | ["ee/kafka_client/client.py", "ee/kafka_client/test/test_client.py", "plugin-server/src/config/config.ts", "plugin-server/src/types.ts", "plugin-server/src/utils/db/hub.ts", "posthog/settings/data_stores.py"] | Support Kafka SCRAM auth | https://github.com/PostHog/posthog/pull/3280 | https://github.com/PostHog/posthog/issues/6889 | https://github.com/PostHog/posthog/pull/9348 | 489dbb3c62411fd26f5d319561847ed5acb2c306 | 301c08b34dfdfce6704df2b2df7f579d26f39c05 | "2021-02-18T14:18:41Z" | python | "2022-04-21T18:14:47Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,213 | ["yarn.lock"] | Feature Flag Values - maybe? | ## Is your feature request related to a problem?
I was thinking about a way to test out a change of a value (let's say some weight input for an algorithm) only for specific users and feature flags seem perfect since they can be configured to split traffic as well as only apply to a sub-group of users.
## Describe the solution you'd like
A way to set values for feature flags. There are a couple of questions I'm unsure about:
- should there be a default value?
- should the default be defined in the code when requesting the flag or should it be defined in the dashboard? (What about connection problems, posthog unavailable?)
- since we have split traffic or filter on user, how should different values be handled?
- is it be possible to define multiple values for one key and set the split/filter between them
- how should the UI look like if so?
## Describe alternatives you've considered
Multiple config endpoints coupled with a feature flag(s) - no granular changes possible since all adjustments require a copy of the whole config.
Maybe this is possible to implement as a plug-in? If so should it become part of core? If not is it worth implementing? | https://github.com/PostHog/posthog/issues/3213 | https://github.com/PostHog/posthog/pull/10440 | 87c948457eb3a9e2f0f307a82e625740dacf1db3 | 93cf6dacac02938ebf034275f7ecd17d19271e48 | "2021-02-05T10:33:44Z" | python | "2022-07-01T12:35:47Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,196 | ["frontend/src/layout/navigation/Navigation.scss", "frontend/src/vars.scss"] | Mobile Version Menu offset too small? | ## Bug description
I think the offset on mobile is still set to the narrow icon only menu pre-update. Clicking on the menu does not appear to work either.
## Expected behavior
The main view is shifted further to the right and clicks/taps work.
## How to reproduce
1. Open Page on mobile (narrow display?)
## Environment
- [X] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: _please provide_
## Additional context
Version: iOS 14 (Edge Browser)
#### *Thank you* for your bug report – we love squashing them! | https://github.com/PostHog/posthog/issues/3196 | https://github.com/PostHog/posthog/pull/3198 | 4c98e78c0f29c3d4123be386a4808ae710e2ee9b | eea29cc01cedc35c5b8bd2cbed2e8458b53e045c | "2021-02-04T13:24:29Z" | python | "2021-02-04T14:28:58Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,191 | [".ts-strict-blacklist", "ee/clickhouse/models/property.py", "frontend/src/lib/components/PropertyFilters/OperatorValueSelect.tsx", "frontend/src/lib/components/PropertyFilters/PropertyValue.js", "frontend/src/lib/utils.tsx", "posthog/models/filters/test/test_filter.py", "posthog/models/property.py", "posthog/utils.py"] | Filtering events by invalid regexp fails with a 500 | ## Bug description
The following filter fails with a 500 internal error.
## Expected behavior
Error is shown to user about invalid regular expression.
Note no errors shown on the page as well.
## How to reproduce
1. Go to events
2. Add filter "Current URL matches regular expression ?*"
3. See infinite loading screen / error
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog, version/commit: _please provide_
## Additional context
Note this can also happen when filtering by events.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3191 | https://github.com/PostHog/posthog/pull/3248 | 591e095d08a183e9446264cc42c83acd415561ac | 95630f7a6bc434a1de6649423893be5505481ef4 | "2021-02-04T10:09:39Z" | python | "2021-02-11T19:53:58Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,189 | ["frontend/src/scenes/persons/PersonV2.tsx", "frontend/src/scenes/persons/personsLogic.ts"] | Updating numerical properties via the UI changes type to string | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
When updating the numerical properties of a user on the PostHog UI, they become strings once saved.
## Expected behavior
If the prop was a number, we should try to convert it to a number upon change, if that fails, we can default to string.
## How to reproduce
1. Go to a person page
2. Update a numerical prop
3. Watch it become a string
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3189 | https://github.com/PostHog/posthog/pull/3202 | 62ded053e48296ff38d6ff8d2d196a30dd2a4871 | bc625ea18d1f83770c1809e971a7658e1a1a79ad | "2021-02-04T09:23:27Z" | python | "2021-02-05T09:01:54Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,148 | ["frontend/src/layout/navigation/TopNavigation.tsx", "frontend/src/lib/utils/eventUsageLogic.ts", "frontend/src/scenes/UpgradeModal.tsx", "frontend/src/scenes/sceneLogic.ts"] | Explain benefits of the paid feature in the upgrade modal | ## Is your feature request related to a problem?
Currently the upgrade modal says what the feature is, but it doesn't explain how beneficial it is (e.g. that multiple projects allow you to track multiple product within one organization).
## Describe the solution you'd like
Make it possible to display benefits in some way in the upgrade modal.
## Additional context
Talked with a user who was confused by the upgrade modal due to this.
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/3148 | https://github.com/PostHog/posthog/pull/3619 | 75fb02933c0dc79ae707a216c2199f4ecbefc388 | f97d40207bd2eb19c7b39a46f764067bf5e69b8b | "2021-02-01T15:53:34Z" | python | "2021-03-23T21:16:54Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,135 | [".github/workflows/posthog-foss.yml", "frontend/src/scenes/insights/Insights.js"] | Chart extends below the fold | ## Bug description
Chart height seems unnecessarily tall.
## Expected behavior
The entire graph should ideally load above the fold on a 13" monitor.
Screenshot was taken on my 13" MacBook Pro at the highest resolution (`1680 x 1050`)
## How to reproduce
1. Use a 13" computer with reasonably high resolution
2. Load a trend chart
3. Scroll
## Environment
Playground
| https://github.com/PostHog/posthog/issues/3135 | https://github.com/PostHog/posthog/pull/3142 | 427e4fac6edf556635039fa41016c24181561595 | 200b80dd0364802a61599061e98fbec6c7ac39eb | "2021-01-29T14:46:52Z" | python | "2021-02-01T10:22:55Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,132 | ["frontend/src/scenes/retention/RetentionTable.tsx"] | Hide PII in Shared Dashboards | ## Is your feature request related to a problem?
*Please describe.*
When I share a dashboard clicking on a data point gives me the list of users just like in-app. Problem is, if I'm sharing this outside of PostHog, I most likely want to display aggregate data without PII.
## Describe the solution you'd like
Disallow data point user loading on shared dashboard links.
## Describe alternatives you've considered
Leave as is
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/3132 | https://github.com/PostHog/posthog/pull/3162 | 0624471b4aa3c7461ab51aead3caa4c8ebae12b0 | a1cb32e0d051706f80fd4d60e938e40ff14d55e9 | "2021-01-29T14:14:13Z" | python | "2021-02-02T17:11:14Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,081 | ["ee/clickhouse/queries/clickhouse_retention.py", "ee/clickhouse/sql/retention/people_in_period.py", "ee/clickhouse/sql/retention/retention.py", "frontend/src/scenes/retention/RetentionTable.tsx", "frontend/src/scenes/retention/types.ts", "posthog/queries/retention.py", "posthog/queries/test/test_retention.py"] | Retention trends graph people | ## Bug description
*Please describe.*
- some datapoints show 0 but people will appear in modal
*If this affects the front-end, screenshots would be of great help.*
## Expected behavior
- amount of people and datapoint should be the same
## How to reproduce
1. demo data clickhouse instance
2. go to retention trends for a day with some people
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3081 | https://github.com/PostHog/posthog/pull/3108 | c1518e8b97a4efd3276c2b263407c4fa842ac214 | 1dbd3df937fe3481f45dddc3bacdf1072ac7fa99 | "2021-01-25T21:08:44Z" | python | "2021-02-08T15:28:38Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,071 | ["frontend/src/scenes/retention/RetentionTable.tsx"] | Load More People under retention list of users doesn't work | ## How to reproduce
1. Go to our [internal retention dashboard](https://app.posthog.com/dashboard/501)
2. Scroll to bottom
3.Click Load More People
4. Error in console:
<img width="297" alt="Screenshot 2021-01-25 at 11 53 57" src="https://user-images.githubusercontent.com/47497682/105702654-026ae580-5f04-11eb-9a81-3ecafc35cfe6.png">
Either there are no more people in which case the button shouldn't appear, or there are more people and there's a problem retrieving them.
## Environment
- [X] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: _please provide_
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3071 | https://github.com/PostHog/posthog/pull/3075 | da92f0bbac846b43e5566b24f0f243849c359675 | 80235818450f8e0f19e49dfb47c439c20f9c34cb | "2021-01-25T11:54:42Z" | python | "2021-01-25T23:23:41Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,020 | ["frontend/src/scenes/App.tsx"] | Page is jumpy on first load (new nav) | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
Similar to what we had with the website where the page loads in a jumpy manner.
Sider loads late and pushes the whole rest of the page to the right.
## Expected behavior
Load without jumpiness
## How to reproduce
1.
2.
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3020 | https://github.com/PostHog/posthog/pull/3246 | 1dac0ad699bf7426f15039eadafc11c7f78dfbdd | 3311b0da5a0a3a72f9070ff9bc7a602890bf9ccd | "2021-01-20T18:00:28Z" | python | "2021-02-10T06:45:28Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,019 | ["frontend/src/scenes/paths/Paths.js"] | Paths panel background color doesn't fully update | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
<img width="669" alt="Screenshot 2021-01-20 at 14 56 26" src="https://user-images.githubusercontent.com/38760734/105215229-c6183d80-5b2f-11eb-949d-362c7f2b387e.png">
## Expected behavior
The entire background should be the same color.
## How to reproduce
1.
2.
3.
## Environment
- [x] PostHog Cloud
- [x] self-hosted PostHog, version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/3019 | https://github.com/PostHog/posthog/pull/3089 | 62a95fad62f6498fd25a0c0d6fbf97a7d9d9ec10 | 7dc40f2c37d8c3cbd90688c058040968214bc128 | "2021-01-20T17:57:34Z" | python | "2021-01-27T14:56:19Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 3,017 | ["frontend/src/scenes/paths/pathsLogic.js", "frontend/src/scenes/retention/retentionTableLogic.ts"] | Retention panel not refreshing after click | ## Bug description
*Please describe.*
In [this dashboard](https://app.posthog.com/dashboard/1655), related to the two retention tables in there, I've just clicked refresh multiple times yet the panel still won't refresh.
## Expected behavior
Refresh the panel
## How to reproduce
1. Click refresh on a retention table panel
2.
3.
## Environment
- [X] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
Context on [description update](https://posthog.slack.com/archives/C017WDX3BFZ/p1611170613022300)
| https://github.com/PostHog/posthog/issues/3017 | https://github.com/PostHog/posthog/pull/3039 | 1dbbb46f82862f1b6badd5bf4f9d162bd22d24b0 | 18bb25f264a4d7e3993bd752899548a835210807 | "2021-01-20T17:54:22Z" | python | "2021-01-26T12:25:43Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,983 | ["cypress/integration/trends.js", "frontend/src/scenes/insights/Insights.tsx"] | Show Cohort name instead of number on table views | ## Is your feature request related to a problem?
*Please describe.*
I have no idea what these cohort numbers mean when looking at a table.
## Describe the solution you'd like
Use cohort name instead of number on tables (with a cut-off length ofc). This could be instead of or perhaps even in addition to the cohort number.
<img width="866" alt="Screenshot 2021-01-18 at 13 19 26" src="https://user-images.githubusercontent.com/38760734/104940086-050f8d00-5990-11eb-8b74-624e17a0e42a.png">
## Describe alternatives you've considered
Leave as is.
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/2983 | https://github.com/PostHog/posthog/pull/4706 | 3c691f4f5c17b0abbc413e0f7438072f581e27d7 | 8e3017260034987a6e451ac106f6b798f4a5c949 | "2021-01-18T16:21:14Z" | python | "2021-06-21T21:21:00Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,951 | ["frontend/src/layout/navigation/navigationLogic.ts", "frontend/src/scenes/PreflightCheck/logic.ts", "frontend/src/scenes/instance/SystemStatus/index.scss", "frontend/src/scenes/instance/SystemStatus/index.tsx", "frontend/src/types.ts", "posthog/api/test/test_preflight.py", "posthog/views.py"] | Show warning if SITE_ENV is incorrect | ## Bug description
The SITE_ENV variable, which is quite useful for PostHog to function properly, is not mentioned in any of the deployment guides and only alluded to in the [Configuring Email](https://posthog.com/docs/configuring-posthog/email) page.
Apparently upgrading from one version of posthog to another broke some links in invite e-mails. I'm not sure, but I assume the e-mail sending code went into an async task, and as of such the URL couldn't be taken from `request` anymore, but reverted to `SITE_URL` that was unset. The e-mail config docs say to set this variable, but it might be easy to skip. Not sure.
## Expected behavior
I'd expect the site to give me a warning if I'm visiting `https://posthog.mysite.com/` while the `SITE_URL` variable is set to `http://localhost:8000/` or even `https://posthog.othersite.com/`.
In an ideal world, I would see a warning like "You're browsing posthog from https://posthog.newsite.com/ yet your SITE_URL variable is set to https://posthog.oldurl.com/. Would you like to update it?" and a button to update it directly. Alternatively it would send me to a page on the docs that would describe the situation.
## How to reproduce
1. Install PostHog.
2. Either use a webhook or setup e-mail and invite an user (but forget to update SITE_URL)
3. Be confused as to why the link doesn't work.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: _please provide_
## Additional context
Was raised in the users' slack.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2951 | https://github.com/PostHog/posthog/pull/4172 | 5a6c92cd713ce7103f80c5c902af33961c658d61 | 3de5252fa636295b6d4975bedc007f5be73728a6 | "2021-01-14T19:27:54Z" | python | "2021-04-30T00:28:49Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,942 | ["frontend/src/scenes/insights/LineGraph.js"] | Order tooltip by volume | ## Is your feature request related to a problem?
When I have a chart with multiple lines, I want to know the exact number when I hover over. At the moment we show the tooltip like this:
However this is the wrong way round, so I have to flip those numbers in my head to interpret the graph
## Describe the solution you'd like
Order the items in the tooltip from largest to smallest number.
## Describe alternatives you've considered
Do the flipping/ordering in my head
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/2942 | https://github.com/PostHog/posthog/pull/2960 | 7103c37a7bdb8e838e33ddc377c5b454a606fe75 | 7b74845cb7ca96b0e7aafaf2307af4143985397f | "2021-01-14T10:41:47Z" | python | "2021-01-16T09:06:29Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,940 | ["posthog/plugins/test/mock.py", "posthog/plugins/test/plugin_archives.py", "posthog/plugins/test/test_utils.py", "posthog/plugins/utils.py"] | GitLab Plugins | ## Is your feature request related to a problem?
You can currently install plugins from Github and NPM sources, but not GitLab
## Describe the solution you'd like
Copy a GitLab URL to install a plugin
## Describe alternatives you've considered
Using the plugin source editor.
## Additional context
Came from a conversation in the Users' slack
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/2940 | https://github.com/PostHog/posthog/pull/2970 | 6daaae8cfdf08a3a352e78697d1a792cc3b809e2 | 45811dd9e650d7ff161de5c7f5aa1a99573452f6 | "2021-01-14T10:10:40Z" | python | "2021-01-19T10:07:41Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,889 | ["plugins/package.json", "plugins/yarn.lock"] | Plugin server crashed: Cannot find module './server' | ## Bug description
Hey Posthog team,
when trying to run Posthog locally using the normal `docker compose up` command I always run into the following error message on the `web` service:
```bash
web_1 | [1/4] Resolving packages...
web_1 | success Already up-to-date.
web_1 | Done in 0.48s.
web_1 | yarn run v1.22.10
web_1 | $ posthog-plugin-server
web_1 | internal/modules/cjs/loader.js:883
web_1 | throw err;
web_1 | ^
web_1 |
web_1 | Error: Cannot find module './server'
web_1 | Require stack:
web_1 | - /code/plugins/node_modules/posthog-plugin-server/dist/src/index.js
web_1 | - /code/plugins/node_modules/posthog-plugin-server/bin/posthog-plugin-server
web_1 | at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
web_1 | at Function.Module._load (internal/modules/cjs/loader.js:725:27)
web_1 | at Module.require (internal/modules/cjs/loader.js:952:19)
web_1 | at require (internal/modules/cjs/helpers.js:88:18)
web_1 | at Object.<anonymous> (/code/plugins/node_modules/posthog-plugin-server/dist/src/index.js:23:18)
web_1 | at Module._compile (internal/modules/cjs/loader.js:1063:30)
web_1 | at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
web_1 | at Module.load (internal/modules/cjs/loader.js:928:32)
web_1 | at Function.Module._load (internal/modules/cjs/loader.js:769:14)
web_1 | at Module.require (internal/modules/cjs/loader.js:952:19) {
web_1 | code: 'MODULE_NOT_FOUND',
web_1 | requireStack: [
web_1 | '/code/plugins/node_modules/posthog-plugin-server/dist/src/index.js',
web_1 | '/code/plugins/node_modules/posthog-plugin-server/bin/posthog-plugin-server'
web_1 | ]
web_1 | }
web_1 | error Command failed with exit code 1.
web_1 | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
web_1 |
web_1 | 🔴 Plugin server crashed!
web_1 | ⌛️ Waiting 2 seconds before restarting!
```
## Expected behavior
I would expect the service to start normally
## How to reproduce
1. Pull the latest master branch (`9f9516ab8e6097dc088a92c7370ba7d46ce70a1a`)
2. Adjust the `docker-compose.yml`: Add the `SECRET_KEY` env variable
3. Run `docker-compose up`
## Environment
- [ ] PostHog Cloud
- [x] self-hosted PostHog, version/commit:
- Master branch: `9f9516ab8e6097dc088a92c7370ba7d46ce70a1a`
- Image: latest ( `DIGEST:sha256:8ba18719477cf5657b8ef40a13343151db4ee4964fbf6ec6a554b8fb15c5246b`)
## Additional context
I already tried to have a look at the code but could not figure it out. I hope it is not related to my docker setup being corrupt since it worked yesterday morning. But maybe you can also help me pointing that out.
What I tried additionally:
- Go inside the container and remove `/code/plugins/node_modules` + run `yarn install` in `/code/plugins`
- Run `docker-compose -f docker-compose.dev.yml up` -> here only the `worker` service crashes with the same error as above
Hope you can help me out on that since we really want to test out Posthog for our product analytics purposes. It sounds like a promising solution to our problems :)
### UPDATE
**Changing the docker image in `docker-compose.yml` to `posthog/posthog:latest-release` (which in this case would be `1.19.0` I guess) -> WORKED without error**
I still leave the issue open because I guess it might be related to the latest changes to the plugin server | https://github.com/PostHog/posthog/issues/2889 | https://github.com/PostHog/posthog/pull/2897 | 730206b169b4e707f04d6da5811eca7f61ace64e | e3aa8bf31b6386907d507a3d524e23fb2472ca3f | "2021-01-08T07:56:19Z" | python | "2021-01-08T14:13:19Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,863 | ["task-definition.plugins.json", "task-definition.worker.json"] | Invite links are being sent from root@localhost on app. | ## Bug description
Try inviting someone on app, the email will come from root@localhost
## Expected behavior
Should come from [email protected]
## How to reproduce
1.
2.
3.
## Environment
- [ ] PostHog Cloud
- [ ] self-hosted PostHog, version/commit: _please provide_
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2863 | https://github.com/PostHog/posthog/pull/2869 | 027708c345ea246d68cf0299e4c6271ba1f278d0 | 1ef890fbf2bceae96da6d136c1f47ae68026d7a8 | "2021-01-06T11:04:45Z" | python | "2021-01-06T17:17:45Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,824 | [".github/workflows/posthog-foss.yml"] | PostHog FOSS could just have an MIT license (ie exclude license from mirror) | We currently mirror everything except proprietary code into PostHog FOSS
However, the license *ideally* would just be MIT here as there's no need to complicate with talk about ee as that folder doesn't exist. | https://github.com/PostHog/posthog/issues/2824 | https://github.com/PostHog/posthog/pull/3146 | 04c949aeeee218bdf923b73b71c0ab87e177fe33 | 95900d4fce0758ef0372081103b6e5cfd422094b | "2020-12-18T12:30:58Z" | python | "2021-02-01T14:26:00Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,794 | ["ee/clickhouse/queries/clickhouse_retention.py", "ee/clickhouse/sql/retention/people_in_period.py", "ee/clickhouse/sql/retention/retention.py", "frontend/src/scenes/retention/RetentionTable.tsx", "frontend/src/scenes/retention/types.ts", "posthog/queries/retention.py", "posthog/queries/test/test_retention.py"] | Bug with CH persons double click on retention table | ## Bug description
We have an issue in which the table of users for each cohort does not contain the same number of users as the table reports.
### Example
([Source](https://app.posthog.com/insights?startEntity=%7B%22actions%22%3A%5B%5D%2C%22events%22%3A%5B%7B%22id%22%3A%22user%20signed%20up%22%2C%22type%22%3A%22events%22%2C%22order%22%3A0%2C%22name%22%3A%22user%20signed%20up%22%7D%5D%2C%22new_entity%22%3A%5B%5D%7D&returningEntity=%7B%22events%22%3A%5B%7B%22id%22%3A%22%24pageview%22%2C%22name%22%3A%22%24pageview%22%2C%22type%22%3A%22events%22%7D%5D%7D&retentionType=retention_first_time&date_to=2020-04-05T12%3A59%3A36.001Z&period=w&display=ActionsTable&properties=%5B%7B%22key%22%3A%22id%22%2C%22value%22%3A71%2C%22type%22%3A%22cohort%22%7D%2C%7B%22key%22%3A%22%24current_url%22%2C%22value%22%3A%22www.posthog.com%22%2C%22operator%22%3A%22not_icontains%22%2C%22type%22%3A%22event%22%7D%2C%7B%22key%22%3A%22%24current_url%22%2C%22value%22%3A%22https%3A%2F%2Fposthog.com%22%2C%22operator%22%3A%22not_icontains%22%2C%22type%22%3A%22event%22%7D%2C%7B%22key%22%3A%22%24current_url%22%2C%22value%22%3A%22localhost%22%2C%22operator%22%3A%22not_icontains%22%2C%22type%22%3A%22event%22%7D%2C%7B%22key%22%3A%22%24current_url%22%2C%22value%22%3A%22127.0.0.1%22%2C%22operator%22%3A%22not_icontains%22%2C%22type%22%3A%22event%22%7D%2C%7B%22key%22%3A%22%24current_url%22%2C%22value%22%3A%220.0.0.1%22%2C%22operator%22%3A%22not_icontains%22%2C%22type%22%3A%22event%22%7D%5D&insight=RETENTION))
**Table shows 6 users in cohort:**
<img width="222" alt="" src="https://user-images.githubusercontent.com/5864173/102359528-867d9500-3f76-11eb-8134-50d0adcbd5b8.png">
**Persons list shows a lot more than 6 users in cohort:**
<img width="150" alt="" src="https://user-images.githubusercontent.com/5864173/102359599-9a28fb80-3f76-11eb-9cb8-61b37ddd4d95.png">
## Expected behavior
The persons list and the retention table should match.
## How to reproduce
See description above.
## Environment
Cloud, Clickhouse.
## Additional context
Currently blocking internal personas analysis.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2794 | https://github.com/PostHog/posthog/pull/3108 | c1518e8b97a4efd3276c2b263407c4fa842ac214 | 1dbd3df937fe3481f45dddc3bacdf1072ac7fa99 | "2020-12-16T14:15:01Z" | python | "2021-02-08T15:28:38Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,769 | ["frontend/src/lib/components/ChartFilter/ChartFilter.js"] | Retention as a bar chart doesn't work | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
Selecting 'bar' in retention does nothing.
<img width="1220" alt="Screenshot 2020-12-15 at 09 50 15" src="https://user-images.githubusercontent.com/38760734/102217208-034b3900-3ebb-11eb-8575-1c6a5da67f6a.png">
## Expected behavior
Show a bar chart
## How to reproduce
1. Switch retention to bar
2.
3.
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2769 | https://github.com/PostHog/posthog/pull/2770 | fe8b5e0dd76172a4b85b388d6227e26099543474 | bf506e3d0b8038c164b70842385040d5037f641e | "2020-12-15T12:51:14Z" | python | "2020-12-15T13:15:56Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,752 | ["frontend/src/scenes/persons/personsLogic.ts"] | Pagination in 'identified' tab in persons removes 'identified' filter | ## Bug description
* Go to /persons
* Click 'identified'
* Scroll to bottom to look at more identified users
* Click pagination
* You now see non-identified and identified users
## Expected behavior
* On clicking pagination to see the second page of identified users
## Environment
PostHog Cloud | https://github.com/PostHog/posthog/issues/2752 | https://github.com/PostHog/posthog/pull/2756 | f3e4cad700da10b21e6167a8c2139e0f95708eee | d9f9545b186ed00aeb532a23c7c754c8dd97c8e6 | "2020-12-14T16:05:58Z" | python | "2020-12-14T21:48:02Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,705 | ["posthog/api/capture.py", "posthog/api/decide.py", "posthog/api/test/test_capture.py", "posthog/api/test/test_decide.py", "posthog/api/test/test_user.py", "posthog/exceptions.py", "posthog/settings.py", "posthog/test/base.py", "posthog/utils.py"] | Handle incorrectly formatted payloads on /capture | ## Is your feature request related to a problem?
When sending incorrectly formatted payloads (e.g. a text-based string with a `gzip` compression header), the app will fail with a cryptic 500 error and register an unhandled exception.
## Describe the solution you'd like
The app should return a 400 bad request error, with details on why the request failed (i.e. it is incorrectly formatted or the content does not match the compression specified). In addition, this shouldn't be treated as an unhandled exception as it's a client error.
## Describe alternatives you've considered
Keep returning a cryptic 500 error.
## Additional context
Relevant context on #2701
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/2705 | https://github.com/PostHog/posthog/pull/3939 | 50e845e79e4175aaca623ea8315b0d6a2099d9ee | c479fa9e3c3fcc2a1aa78c6a7b69cfe00350d9c2 | "2020-12-08T17:01:13Z" | python | "2021-04-20T16:30:50Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,688 | [".gitattributes", ".github/workflows/posthog-foss.yml", ".gitignore"] | dont run Github Actions run on clone repos | ## Is your feature request related to a problem?
Not a big one, but my clone attempts to run Github Actions that are not appropriate for my repo - https://github.com/enterprise-oss/posthog/runs/1511576051
## Describe the solution you'd like
A way to get the latest source code via git that doesn't include a `.github` dir.
I'd suggest renaming the `.github` dir to `sample.github` or removing it altogether in the FOSS repo so that folks who clone and push to github don't run these actions automatically. in a meta sense, the existing github action that updates the foss repo could pretty easily remove the `.github` dir as well as `ee`
## Describe alternatives you've considered
Removing the github dir myself which I fear will lead to merge conflicts
## Additional context
https://posthogusers.slack.com/archives/CT7HXDEG3/p1607355002184800
| https://github.com/PostHog/posthog/issues/2688 | https://github.com/PostHog/posthog/pull/3141 | ff3d2d7aae25340b60918ffff074b0f0df8f1153 | 427e4fac6edf556635039fa41016c24181561595 | "2020-12-07T15:54:29Z" | python | "2021-02-01T08:25:40Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,684 | ["ee/clickhouse/process_event.py", "posthog/tasks/process_event.py", "posthog/tasks/test/test_process_event.py"] | Support $set_once | posthog-js supports person.set_once but our backend doesn't. Make sure we can pass through `$set_once` on an `$identify` call, and only set the properties within if the properties aren't already set on the user. | https://github.com/PostHog/posthog/issues/2684 | https://github.com/PostHog/posthog/pull/2972 | e6b7ac88caa91a037b4a3c459c8475aa885c42b9 | 8d65088c5dfdf66149628d31be702a2d539e6345 | "2020-12-07T13:49:52Z" | python | "2021-01-18T15:02:58Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,679 | ["ee/clickhouse/queries/trends/lifecycle.py", "posthog/queries/test/test_trends.py"] | All time filter doesn't work for lifecycle | ## Bug description
*Please describe.*
- lifecycle is missing all time filter handling
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2679 | https://github.com/PostHog/posthog/pull/2693 | 25d60bf839164b680ea9484a8a1addeb1c442877 | d3735cb15e97932b29566b605619788ccc1f05af | "2020-12-05T04:20:01Z" | python | "2020-12-09T18:31:48Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,650 | ["ee/clickhouse/queries/trends/lifecycle.py", "ee/clickhouse/sql/trends/lifecycle.py", "posthog/queries/lifecycle.py", "posthog/queries/test/test_trends.py"] | [Lifecycle] Interval generates weird results | ## Is your feature request related to a problem?
Compare year to date
With last 90 days [(link)](https://app.posthog.net/insights?display=ActionsBar&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%22total%22%7D%5D&shown_as=Lifecycle&actions=%5B%5D&properties=%5B%7B%22key%22%3A%22%24current_url%22%2C%22value%22%3A%22https%3A%2F%2Fposthog.com%22%2C%22operator%22%3A%22not_icontains%22%2C%22type%22%3A%22event%22%7D%2C%7B%22key%22%3A%22id%22%2C%22value%22%3A71%2C%22type%22%3A%22cohort%22%7D%5D&interval=week&date_from=-90d)
## Describe the solution you'd like
## 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/2650 | https://github.com/PostHog/posthog/pull/2657 | 7166679672dcef18febb1a2dd211a68264d33ad0 | b9d6112058ce70c9d8e16816017dbbb96cc9884d | "2020-12-03T11:26:16Z" | python | "2020-12-04T10:02:52Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,645 | ["requirements-dev.txt", "requirements.in", "requirements.txt"] | New UX doesn't signify the command palette exists | ## Bug description
<img width="1194" alt="Screenshot 2020-12-03 at 10 40 33" src="https://user-images.githubusercontent.com/47497682/100998868-fa21aa00-3553-11eb-9b0b-84621f3c1308.png">
I'm not sure the best way to do this, but no one will use the command palette without it being obvious somewhere so we should either kill it off or promote it and validate it with users. | https://github.com/PostHog/posthog/issues/2645 | https://github.com/PostHog/posthog/pull/19643 | 025069d720b1d0ed130521e5601b5f686f1fad59 | e9b825236f6f4d81c98639fc2016de31f03723a9 | "2020-12-03T10:41:08Z" | python | "2024-01-15T13:17:13Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,640 | ["frontend/src/lib/components/CommandPalette/CommandResults.tsx"] | Command palette scrolling issue | ## Bug description
Using the keyboard arrow keys scrolls the underlying page.
## Expected behavior
Using the arrow keys on the command palette should not scroll the page beneath.
## How to reproduce
1. Open the command palette
2. Open the share feedback command
3. Press the top and bottom arrow keys
## Environment
Cloud
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2640 | https://github.com/PostHog/posthog/pull/2658 | 3eff7abdc5a5b118057f72a841a313e25bbe09d8 | 899b0967d6c295d8ca17120da4f32f448c0fdebe | "2020-12-03T02:59:33Z" | python | "2020-12-04T20:32:39Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,637 | ["cypress/integration/person.js", "frontend/src/lib/components/PropertiesTable.tsx", "frontend/src/scenes/persons/Person.tsx"] | [UX] Allow me to copy property values that are an email or URL easily | Here's my use case. Since I don't have Zapier integration *cough* *cough* yet, I've been using the Slack events to email my users.
These are my steps:
1. Get Slack message
2. Click on the email and open up the Person page.
3. Copy the email address with great difficulty.
4. Open email app and paste it in.
## Describe the solution you'd like
For fields that have a URL or email, it would be nice to have the link below the field in a link format that I can right click and copy or just click it to visit the customer's URL.
## Describe alternatives you've considered
See my steps above. | https://github.com/PostHog/posthog/issues/2637 | https://github.com/PostHog/posthog/pull/5884 | 3f32d1a3cafb91e36dd016ea225660ff4333abba | 693bb7ee4f19cb83f592df8212f0e21ecb59cc69 | "2020-12-02T18:56:05Z" | python | "2021-09-14T16:02:00Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,636 | ["posthog/templates/login.html", "posthog/test/test_urls.py", "posthog/urls.py"] | Does not redirect to desired page when logged out (next query isn't honoured) | ## How to reproduce
1. Log out
2. Open a specific PH link (e.g. https://<PH instance>/person/338)
3. Login
## Expected behavior
I expect it to take me to the page I was intending to go to when I was logged out and not "Insights" page.
## Actual behavior
It takes me to the https://<PH instance>/insights...
## Environment
- PostHog cloud or self-managed? self-hosted
- PostHog version/commit: 1.17.0 | https://github.com/PostHog/posthog/issues/2636 | https://github.com/PostHog/posthog/pull/2757 | bf506e3d0b8038c164b70842385040d5037f641e | 0b01bb694e4d379fd36f526ee9cb7e3af9d9151e | "2020-12-02T18:48:04Z" | python | "2020-12-15T14:25:15Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,632 | ["frontend/src/lib/components/SaveToDashboard/SaveToDashboardModal.js"] | Update dashboard modal is broken on the new UI | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
<img width="893" alt="Screenshot 2020-12-02 at 15 38 54" src="https://user-images.githubusercontent.com/38760734/100900205-81224400-34ba-11eb-8abe-7706dfb2a12b.png">
## Expected behavior
Should be a normal modal like before
## How to reproduce
1. Go to a dashboard
2. Click on a panel
3. Change the data
4. Click update dashboard
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2632 | https://github.com/PostHog/posthog/pull/2673 | 899b0967d6c295d8ca17120da4f32f448c0fdebe | 88dafdd55f0c0e00e7c3c31d0d83a99e2e5c75d4 | "2020-12-02T16:22:35Z" | python | "2020-12-04T21:28:12Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,626 | ["frontend/src/lib/components/icons.tsx", "frontend/src/scenes/events/EventDetails.js", "frontend/src/scenes/events/EventsTable.js"] | Allow jumping into insights/trends from event view | ## Is your feature request related to a problem?
I'm analyzing a new event. After seeing it pop up in events view, it would be great to jump straight to insights view with the event selected.
## Describe the solution you'd like
Add a button 'analyze this event' on the right of "create action from this event"
## Describe alternatives you've considered
Manually going to 'insights' and re-selecting the event
## Additional context
Came up during #2560
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/2626 | https://github.com/PostHog/posthog/pull/2748 | 734573fbf7d318c421f232204288e6591c5ac034 | 00930e3e328c95d4da2b793b3a29a07540497ade | "2020-12-02T10:53:11Z" | python | "2020-12-13T19:09:22Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,620 | ["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"] | Order metrics shown on tooltip | ## Is your feature request related to a problem?
This tooltip is hard to follow:
## Describe the solution you'd like
Order the tooltip by volume somehow.
One potential ordering - take the last data point, order by that.
## Describe alternatives you've considered
## Additional context
Not sure why versions which are at 0 every datapoint even show up.
Came up during #2560
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/2620 | https://github.com/PostHog/posthog/pull/8046 | b1f304754fa37a2f72fe4b3ad51f8ed6bdf707b7 | 22ea1cf6820748a58b1b521462cf11d17082d8b3 | "2020-12-02T08:54:47Z" | python | "2022-01-18T20:34:46Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,613 | ["dump.rdb", "frontend/src/scenes/actions/actionEditLogic.js"] | Bug with actions with regex URL matching group | ## Bug description
Cannot set regex filter on the URL for an autocapture action matching group (see recording below). The filter by regex property is not saved, and instead it defaults to contains.
## Expected behavior
Filtering with a regex expression should work.
## How to reproduce
See attached recording.
## Environment
Cloud (happens locally too)
## Additional context
Here's the response payload after saving with the regex option
```json
{
"id":2745,
"name":"created action [no toolbar]",
"post_to_slack":false,
"slack_message_format":"",
"steps":[
{
"id":3045,
"event":"$autocapture",
"tag_name":null,
"text":null,
"href":null,
"selector":"button[data-attr=\"save-action-button\"]",
"url":"\\/action$",
"name":null,
"url_matching":null,
"properties":[
]
},
{
"id":3047,
"event":"$autocapture",
"tag_name":null,
"text":null,
"href":null,
"selector":"#action_step > button[type=\"submit\"]",
"url":null,
"name":null,
"url_matching":null,
"properties":[
]
}
],
"created_at":"2020-12-01T22:07:20.271178Z",
"deleted":false,
"count":0,
"is_calculating":false,
"created_by":null
}
```
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2613 | https://github.com/PostHog/posthog/pull/2696 | 4c93afbca63c9c707f5bc8a2f38c609999d3097c | 64f2a57bd2a52fe3d446e649f4e2ece6c8b77b00 | "2020-12-01T22:26:01Z" | python | "2020-12-08T16:55:37Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,596 | ["frontend/src/lib/components/Link.tsx", "frontend/src/lib/components/LinkButton.tsx", "frontend/src/scenes/sessions/SessionsPlay.tsx", "frontend/src/scenes/sessions/SessionsPlayerButton.tsx", "frontend/src/scenes/sessions/SessionsTable.tsx", "frontend/src/scenes/sessions/sessionsPlayLogic.ts", "frontend/src/scenes/sessions/sessionsTableLogic.ts"] | Improved interactivity for sessions (BigFrigginPlayButton) | ## Is your feature request related to a problem?
Closely related to https://github.com/PostHog/posthog/issues/2595
It should be easy to jump from sessions, cohorts or other views to view a session.
## Describe the solution you'd like
Let's add a large "Play sessions" button to sessions page. This would then start the player in the same tab with an automatic overlay at the end of recording to prompt you to see the next recording.
We could add this elsewhere as well (e.g. cohorts, insights when viewing user list) - the button would then redirect to relevant sessions page with the filters set (https://github.com/PostHog/posthog/issues/2595) and start the player automatically.
## Describe alternatives you've considered
## Additional context
Depends partially on https://github.com/PostHog/posthog/issues/2595
Unclear right now whether already watched session recordings should be automatically skipped.
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/2596 | https://github.com/PostHog/posthog/pull/2744 | 5845e3ec8bec99dce048f722475cea555de8ce0d | 3b6a08da82ba414714068326dd5d406398eec5ad | "2020-12-01T11:25:21Z" | python | "2020-12-15T17:02:08Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,587 | ["frontend/src/lib/constants.tsx", "frontend/src/lib/utils/eventUsageLogic.ts", "frontend/src/scenes/dashboard/Dashboard.scss", "frontend/src/scenes/dashboard/Dashboard.tsx", "frontend/src/scenes/dashboard/dashboardLogic.ts", "posthog/api/dashboard.py", "posthog/api/test/test_dashboard.py", "posthog/api/test/test_insight.py", "posthog/models/insight.py"] | Custom filters on dashboards | ## Is your feature request related to a problem?
When setting up dashboards I'd like to filter the stats to a certain page/subdomain.
## Describe the solution you'd like
Allow adding a extra filters for all graphs on a dashboard (e.g. filter by $current_url)
## Describe alternatives you've considered
Updating every graph in dashboard one-by-one and then reverting them back.
## Additional context
Related to https://github.com/PostHog/posthog/issues/780
Datadog has a decent solution for this: https://docs.datadoghq.com/dashboards/template_variables/, which I think we can simplify and use ourselves.
Came up during #2560
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/2587 | https://github.com/PostHog/posthog/pull/9767 | 6f13f07aa1b205440f67086fb283ff7e102e5a49 | 1a15c219529b3d4174eae24df085a4786c24b04d | "2020-12-01T08:58:06Z" | python | "2022-05-18T11:16:02Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,573 | ["posthog/api/test/test_action.py", "posthog/api/test/test_capture.py", "posthog/api/test/test_dashboard.py", "posthog/api/test/test_decide.py", "posthog/api/test/test_element.py", "posthog/api/test/test_event.py", "posthog/settings.py", "requirements.in", "requirements.txt"] | Implement brute force guessing blocking | ## Is your feature request related to a problem?
It's possible to brute-force passwords if you're particularly determined
## Describe the solution you'd like
Install `django-axes`: https://django-axes.readthedocs.io/en/latest/2_installation.html
## 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/2573 | https://github.com/PostHog/posthog/pull/2582 | b8031b7895ba473bb141776f0f58e2a8dff5414c | d924181fce09c4a62340aa35932328221db942d4 | "2020-11-30T19:28:47Z" | python | "2020-12-02T10:01:46Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,569 | ["ee/clickhouse/queries/test/test_trends.py", "ee/clickhouse/queries/trends/breakdown.py"] | Feature flag insights are broken | ## Bug description
Trying to look at insights for feature flags no longer works (see screenshot below).
<img width="1329" alt="" src="https://user-images.githubusercontent.com/5864173/100642031-de24cb00-32fd-11eb-88b4-047c4f82124f.png">
Removing the breakdown works but then you can't see the difference between the binary values.
## Expected behavior
Insights should be shown as before.
## How to reproduce
1. Click on the insights link on any feature flag row.
## Environment
Cloud (Clickhouse).
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2569 | https://github.com/PostHog/posthog/pull/2575 | 5967d0397d5a9f7adf409e9e780135ade141cf56 | 3f5b76cb8c331c2fb4200b6b110bd068a3ddd6ff | "2020-11-30T17:20:08Z" | python | "2020-11-30T20:51:12Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,553 | ["frontend/src/layout/navigation/Navigation.scss"] | sidebar icons in app should do something on hover | ## Is your feature request related to a problem?
We have a lovely new sidebar:
<img width="77" alt="Screenshot 2020-11-27 at 15 55 03" src="https://user-images.githubusercontent.com/47497682/100466555-fcee4c00-30c8-11eb-90be-cbadb159598d.png">
The icons don't do anything on hover, whereas everywhere else in app and in posthog.com we generally apply an effect to signify you can click.
## Describe the solution you'd like
For the colour (or an underline) to appear on hover, consistent with the rest of the app.
## Describe alternatives you've considered
Just use it and put aside the slight UX irritation :)
| https://github.com/PostHog/posthog/issues/2553 | https://github.com/PostHog/posthog/pull/2563 | 73793991a6181f3f8011fafb0ff62c46dbba1174 | 7c24e8760d04a0c611f379ab455946ab677ddea7 | "2020-11-27T15:57:03Z" | python | "2020-11-30T16:06:03Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,545 | ["frontend/src/global.scss", "frontend/src/layout/navigation/MainNavigation.tsx", "frontend/src/layout/navigation/TopNavigation.tsx", "frontend/src/layout/navigation/navigationLogic.ts", "frontend/src/lib/components/BackTo.tsx", "frontend/src/scenes/App.tsx", "frontend/src/scenes/instance/SystemStatus/systemStatusLogic.ts"] | New navigation doesn't include certain pages | ## Bug description
The new navigation is missing a few options:
- Team members
- Invites
- Licenses
- Annotations
Also because settings is a menu item I was confused about organization settings being top right. That page is also blank.
I've rolled back the rollout of this in the mean time and just turned it on for us.
## Expected behavior
## How to reproduce
1.
2.
3.
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2545 | https://github.com/PostHog/posthog/pull/2763 | 0b01bb694e4d379fd36f526ee9cb7e3af9d9151e | 6d69b029e0682174a2df14201407d09bcf539f91 | "2020-11-27T11:50:01Z" | python | "2020-12-15T14:48:14Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,541 | ["frontend/src/global.scss", "frontend/src/layout/navigation/MainNavigation.tsx", "frontend/src/layout/navigation/TopNavigation.tsx", "frontend/src/layout/navigation/navigationLogic.ts", "frontend/src/lib/components/BackTo.tsx", "frontend/src/scenes/App.tsx", "frontend/src/scenes/instance/SystemStatus/systemStatusLogic.ts"] | Error on creating a new account | ## Bug description
I was creating a new account on PostHog cloud in incognito with these credentials:
<img width="304" alt="Screenshot 2020-11-27 at 10 33 58" src="https://user-images.githubusercontent.com/47497682/100439954-14631000-309c-11eb-97af-ee029a66de13.png">
I got this error:
<img width="1476" alt="Screenshot 2020-11-27 at 10 32 45" src="https://user-images.githubusercontent.com/47497682/100439847-f7c6d800-309b-11eb-9fb7-964a51f458f9.png">
## Expected behavior
No error messages on signing up fresh.
| https://github.com/PostHog/posthog/issues/2541 | https://github.com/PostHog/posthog/pull/2763 | 0b01bb694e4d379fd36f526ee9cb7e3af9d9151e | 6d69b029e0682174a2df14201407d09bcf539f91 | "2020-11-27T10:34:34Z" | python | "2020-12-15T14:48:14Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,474 | ["posthog/api/capture.py", "posthog/api/decide.py", "posthog/api/personal_api_key.py", "posthog/api/test/test_capture.py", "posthog/api/test/test_decide.py", "posthog/api/test/test_personal_api_keys.py", "posthog/models/team.py", "posthog/models/user.py"] | Capture and decide endpoints don't work with personal API keys anymore | ## Bug description
Since users can now be part of multiple projects, the `get_team_from_token` function used in capture and decide endpoints cannot work reliably with personal API keys. These endpoints should be e.g. nested under `/api/projects/:project_id` _or_ should accept `project_id` in request body.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2474 | https://github.com/PostHog/posthog/pull/2617 | b9d6112058ce70c9d8e16816017dbbb96cc9884d | 40dbffbb983d33ae3123041271e9ee526ac74205 | "2020-11-23T14:18:26Z" | python | "2020-12-04T13:01:31Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,421 | ["posthog/api/feature_flag.py", "posthog/api/test/test_feature_flag.py"] | Feature Flag cannot recreate with the same key after deleting | ## Bug description
Feature Flag cannot recreate with the same key after deleting
Steps to reproduce:
1. create feature flag with key `bla`
2. delete the feature flag
3. try to create again feature flag with `bla` key
4. alert will popup with This key already exists
## Expected behavior
New feature flag will be added
## Environment
self-hosting
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2421 | https://github.com/PostHog/posthog/pull/2461 | eed10468950e0ef148632972fab5acaf3c8c96d7 | 7affee178e9733f95a97f8f7faa1027d8cbf33ff | "2020-11-17T20:36:21Z" | python | "2020-11-26T10:15:17Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,393 | ["frontend/src/layout/navigation/MainNavigation.tsx", "frontend/src/scenes/events/Events.tsx"] | Navigation broken between events and actions | ## Bug description
- "Actions" won't highlight when clicked the first time
- The title of the page remains "Events"
- The pages open if you click into them from outside any of them, later nothing changes
## Expected behavior
Should work consistently.
## How to reproduce
1. Click events or actions
2. Click the other one
## Environment
Master branch
## Additional context
Might also be wise to fix this before the next release. This seems like a pretty front and center bug.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2393 | https://github.com/PostHog/posthog/pull/2401 | 1ec12f26e707489e77077be029ddb79ceeefd944 | 0725d11979e10cc2da05ba6e98f104d717a295b4 | "2020-11-16T10:57:02Z" | python | "2020-11-17T08:25:25Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,327 | ["frontend/src/scenes/paths/Paths.js", "frontend/src/scenes/paths/pathsLogic.js", "frontend/src/scenes/retention/retentionTableLogic.ts"] | Can't update dashboard (retention and paths) | ## Bug description
*Please describe.*
- if you have multiple retention or paths graphs on a dashboard and you click into the graph to try to update it, you won't be able to
*If this affects the front-end, screenshots would be of great help.*
## Expected behavior
- When you click on the graph and land on insights page you should be able to update the dashboard it came from
## How to reproduce
1. Have multiple retention or paths insights on a dashboard
2. Click the dashboard and then click on one of the items
3. On the insight page it should show "update dashboard" but it won't
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
- this is happening because when implementing the ability to add retention and paths graphs to the dashboard. I wanted to reuse the logic but all the other insights don't reuse the logic as heavily (the logic for trends is scoped to the graph itself and handled differently. same with funnels)
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2327 | https://github.com/PostHog/posthog/pull/2341 | 92b41eeaffe285d0d83686da2f2526981539fd70 | 4f70f02900ae21e538f50b4aefac81f356b97d1d | "2020-11-10T21:21:03Z" | python | "2020-11-12T11:59:10Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,322 | ["frontend/src/scenes/actions/ActionsTable.tsx"] | Add filter for actions that will receive notifications | ## Describe the solution you'd like
- the ability to filter actions that are attached to a hook
## Additional context
- this will allow users to know which actions will trigger notifications in slack
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/2322 | https://github.com/PostHog/posthog/pull/5415 | 617ded5b80cd74e1bc7703f5f612bf56668aa23d | cc499d8fbc1b070ead7010b1c0aee8ae2fd9c399 | "2020-11-10T16:18:33Z" | python | "2021-08-02T21:44:25Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,318 | ["cypress/integration/cohorts.js", "cypress/integration/licenses.js", "cypress/integration/projectSettings.js", "frontend/src/lib/utils.tsx", "frontend/src/scenes/sceneLogic.ts"] | Add titles to different pages | ## Is your feature request related to a problem?
*Please describe.*
When using PostHog with many tabs open, it's hard to know what's on each tab.
## Describe the solution you'd like
Something like this (see browser tabs):
<img width="1166" alt="Screenshot 2020-11-10 at 14 36 35" src="https://user-images.githubusercontent.com/38760734/98687900-29346980-2362-11eb-802e-360bad4556c8.png">
## Describe alternatives you've considered
Guessing what each tab is
## Additional context
Helmet could be the solution here?
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/2318 | https://github.com/PostHog/posthog/pull/2361 | 356bb72a5522dabba46e2537a25a5ca367bb92b6 | 33823e864844755d31e205c8c60eeff77c1fd94f | "2020-11-10T14:36:18Z" | python | "2020-11-13T16:50:23Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,312 | ["frontend/src/scenes/persons/Persons.tsx"] | Cohort Search Bar doesn't work | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
Search bar doesn't work on the Cohort pages (individual cohort)
## Expected behavior
I can search for users in the cohort
## How to reproduce
1. Use the search bar on a Cohort
2.
3.
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2312 | https://github.com/PostHog/posthog/pull/2557 | 6426408c6aab5488a64d260735fc273009f0f551 | 60072edb7b3a37d5e539f33d7512a0745b4bc0d2 | "2020-11-10T12:34:59Z" | python | "2020-11-30T09:54:18Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,306 | ["ee/clickhouse/models/cohort.py", "ee/clickhouse/models/person.py", "ee/clickhouse/models/test/test_cohort.py", "ee/clickhouse/sql/person.py", "posthog/celery.py", "posthog/models/cohort.py", "posthog/models/feature_flag.py", "posthog/tasks/calculate_cohort.py", "posthog/test/test_cohort_model.py", "posthog/test/test_feature_flag.py"] | /decide endpoint can become slow due to feature flags | ## Bug description
Currently, decide endpoint takes 10+ seconds on kea.js.org.
This means that for first-time visitors autocapture nor session recording will be turned on for that long - losing valuable information.
When measuring this yesterday via shell ([slack thread](https://posthog.slack.com/archives/C0113360FFV/p1604951621008400)), the culprit was feature flags cohort checking. In this case, the cohort user was checked against was defined against the following action:
Which currently looks through events of the data for that team.
## Expected behavior
Decide endpoint should use cached/materialized cohort ownership rather than calculating it on the fly.
## How to reproduce
1. Create an action with some selector
2. Create a cohort for has done action at any point
3. Create a feature flag using the cohort.
4. Measure /decide endpoint latency
## Environment
Cloud
## Additional context
cc @EDsCODE who made it not time out by https://github.com/PostHog/posthog/pull/2299
#### *Thank you* for your bug report – we love squashing them! | https://github.com/PostHog/posthog/issues/2306 | https://github.com/PostHog/posthog/pull/2316 | 1daede8ad330e0b6331b1fb53a529a5e2a164bdd | a3f055429a3dace38ba233e4e7455c433802b8e5 | "2020-11-10T09:49:14Z" | python | "2020-11-12T10:58:35Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,301 | ["ee/clickhouse/models/action.py", "ee/clickhouse/models/cohort.py", "ee/clickhouse/models/property.py", "ee/clickhouse/queries/test/test_trends.py"] | Bug with contains filter in array-based attributes | ## Bug description
When filtering insights by active feature flags, and trying to select a single feature flag (by using a `contains` selector), events are not being correctly filter (i.e. no events are returned). This presumably happens because the `active_feature_flags` attribute is stored as an array and the operator does not work properly on CH.
## Expected behavior
Relevant events should be loaded.
## How to reproduce
1. Create an insights graph, filter by "Active feature flags" using a contain selector.
Alternatively, just open [this graph](https://app.posthog.com/insights?actions=%5B%7B%22id%22%3A1578%2C%22name%22%3A%22created%20action%22%2C%22type%22%3A%22actions%22%2C%22order%22%3A0%7D%5D&events=%5B%5D&new_entity=%5B%5D&interval=week&date_from=-90d&breakdown=false&breakdown_type&properties=%5B%7B%22key%22%3A%22%24active_feature_flags%22%2C%22value%22%3A%22actions-ux-201012%22%2C%22operator%22%3A%22icontains%22%2C%22type%22%3A%22event%22%7D%5D).
## Environment
Cloud latest version.
#### *Thank you* for your bug report – we love squashing them!
CC @timgl
| https://github.com/PostHog/posthog/issues/2301 | https://github.com/PostHog/posthog/pull/2711 | 177cee9e38e3244bb664219316e712732beb98af | 25d60bf839164b680ea9484a8a1addeb1c442877 | "2020-11-10T06:42:01Z" | python | "2020-12-09T18:19:58Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,278 | ["frontend/src/lib/utils/rrwebBlockClass.tsx"] | Use ph-no-capture instead of rr-block to block sensitive info | ## Is your feature request related to a problem?
People already use ph-no-capture to block sensitive data. There's no reason they should use a different classname (with a different prefix) to block stuff for session recording
## Describe the solution you'd like
Rename rr-block to ph-no-capture
## 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/2278 | https://github.com/PostHog/posthog/pull/2279 | efa6015a0546baaf2337535d0af5d2e0280f6b23 | 02d15c721cdcb5da911d6f422152a5e93a932089 | "2020-11-09T10:57:58Z" | python | "2020-11-09T19:33:36Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,260 | ["posthog/api/organization_invite.py", "posthog/api/test/test_organization_invites.py", "posthog/models/organization.py"] | Return a nicer error when inviting someone who's already invited | ## Is your feature request related to a problem?
Right now, if you try to invite someone who's already invited (or a user) you get the following error message:
## Describe the solution you'd like
The server itself does return a useful error message, so we could just display that
## 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/2260 | https://github.com/PostHog/posthog/pull/2481 | c29ed53c699d46347d6fc5d60ddbf79e0c92b7c6 | ac1f6fff93fdda3eba1873f3b0cadba11b99c5e3 | "2020-11-06T10:46:44Z" | python | "2020-11-24T14:04:09Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,246 | ["frontend/src/scenes/insights/PeopleModal.js"] | Clicking on Trends chart data point always "finds 99 users" | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
This number is always 99:
<img width="688" alt="Screenshot 2020-11-05 at 16 20 53" src="https://user-images.githubusercontent.com/38760734/98267239-0f221200-1f83-11eb-90bf-7c083aac355a.png">
## Expected behavior
"Found X users"
## How to reproduce
1. Click on a data point in a Trends chart
2.
3.
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2246 | https://github.com/PostHog/posthog/pull/2330 | ee65654676444b5bf72ae66be33893cc5e737fb1 | 4810e6f98a36cefee2781b3a59707f417f6ed389 | "2020-11-05T16:22:38Z" | python | "2020-11-11T08:51:06Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,245 | ["frontend/src/scenes/App.tsx", "frontend/src/scenes/PreflightCheck/index.js"] | Large gray bar at the bottom of the /signup page | ## Bug description
On `/signup`, the bottom of the page below the signup form is a big gray (#f2f2f2) bar.
<img width="1008" alt="Screen Shot 2020-11-05 at 16 42 02" src="https://user-images.githubusercontent.com/4550621/98262487-f6672b80-1f85-11eb-88f6-40c00eebc335.png">
This seems to have been introduced by #2114. – previously `body` background was white by default, now it's this gray.
## Environment
- master
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2245 | https://github.com/PostHog/posthog/pull/2323 | 2649e34c9609b5d54b196b428c9dd4abfd453e9b | ee65654676444b5bf72ae66be33893cc5e737fb1 | "2020-11-05T15:45:09Z" | python | "2020-11-11T07:52:32Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,224 | ["posthog/celery.py"] | Instance status reports get sent multiple times | ## Bug description
Some instances sent instance status report thousands of times. I bet it's because of Celery retrying or something, as some of the queries are using COUNT(*) and can be very slow. We should use estimated row sizes instead probably.
## Expected behavior
Only sent 1 instance report per team
## How to reproduce
1.
2.
3.
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2224 | https://github.com/PostHog/posthog/pull/2226 | a25217463d2d7554b57fe5dfe152543364fb4c57 | c875954eb1338417691efc7afab395a32c351883 | "2020-11-04T16:52:38Z" | python | "2020-11-05T08:57:29Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,203 | ["frontend/src/scenes/project/Settings/WebhookIntegration.tsx", "posthog/api/user.py"] | Slack/Microsoft Teams Integration UX is a little confusing | ## Bug description
<img width="704" alt="Screenshot 2020-11-03 at 15 59 49" src="https://user-images.githubusercontent.com/47497682/98009740-cdac2e00-1ded-11eb-940f-70cdfbbbca74.png">
The UX here is unclear - the message 'integration disabled' in the webhook URL makes me feel like maybe either either need to enter the URL and it'll work *or* maybe i"ll go to the trouble of entering the URL then it won't work because it's disabled globally.
If it is disabled globally, then this input should only appear for admin users (with perhaps a 'Request integration' button that messages the admin user as a second step)
If it just needs a webhook URL to be entered, then we should clarify this placeholder text.
Sidenote: We should add Discord since this also works [as I think the API is the same?](https://github.com/PostHog/posthog.com/issues/564)
| https://github.com/PostHog/posthog/issues/2203 | https://github.com/PostHog/posthog/pull/2488 | 760dd9a6b289041549fa6115f36d47889ef4f205 | 37243eef32914715391f928138be252b415141de | "2020-11-03T16:05:05Z" | python | "2020-11-26T12:47:15Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,173 | ["ee/clickhouse/process_event.py", "posthog/tasks/process_event.py"] | React-native sending incorrect timestamps | ## Bug description
It looks like either timestamp or sent_at is being sent without timezone, causing [this issue](https://sentry.io/organizations/posthog/issues/1972106098/?project=1899813&query=is%3Aunresolved&statsPeriod=14d)
## Expected behavior
It should send both timestamps with timezone
## How to reproduce
1.
2.
3.
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2173 | https://github.com/PostHog/posthog/pull/2396 | f39575d388a2f1da0555a466729b152531175f8b | 6906c86a5ce7a1823ff574c0d987bfe20785c2e7 | "2020-11-02T17:46:44Z" | python | "2020-11-20T13:47:03Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,135 | ["posthog/settings.py", "posthog/views.py"] | Loading /instance/status fails on self-hosted instance | ## Bug description
I set up a self-hosted instance via AWS cloudformation and updated it recently.
The page /instance/status fails to load for me.
## Expected behavior
Instance status page loads successfully.
## How to reproduce
- Set up a cloudformation instance
- ???
- Visit /instance/status
- See report on 500 error from backend
## Environment
- 1.15.1 (latest docker container)
## Additional context
Not able to provide a lot of useful context here due to https://github.com/PostHog/deployment/issues/32
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2135 | https://github.com/PostHog/posthog/pull/2237 | 63c35d20bfa2e0b3f40aec0029b23acfba05d9e2 | 4f863bb57f0751901bd1332ab62139a98d62c4ad | "2020-10-30T12:54:01Z" | python | "2020-11-06T08:57:07Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,107 | ["frontend/src/scenes/sessions/SessionsPlayer.tsx", "frontend/src/scenes/sessions/sessionsTableLogic.ts"] | Save session player settings in localStorage | ## Is your feature request related to a problem?
Currently, when watching session recordings you have to choose playback speed every time.
## Describe the solution you'd like
Store this info in localStorage instead and use it when initializing the player again.
| https://github.com/PostHog/posthog/issues/2107 | https://github.com/PostHog/posthog/pull/2110 | 67debacff2a1d1fc75f7f430f9b14acd9dc7eed3 | eb4817b8f326492b16fd58a3ea342106e459b1fa | "2020-10-29T12:41:52Z" | python | "2020-11-05T11:26:53Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,094 | ["cypress/integration/person.js", "frontend/src/lib/constants.ts", "frontend/src/scenes/persons/PersonTable.js", "posthog/demo.py"] | Too many distinct_ids | ## Bug description
*Please describe.*
When a user has a lot of distinct_ids, it could get ugly.
*If this affects the front-end, screenshots would be of great help.*
Viewing window at 33% and these are my distinct_ids
<img width="639" alt="Screen Shot 2020-10-29 at 10 06 20 AM" src="https://user-images.githubusercontent.com/13127476/97547717-86b0d980-19a4-11eb-826d-971c9e3faef1.png">
## Expected behavior
Should only show the first 3 distinct ids. If there are more than three, show a link that says "x distinct ids hidden. Click to show." When clicked, it should show all distinct ids.
## How to reproduce
1. Go look at profile for my email
2.
3.
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2094 | https://github.com/PostHog/posthog/pull/2480 | 8fe26f37b21a1b8e950de664437831fac248da6c | 000f76a5bdebcc30f5c38bf4c1c75c9125d9cb12 | "2020-10-29T09:07:08Z" | python | "2020-11-25T10:12:22Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,093 | ["frontend/src/scenes/users/Cohort.js"] | Deleting a group in cohort multiples the OR | ## Bug description
*Please describe.*
If you have a cohort and want to delete some of the groups to update the cohort, a bunch of ORs are left and it's very glitchy
*If this affects the front-end, screenshots would be of great help.*
<img width="744" alt="Screen Shot 2020-10-29 at 9 44 37 AM" src="https://user-images.githubusercontent.com/13127476/97545578-9d096600-19a1-11eb-991a-14416ca504d1.png">
## Expected behavior
If you delete a group that's above another, it should just disappear as expected and move the rest of the groups under it up
## How to reproduce
1. Go to a cohort with multiple groups
2. Delete the top most group
3.
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2093 | https://github.com/PostHog/posthog/pull/2324 | fdbadbaa634e2e6a83a4ee7b20dab5206c18f7bd | 229b665c1e8e0a03d8571b91aeaeb729cf41fbca | "2020-10-29T08:46:58Z" | python | "2020-11-11T14:32:02Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,079 | ["docker-compose.yml"] | docker-compose down causes data loss | ## Bug description
Looks like the production docker-compose file doesn't map a local folder for database data and running `docker-compose down` removes the old installation.
I say this because when I do `docker-compose down` and `docker-compose up` it gives me the preflight screen.
## Expected behavior
`docker-compose down` should not cause data loss.
## How to reproduce
1. `docker-compse up -d`
2. Setup a instance
3. `docker-compose down`
## Environment
- PostHog cloud or self-managed? self-managed
- PostHog version/commit: commit 99e2f2e0d936bad1cb38549e569b80de82a9babf
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/2079 | https://github.com/PostHog/posthog/pull/2359 | 7ac64c84f10c0b13110edc032e5993b0371cce35 | 9dc202ee24872a2761c630df16b4ed6241dc2ffb | "2020-10-28T18:29:14Z" | python | "2020-11-13T13:34:55Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,057 | ["cypress/integration/featureFlags.js", "frontend/src/lib/components/PropertyFilters/PropertyFilterButton.tsx", "frontend/src/lib/components/PropertyFilters/PropertyFilters.js", "frontend/src/lib/components/PropertyFilters/PropertyFiltersDisplay.tsx", "frontend/src/scenes/experimentation/FeatureFlags.js"] | Add feature flag filters to main table | ## Is your feature request related to a problem?
To understand how a feature flag is built up, I need to click into each individual feature flag
## Describe the solution you'd like
I want to see everything under "Filter by user properties" (but non-clickable and without the "X" and "Add filter" button) and I want to see the percentage of user roll out, all inside the main table
## Describe alternatives you've considered
Click into each feature flag
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/2057 | https://github.com/PostHog/posthog/pull/2387 | 88ad205a3ae8ed1fe48cd93d4ef2a55d28032321 | f39575d388a2f1da0555a466729b152531175f8b | "2020-10-27T22:24:18Z" | python | "2020-11-20T10:03:14Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 2,050 | ["frontend/src/lib/components/PropertyFilters/PropertyFilter.js", "frontend/src/lib/components/PropertyFilters/PropertyValue.js", "frontend/src/lib/components/SelectGradientOverflow.scss", "frontend/src/lib/components/SelectGradientOverflow.tsx", "frontend/src/scenes/insights/BreakdownFilter.js"] | Insights filters aren't obviously scrollable | I've left this up for clarity - I was confused by the UI!
## Is your feature request related to a problem?
We have way more filters than the UI makes obvious in the insights page.
These include some basic, important use cases like UTM tags.
You can find these filters by searching in the text box, but they don't appear unless you scroll or type something ie:
## Describe the solution you'd like
Add something to make it obvious you can scroll the list. | https://github.com/PostHog/posthog/issues/2050 | https://github.com/PostHog/posthog/pull/2453 | 454161db57f7675fff5c2184f6e1db72c1acb1bc | 433a37c48202895ba9e4e111e0901d8aea4e5e64 | "2020-10-27T13:38:03Z" | python | "2020-11-24T07:59:59Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,999 | ["cypress/integration/featureFlags.js", "frontend/src/lib/utils.tsx", "frontend/src/scenes/actions/ActionsTable.js", "frontend/src/scenes/events/EventsTable.js", "frontend/src/scenes/experimentation/FeatureFlags.js"] | Confusing UX with feature flags. | ## Is your feature request related to a problem?
With the blue button at the end of the table as the only visible and dominant action, it's not obvious clicking on any non-indicated part of the row opens the "edit" view.
## Describe the solution you'd like
Either make the blue button a small secondary-looking icon... or add an edit button... or both?
## Describe alternatives you've considered
Clicking around until something happens
## Additional context
Wanted to add myself to a feature flag.
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/1999 | https://github.com/PostHog/posthog/pull/2243 | 4810e6f98a36cefee2781b3a59707f417f6ed389 | 4dffff55431b522df1c78df561456842cb68b346 | "2020-10-23T08:50:58Z" | python | "2020-11-11T11:22:15Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,937 | ["ee/settings.py", "latest_migrations.manifest", "posthog/celery.py", "posthog/email.py", "posthog/migrations/0091_messagingrecord.py", "posthog/models/__init__.py", "posthog/models/messaging.py", "posthog/settings.py", "posthog/tasks/email.py", "posthog/test/test_email.py"] | Fix weekly email report | Fix release from #1860 (hotfix #1934).
- Cron job to send weekly email report is processed multiple times. Review scheduling process to send to only one worker.
- Implement mechanism to ensure each email is sent only once to each recipient.
- Improve the way the async task is processed by creating a separate task for each organization, instead of processing all organizations in a single task. | https://github.com/PostHog/posthog/issues/1937 | https://github.com/PostHog/posthog/pull/1954 | fb352aa8dc2ecd322c7e05650b26d77995f03c4b | 44bfcffca417dbc31c9f9e79e7f2652f67175737 | "2020-10-20T07:45:57Z" | python | "2020-10-22T16:46:33Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,928 | ["frontend/src/scenes/events/EventDetails.js"] | Hidden properties applied to the middle of the list | ## Bug description
When clicking "3 hidden properties. Click here to show", I have to play a game of clue to figure out which added properties are hidden and which are not.
## Expected behavior
The hidden properties would show up in the bottom of the list.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/1928 | https://github.com/PostHog/posthog/pull/2326 | 9fff06e2cce674fd6abfdd75f41ad85a5a343b46 | 2649e34c9609b5d54b196b428c9dd4abfd453e9b | "2020-10-19T09:37:47Z" | python | "2020-11-11T07:16:22Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,920 | ["frontend/src/layout/SendEventsOverlay.js", "frontend/src/scenes/App.js", "frontend/src/style/send-events-overlay.scss"] | Send events overlay background broken | ## Bug description
This image doesn't load:
https://posthog.s3.eu-west-2.amazonaws.com/preview-action-trends.png?1602965696886
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/1920 | https://github.com/PostHog/posthog/pull/1922 | 36a5d97389012d85df0b7b06af2dbb35e24f5db2 | 5785fe726e7e861db3c5692d31139d7cdee902ae | "2020-10-17T20:16:27Z" | python | "2020-10-19T09:52:49Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,911 | ["frontend/src/layout/Sidebar.scss"] | Responsive navigation overlay doesn't cover entire page | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
<img width="889" alt="Screenshot 2020-10-16 at 16 57 40" src="https://user-images.githubusercontent.com/38760734/96285073-5e090700-0fd6-11eb-9014-6b72e30b9302.png">
## Expected behavior
Overlay and sidebar cover the entire height of the window
## How to reproduce
1. Open the PostHog navigation on a small screen
2.
3.
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/1911 | https://github.com/PostHog/posthog/pull/1924 | 2b81946f3b3dbf58dd80bde5716f0ba1baa45ceb | 36a5d97389012d85df0b7b06af2dbb35e24f5db2 | "2020-10-16T16:39:11Z" | python | "2020-10-19T09:39:15Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,904 | ["frontend/src/scenes/userLogic.tsx"] | Listening for events page whites out after a while | ## Bug description
Listening for events page becomes fully white after a while if a request to /api/user fails.
Before:
After:
## Expected behavior
The page would continue showing even as network requests fail once/twice.
## How to reproduce
1. Set up a new instance
2. Register, get to "Listening to events!"
3. Cause a request to fail
4. See a blank page
## Environment
- Self-managed
## Additional context
In my case, I had set up an instance on AWS via https://posthog.com/docs/deployment/deploy-aws and every now and again a request fails with 502. However this also consistently occurs if you e.g. turn the wifi off.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/1904 | https://github.com/PostHog/posthog/pull/1906 | d1715b757e637ec8047228860da13571d8a77956 | f8788287dbb2f74950e71707c24ab58982998b7e | "2020-10-16T13:06:01Z" | python | "2020-10-19T08:55:38Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,889 | ["frontend/src/lib/components/Link.js", "frontend/src/lib/components/Link.tsx", "frontend/src/lib/components/LinkButton.js", "frontend/src/lib/components/LinkButton.tsx"] | Simplify AWS CloudFormation deployment instructions | ## Is your feature request related to a problem?
The current [AWS cloudformation documentation](https://posthog.com/docs/deployment/deploy-aws#cloudformation-install-recommended) is quite wordy, making setting things up intimidating and take far too long.
## Describe the solution you'd like
The best-in-class solution and documentation for setting up ECS clusters with CloudFormation is https://github.com/buildkite/elastic-ci-stack-for-aws.
It has:
- Clickable deploy button
- AWS CLI instructions for install + upgrading based on a local config file
- Repo with a issue tracker and relevant config -> easy for users to make improvements
~~Ideally we'd also create a repo, link to documentation from there and automatically deploy relevant config changes to S3 on merge.~~ This already exists at https://github.com/PostHog/deployment.
## Describe alternatives you've considered
Keep current solution.
| https://github.com/PostHog/posthog/issues/1889 | https://github.com/PostHog/posthog/pull/1890 | 2fef0bf358c3b189d58964d61cb46eefc0ec9643 | 19fede85c592e904c0bac232362125d1a4c25ffb | "2020-10-15T06:32:29Z" | python | "2020-10-15T08:06:14Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,884 | ["frontend/src/lib/components/CommandPalette/commandPaletteLogic.ts", "frontend/src/lib/components/CommandPalette/index.tsx"] | Share feedback in command palette is confusing | ## Is your feature request related to a problem?
The share feedback custom command has confusing UX.
- It's hard to understand that you're supposed to type the message on the command input to send it (@EDsCODE had this issue too).
- I don't think it's great to have the extra email option, we're just potentially adding strain to users without any huge additional value.
- We're inherently predisposing users to writing short feedback. We want them to be as verbose and provide as much context as possible.
In addition, there seems to be some weird behavior with the way command results are shown (see screenshot below). I would expect that typing share would show share feedback as the first result.
## Describe the solution you'd like
I think the following UX would work better:
- After selecting the share feedback command you get the two options (send a message & schedule a call). You must select one.
- If you select the send a message option, we open another screen where the text input is large and multi-lined (add a button to send or Cmd + Enter to send).
## Describe alternatives you've considered
Keep the current UX?
## Additional context
The feature was shipped before having time for a feedback round.
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/1884 | https://github.com/PostHog/posthog/pull/1905 | d4bf674a8f62fda02a8cedd641d832171eb35177 | f3ce6fc2edce9bd3aed04cdca94eb33a147b4a8c | "2020-10-14T14:23:21Z" | python | "2020-10-19T13:05:09Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,870 | [".github/workflows/build-hogql-parser.yml", ".github/workflows/container-images-ci.yml"] | Release 1.16.0 - 29 Oct 2020 | # Things we want to achieve
- Session recording #1846 (@macobo)
- AWS one-click deployment (@macobo)
- Plugin infra + example plugins (Marius to come up with list) (@mariusandra #1896)
- Have great UX (@paolodamico #1694 #1775 #1841 #1875, )
- Add feature flags to all client libraries (@timgl NodeJS @fuziontech mobile, go @mariusandra Ruby, php)
- Feature flag interface @timgl #1697
- Social auth improvements (@twixes #1888 #1594)
- Awesome guided demo + a lot more data (@Twixes https://github.com/PostHog/posthog-production/issues/18)
- Merge Organization PR (@Twixes)
- Clickhouse turned on for everyone on app + refactor(@EDsCODE (+@timgl for elements_chain))
- Every query under 5 seconds, person_id on events, backfill elements_chain (@fuziontech)
- Website refactor (@yakkomajuri)
- 5-6 pages with new components (Lottie)
- pages for new features (Lottie) | https://github.com/PostHog/posthog/issues/1870 | https://github.com/PostHog/posthog/pull/19891 | bbf07af5e98ab5c664ebf765ed81e5182cefc146 | 3fba4c63aa98deb5986243ca1ee18b52bbc68374 | "2020-10-14T08:49:54Z" | python | "2024-01-23T13:13:39Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,866 | [".github/workflows/build-hogql-parser.yml", ".github/workflows/container-images-ci.yml"] | Command palette shortcut clashes with chrome on win/linux | ## Bug description
In chrome on windows and linux, ctrl + k also starts search in the address bar.
See https://support.google.com/chrome/answer/157179?co=GENIE.Platform%3DDesktop&hl=en&oco=0 under address bar shortcuts
## Expected behavior
Different/non-clashing shortcut is used or avoid triggering browser search feature.
## How to reproduce
1. Use chrome/chromium on linux
2. Ctrl + k
3.
## Environment
- All
- DEBUG at 38135ba73ad9c00e0181b60ea725d36ff52e76b5
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/1866 | https://github.com/PostHog/posthog/pull/19891 | bbf07af5e98ab5c664ebf765ed81e5182cefc146 | 3fba4c63aa98deb5986243ca1ee18b52bbc68374 | "2020-10-14T07:46:23Z" | python | "2024-01-23T13:13:39Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,844 | ["frontend/src/layout/TopContent/User.js", "frontend/src/lib/components/CommandPalette/commandPaletteLogic.ts", "frontend/src/scenes/userLogic.tsx"] | Session recording feature flag leaking? | ## Bug description
We have a beta feature up on app.posthog.com called "session recording" (via rrweb). Search and you'll see the various PRs for it.
I'm logged in as [email protected] and even though I'm not in the "posthog team" cohort, for which this feature flag is enabled, I see the session recording features.
## Expected behavior
I should not see the session recordings option.
## How to reproduce
Sign up/in as someone not in the posthog team cohort and you'll see that the flag applies to you.
## Environment
- PostHog cloud or self-managed?
- PostHog version/commit
## Additional context
This feature is so cool though! I can see so many ways to make the product better with it.
Random other thing: the "skip inactive" toggle doesn't seem to work though.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/1844 | https://github.com/PostHog/posthog/pull/1850 | 2d60a5b670bd852f825ae38a54d6738b9fcb3fd3 | 2fef0bf358c3b189d58964d61cb46eefc0ec9643 | "2020-10-13T08:25:42Z" | python | "2020-10-15T07:56:58Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,749 | ["plugin-server/yarn.lock"] | [clickhouse] Implement connection pooling | I often have queries crashing when testing the app in localhost with the clickhouse backend.
From https://clickhouse-driver.readthedocs.io/en/latest/quickstart.html#async-and-multithreading
>Every ClickHouse query is assigned an identifier to enable request execution tracking. However, ClickHouse native protocol is synchronous: all incoming queries are executed consecutively. Clickhouse-driver does not yet implement a connection pool.
> To utilize ClickHouse’s asynchronous capability you should either use multiple Client instances or implement a queue.
> The same thing is applied to multithreading. Queries from different threads can’t use one Client instance with single connection. You should use different clients for different threads.
> However, if you are using DB API for communication with the server each cursor create its own Client instance. This makes communication thread-safe.
Thus the same problems will surely be present in production as well.
The solution is probably to implement [clickhouse-pool](https://pypi.org/project/clickhouse-pool/)
| https://github.com/PostHog/posthog/issues/1749 | https://github.com/PostHog/posthog/pull/10365 | 8da7cf9a2adf0d6ff283616dadf754d35650ecea | 374b929cf664ee4ade2329c13ae2780093399dc7 | "2020-09-29T11:07:23Z" | python | "2022-06-24T14:45:29Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,742 | ["ee/clickhouse/demo.py"] | [clickhouse] Improve payload serialization | Potentially related to an escaping issue. Some urls such as `.../demo/1` are being recorded in the db as `.../demo1`
We should improve the serialization using a library such as avro or protobuf to define structure of payloads | https://github.com/PostHog/posthog/issues/1742 | https://github.com/PostHog/posthog/pull/1757 | e3e3501f2bb1cd67d8696fb712124ad008706cc0 | 37ccb7026f67fe08f9c3cc2c89095f2ae27c85a3 | "2020-09-29T08:05:03Z" | python | "2020-09-29T16:06:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,740 | ["plugin-server/yarn.lock"] | [clickhouse] feature flag all the endpoints | add a flag in all the clickhouse endpoints so we can deploy and use clickhouse internally to start | https://github.com/PostHog/posthog/issues/1740 | https://github.com/PostHog/posthog/pull/10365 | 8da7cf9a2adf0d6ff283616dadf754d35650ecea | 374b929cf664ee4ade2329c13ae2780093399dc7 | "2020-09-29T07:56:05Z" | python | "2022-06-24T14:45:29Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,739 | ["plugin-server/yarn.lock"] | Consolidate and write Tests for SQL queries | We've written a lot of queries that get the job done. Some of them are very specific.
We should parameterize the queries more so that they can be reused more.
We should also have unit tests to make sure the queries do what we expect. For example, the query building in `ee/clickhouse/models/action.py` are untested right now | https://github.com/PostHog/posthog/issues/1739 | https://github.com/PostHog/posthog/pull/10365 | 8da7cf9a2adf0d6ff283616dadf754d35650ecea | 374b929cf664ee4ade2329c13ae2780093399dc7 | "2020-09-29T07:48:22Z" | python | "2022-06-24T14:45:29Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,719 | ["app.json", "posthog/management/commands/api_keys.py", "posthog/management/commands/setup_dev.py"] | Provide non interactive Posthog setup, for instance via manage.py subcommand | Hi,
I integrate Posthog (with Posthog docker image) in my development environment.
I need to setup Posthog via script.
For the previous Posthog version, I used this script:
```
import sys
import requests
client = requests.session()
url = 'http://127.0.0.1:8000/setup_admin'
client.get(url)
if 'csrftoken' in client.cookies:
csrftoken = client.cookies['csrftoken']
else:
csrftoken = client.cookies['csrf']
r = client.post(
url,
data={
'email': '[email protected]',
'password': 'password',
'company_name': 'Example',
'emailOptIn': 'off',
'name': 'admin',
'csrfmiddlewaretoken': csrftoken
},
headers=dict(Referer=url)
)
```
This script didn't work because Posthog now provide `/preflight` page:
<img width="400" src="https://user-images.githubusercontent.com/54498080/94268444-750b8a80-ff3d-11ea-8b07-2e8962f8c183.png">
What do you think to provide a `manage.py` subcommand to setup Posthog via cli?
Best regards,
Stéphane | https://github.com/PostHog/posthog/issues/1719 | https://github.com/PostHog/posthog/pull/1720 | 9d7dae201a315f0a709a209054cc3eee165448ac | f81c6c31349bfce14040887392189356c93c6ee5 | "2020-09-25T12:46:29Z" | python | "2020-09-28T19:25:50Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,688 | ["frontend/src/models/dashboardsModel.tsx", "frontend/src/scenes/dashboard/DashboardHeader.tsx", "frontend/src/scenes/dashboard/Dashboards.tsx", "posthog/api/dashboard.py", "posthog/api/test/test_dashboard.py", "posthog/models/dashboard.py"] | FR: Cloning dashboards | ## Is your feature request related to a problem?
A user mentioned needing a feature to clone dashboards as they create the same dashboard multiple times, each for a different end-customer. Given that we are already planning on doing default / custom dashboards (#1659) we can add this functionality to facilitate dashboard creation.
## Describe the solution you'd like
Simple functionality to duplicate a dashboard.
- Add "Duplicate" button to dashboard list and clone dashboard (e.g. "Copy - AARRR").
## Describe alternatives you've considered
Re-create the dashboard manually.
## Additional context
No additional context.
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/1688 | https://github.com/PostHog/posthog/pull/6476 | 8edd14a16ad936fb241dcf856925e9f2ea87cba4 | f34bd5551f35941a02a33d3314bd2cf8e8c2a722 | "2020-09-21T07:07:05Z" | python | "2021-10-19T16:10:27Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,576 | ["posthog/api/decide.py"] | Invalid JSON causes internal server error | ## Bug description
I am trying to use the RESTful API to be able to built on the `posthog-js-lite`-package by adding the `decide`-endpoint only when I tried to call this endpoint in Paw I kept getting 500 Internal Server Error. After a few hours of staring at what could be the problem I noticed I was sending invalid JSON as Base64 string.
Encoded: `eyJ0b2tlbiI6IFRva2VuSGVyZSwgImRpc3RpbmN0X2lkIjogMTc0NTYyNWM2MDUxOTgtMGIwZWZkY2Y2ZjJjOGEtMWU0ZDMyMWEtMWVhMDAwLTE3NDU2MjVjNjA2ZGNkfQ==`
Decoded: `{"token": TokenHere, "distinct_id": 1745625c605198-0b0efdcf6f2c8a-1e4d321a-1ea000-1745625c606dcd}`
Note that I forgot to properly quote the string values of the properties `token` and `distinct_id`
## Expected behavior
The API shouldn't fail with status code 500 but instead returning something like 400 or 422 to indicate something is wrong with my request instead of throwing confusing 500.
## How to reproduce
1. Run the `curl` command:
```
curl -X "POST" "https://app.posthog.com/decide/" \
-H 'Origin: https://localhost:5000' \
-H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36 Edg/85.0.564.44' \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode "data=eyJ0b2tlbiI6IGFwaV9rZXksICJkaXN0aW5jdF9pZCI6IDE3NDU2MjVjNjA1MTk4LTBiMGVmZGNmNmYyYzhhLTFlNGQzMjFhLTFlYTAwMC0xNzQ1NjI1YzYwNmRjZH0="
```
2. Notice 500 is returned
## Environment
- PostHog cloud or self-managed?: cloud
- PostHog version/commit: latest cloud version
| https://github.com/PostHog/posthog/issues/1576 | https://github.com/PostHog/posthog/pull/1581 | 49994a4b2855dbef564a366e8a32273aa9228919 | 832b55f71eb27e7bf9ffe649da4b112885714f1f | "2020-09-04T12:18:36Z" | python | "2020-09-07T11:43:21Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,554 | ["cypress/integration/feature_flags.js", "frontend/src/lib/utils.js", "frontend/src/scenes/experiments/EditFeatureFlag.js", "frontend/src/scenes/experiments/FeatureFlags.js", "frontend/src/scenes/experiments/featureFlagLogic.js"] | Allow Feature Flag deletion | ## Is your feature request related to a problem?
*Please describe.*
Feature flags currently can only be toggled on and off, but not deleted.
## Describe the solution you'd like
A delete button.
## Describe alternatives you've considered
Repurposing old feature flags for new ones.
## Additional context
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/1554 | https://github.com/PostHog/posthog/pull/1761 | 632b2195f7c3f42af71f7f51a889c9bc7ab05048 | f117b66ebe7411a2efe00dc987190c3f15bfd506 | "2020-09-02T19:12:41Z" | python | "2020-10-13T10:47:46Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,552 | ["posthog/celery.py"] | `first team event ingested` event sent multiple times | ## Bug description
- See screenshot below (it's likely being processed in 3 workers at the same time).
## Expected behavior
- We should receive the event only once.
## How to reproduce
1. View a user of recent creation with this event ([example](https://app.posthog.com/person/5fabb7b9-a36c-4419-af97-eea75960b2e4))
## Environment
- Cloud from PR #1508
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/1552 | https://github.com/PostHog/posthog/pull/2226 | a25217463d2d7554b57fe5dfe152543364fb4c57 | c875954eb1338417691efc7afab395a32c351883 | "2020-09-02T17:30:02Z" | python | "2020-11-05T08:57:29Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,518 | ["posthog/templates/head.html"] | Stop capturing events on debug instances | When `DEBUG = 1` stop sending events to PostHog (via `posthoganalytics`) as to remove noise from test installations. Perhaps we can just send a boot / install event with a property that indicates if it's running on debug to track the number of test installations.
CC @yakkomajuri | https://github.com/PostHog/posthog/issues/1518 | https://github.com/PostHog/posthog/pull/1539 | c59ab4c3a7f723d3a42f002ee7ceffdf25ef1e12 | a2b7e9134ec763588791076f5de0dbe15afd04f4 | "2020-08-26T20:32:13Z" | python | "2020-09-01T14:19:19Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,474 | ["frontend/src/layout/navigation/Navigation.scss", "frontend/src/layout/navigation/TopNavigation.tsx", "frontend/src/scenes/organization/TeamMembers/Invites.tsx", "frontend/src/scenes/organization/TeamMembers/Members.tsx", "package.json", "yarn.lock"] | Gravatar profile picture | ## Is your feature request related to a problem?
We could make the app's UI a bit more "human" by putting a user's profile picture in the top right.
## Describe the solution you'd like
A pretty simple solution would be pulling in the [gravatar](https://en.gravatar.com) linked to the user's email address.
## Describe alternatives you've considered
We could add pictures uploaded by users to PostHog, but that'd be significantly more effort and doesn't seem worth it at the moment.
## Additional context
Noticed today that Docker Hub does this, but I've definitely seen lots of other services do it as well before.
#### *Thank you* for your feature request – we love each and every one!
| https://github.com/PostHog/posthog/issues/1474 | https://github.com/PostHog/posthog/pull/3584 | 26fdfabc350b366fed0ad4c1683c326336abfdb3 | 6f85e8f5800b26b00be24cdc75b4716d00b30de5 | "2020-08-20T08:56:37Z" | python | "2021-03-08T13:13:31Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,465 | ["frontend/src/lib/components/CopyToClipboard.js", "frontend/src/lib/components/TeamInvitation.js", "frontend/src/scenes/team/Team.js", "posthog/api/test/test_user.py", "posthog/api/user.py"] | Allow disabling of sharing link in settings | ## Is your feature request related to a problem?
I want to be able to disable the sharing link for extra security
## Describe the solution you'd like
A toggle to disable the sharing link in the sharing modal
## 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/1465 | https://github.com/PostHog/posthog/pull/1475 | ba4a7526465e1545a7af390f09953501c75643a0 | 03a42f05709e42f2122346d54790b71f893675ed | "2020-08-18T20:23:33Z" | python | "2020-08-25T09:09:39Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,458 | ["posthog/models/event.py", "posthog/test/test_event_model.py"] | remove trailing spaces in the selector box | ## Bug description
*Please describe.*
*If this affects the front-end, screenshots would be of great help.*
Trailing spaces in the selector box are not removed automatically and can mess up the event results when saving an action
## Expected behavior
## How to reproduce
1. Create a new action with any selector
2. put in a couple of spaces at the end of the line in the selector input box
3.
## Environment
- Self-managed?
- PostHog version/commit
## Additional context
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/1458 | https://github.com/PostHog/posthog/pull/1621 | 5729fb5f687f3421035fdce4d74a42c6a760264e | 4a1f8380480c5982e56b71a6f0fdc2bba980ea81 | "2020-08-18T14:31:59Z" | python | "2020-10-07T10:23:13Z" |
closed | PostHog/posthog | https://github.com/PostHog/posthog | 1,409 | ["posthog/models/event.py", "posthog/test/test_event_model.py"] | Filtering selector on attributes isn't working | ## Bug description
Creating a selector with an attribute isn't working at all.
`[data-attr="bla"]`
## Expected behavior
It should work
## How to reproduce
1. Create action
2. Add an attribute in the selector
3.
## Additional context
The reason for this is that we store the attributes as `attr__data-attr` but we do not add `attr__` in the filtering. I am working on a solution.
#### *Thank you* for your bug report – we love squashing them!
| https://github.com/PostHog/posthog/issues/1409 | https://github.com/PostHog/posthog/pull/1413 | 0e96ffb5f41b6a2ae2b540ff8fa964aa49895f85 | 2585e9507416efd758c46b02b2bd5cc489175788 | "2020-08-11T21:19:21Z" | python | "2020-08-12T16:55:56Z" |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.