chore: member tracker events

[gakshita]

Description

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (change that would cause existing functionality to not work as expected)
• Code refactoring
• Performance improvements
• Documentation update

Screenshots and Media (if applicable)

Test Scenarios

References

Summary by CodeRabbit

• New Features

  • Enhanced event tracking with new UI element identifiers for cycles, modules, and members.
  • Added tracking for "archive" and "restore" actions on cycles and modules.
  • Introduced granular event tracking for clicks, views, hovers, and business events across the app.

• Refactor

  • Streamlined and standardized event tracking throughout the application using new helper functions.
  • Simplified event payloads for success and error tracking.
  • Removed legacy event tracking methods and replaced them with a unified approach.

• Style

  • Added data-ph-element attributes to various buttons and UI components for improved tracking and analytics.

• Chores

  • Cleaned up unused code, imports, and obsolete event tracking logic.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This change refactors event tracking across the codebase by removing legacy event payload functions and store methods, introducing new UI element constants, and standardizing event tracking with a new helper module. Event tracking calls are updated to use structured helpers for clicks, successes, and errors, with simplified payloads and explicit element identifiers.

Changes

Files/Group	Change Summary
packages/constants/src/event-tracker/core.ts	Removed event payload functions; added new UI element identifier constants and archive/restore event constants for cycles and modules.
web/helpers/event-tracker.helper.ts	Introduced a new helper module for structured event tracking, providing functions for capturing clicks, views, hovers, successes, errors, and combined events.
web/core/store/event-tracker.store.ts	Removed workspace, cycle, and module event capture methods from the event tracker store, including their interface and implementation.
web/app/(all)/[workspaceSlug]/(projects)/projects/(detail)/[projectId]/cycles/(list)/header.tsx, web/app/(all)/[workspaceSlug]/(projects)/projects/(detail)/[projectId]/cycles/(list)/page.tsx, web/app/(all)/[workspaceSlug]/(projects)/projects/(detail)/[projectId]/modules/(list)/header.tsx, web/core/components/modules/modules-list-view.tsx, web/core/components/project/member-list.tsx, web/core/components/workspace/sidebar/projects-list-item.tsx	Replaced usage of useEventTracker with new element constants; added data-ph-element attributes to relevant buttons and menu items for tracking.
web/app/(all)/[workspaceSlug]/(settings)/settings/(workspace)/members/page.tsx, web/core/components/onboarding/invite-members.tsx, web/core/components/onboarding/invitations.tsx, web/core/components/onboarding/create-workspace.tsx, web/core/components/workspace/create-workspace-form.tsx, web/core/components/workspace/delete-workspace-form.tsx, web/core/components/workspace/settings/members-list-item.tsx, web/core/components/workspace/settings/workspace-details.tsx	Refactored event tracking for workspace/member actions to use new helper functions for success/error, with simplified payloads and explicit error objects.
web/app/(all)/invitations/page.tsx	Updated workspace invitation event tracking to use new helpers; simplified payloads and added error context; added data-ph-element to accept button.
web/ce/components/workspace/delete-workspace-section.tsx	Added data-ph-element attribute to delete workspace button.
web/ce/helpers/command-palette.ts, web/core/components/command-palette/actions/project-actions.tsx	Integrated click tracking for command palette actions using new helpers and element constants; removed legacy tracking calls.
web/core/components/cycles/analytics-sidebar/sidebar-header.tsx, web/core/components/modules/analytics-sidebar/root.tsx	Refactored sidebar event tracking to use new helper functions; removed modal management for archive/delete; simplified event payloads.
web/core/components/cycles/archived-cycles/modal.tsx, web/core/components/cycles/delete-modal.tsx, web/core/components/modules/delete-module-modal.tsx	Updated archive/delete modals to use new success/error tracking helpers with simplified payloads and error objects.
web/core/components/cycles/form.tsx, web/core/components/cycles/modal.tsx, web/core/components/modules/modal.tsx	Simplified form submission handlers by removing dirtyFields parameter; updated event tracking to use new helpers with minimal payloads.
web/core/components/cycles/list/cycle-list-item-action.tsx, web/core/components/modules/module-list-item-action.tsx, web/core/components/modules/module-card-item.tsx	Refactored favorite/unfavorite event tracking to use new helper functions and element constants; added error tracking; simplified payloads.
web/core/components/cycles/quick-actions.tsx, web/core/components/modules/quick-actions.tsx	Instrumented quick actions and context menu items with click tracking; refactored restore actions to use new success/error helpers.
web/core/components/modules/links/list-item.tsx, web/core/components/project/settings/member-columns.tsx, web/core/components/workspace/settings/invitations-list-item.tsx, web/core/components/workspace/settings/member-columns.tsx	Added data-ph-element attributes to edit/delete/context menu elements for tracking; imported new element constants.
web/core/components/project/leave-project-modal.tsx, web/core/components/project/member-list-item.tsx, web/core/components/project/send-project-invitation-modal.tsx	Refactored project member event tracking to use new helpers for success/error; streamlined payloads.
web/core/lib/posthog-provider.tsx	Added a global click listener for elements with data-ph-element attributes to capture UI interactions via the new helper; centralized PostHog enablement logic.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant UIComponent
    participant EventTrackerHelper
    participant PostHog

    User->>UIComponent: Clicks tracked element (e.g., button)
    UIComponent->>EventTrackerHelper: captureClick({ elementName })
    EventTrackerHelper->>PostHog: Send click event with elementName and timestamp

    User->>UIComponent: Performs tracked business action (e.g., create, delete)
    UIComponent->>EventTrackerHelper: captureSuccess({ eventName, payload })
    EventTrackerHelper->>PostHog: Send success event with eventName, payload, timestamp

    alt On error
        UIComponent->>EventTrackerHelper: captureError({ eventName, payload, error })
        EventTrackerHelper->>PostHog: Send error event with eventName, payload, error, timestamp
    end

Loading

Possibly related PRs

• makeplane/plane#7276: Refactored event constants and payload functions in the constants package, directly overlapping with the changes in event tracking constants and payload handling in this PR.

Suggested labels

🛠️refactor, ready to merge

Poem

A bunny with code in its paws,
Hopped through events with nary a pause.
Old trackers are gone,
New helpers hop on—
Now clicks and successes are tracked with applause!
With data-ph-element in every nook,
This rabbit ensures PostHog gets a look!

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[CLAassistant]

All committers have signed the CLA.