Feature Request: group/categorize data pipeline destinations

Open
#40,673 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
frontend

Research direction

Start at the data pipeline destinations page identified in the issue: https://us.posthog.com/project/75496/pipeline/destinations, and inspect the frontend entry point for cdp_destinations. Clarify whether grouping by destination, status, and customer-defined usage sets are all required; done should mean the agreed grouping options are available in the destinations UX.

Written by the indexing model from the issue text.

Description

design enhancement team/data-warehouse ux
Feature request

Is your feature request related to a problem?

Data pipeline destinations can get a little messy when there are plenty of them. We should update the UX to better group these on the frontend.

Describe the solution you'd like

Group by destination, group by status, group by arbitrarily defined usage set by customer.

Additional context

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

Debug info
Kind: feedback

Target area: cdp_destinations

Report event: http://go/ticketByUUID/39346400-4acf-4c8a-b518-85ada3f19dd8

Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/019a3171-0718-7b2a-8ddc-39ad1f91ce95?t=10685

Exceptions: https://us.posthog.com/project/2/error_tracking?filterGroup=%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22key%22%3A%22%24session_id%22%2C%22value%22%3A%5B%22019a3171-0718-7b2a-8ddc-39ad1f91ce95%22%5D%2C%22operator%22%3A%22exact%22%2C%22type%22%3A%22event%22%7D%5D%7D%5D%7D

Location: https://us.posthog.com/project/75496/pipeline/destinations

Persons-on-events mode for project: person_id_override_properties_on_events
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Contributor guide

Open the contributing guide

First steps

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

More from PostHog/posthog

All issues in PostHog/posthog

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.