chore: project page 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 user interaction tracking with new data attributes on buttons and menu items across the app.
  • Introduced more granular event tracking for clicks, views, and business events (success/error) throughout the user interface.

• Refactor

  • Streamlined and standardized event tracking logic, replacing previous methods with new helper functions for capturing user actions and outcomes.
  • Simplified event payloads for tracking, focusing on key identifiers and outcomes.
  • Improved naming and organization of tracking constants for better clarity and consistency.

• Chores

  • Removed unused or redundant event tracking functions and related internal code.
  • Updated imports and cleaned up legacy tracking logic to support the new tracking system.

[CLAassistant]

All committers have signed the CLA.

[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 old event payload helper functions, introducing new element and event constants for tracking, and centralizing event tracking logic into a new helper module. Event tracking calls are updated to use these new helpers and constants, and payloads are simplified throughout.

Changes

File(s) / Area	Change Summary
packages/constants/src/event-tracker/core.ts	Removed payload helper functions; added/renamed tracker element/event constants for cycles, modules, etc.
web/helpers/event-tracker.helper.ts	Added new helper module with exported functions for capturing clicks, views, hovers, successes, errors.
web/core/store/event-tracker.store.ts	Removed workspace, cycle, and module event capture methods and related imports.
web/app/..., web/core/components/..., web/core/lib/posthog-provider.tsx, etc. (multiple files)	Refactored event tracking calls to use new helper functions/constants; added data-ph-element attributes; removed old hook usage.
web/core/components/cycles/form.tsx, web/core/components/cycles/modal.tsx, web/core/components/modules/modal.tsx	Updated function signatures to remove dirtyFields parameter from form submit handlers.

Changes Table (Grouped)

File(s) / Area	Change Summary
packages/constants/src/event-tracker/core.ts	Removed old event payload helpers; added/renamed tracker element/event constants.
web/helpers/event-tracker.helper.ts	Introduced new event tracking helper functions.
web/core/store/event-tracker.store.ts	Removed workspace, cycle, module event capture methods and related imports.
web/app/, web/core/components/, web/core/lib/posthog-provider.tsx, etc. (multiple files)	Refactored event tracking to use new helpers/constants; added data-ph-element attributes; removed old hooks.
web/core/components/cycles/form.tsx, web/core/components/cycles/modal.tsx, web/core/components/modules/modal.tsx	Updated function signatures to remove dirtyFields.

Sequence Diagram(s)

sequenceDiagram
    participant UI as UI Component
    participant Helper as event-tracker.helper.ts
    participant PostHog as PostHog Client

    UI->>Helper: captureClick({ elementName, context })
    Helper->>PostHog: posthog.capture("element_interaction", { elementName, context, type: "click", timestamp })
    Note right of PostHog: Event recorded

    UI->>Helper: captureSuccess({ eventName, payload })
    Helper->>PostHog: posthog.capture(eventName, { payload, state: "SUCCESS", timestamp })
    Note right of PostHog: Success event recorded

    UI->>Helper: captureError({ eventName, error, payload })
    Helper->>PostHog: posthog.capture(eventName, { payload, error, state: "ERROR", timestamp })
    Note right of PostHog: Error event recorded

Loading

Possibly related PRs

• makeplane/plane#7302: Removes old event payload helpers and refactors event tracking to use new helpers and constants, overlapping significantly in files and concepts.
• makeplane/plane#7276: Consolidates event constants and removes old payload helpers, directly modifying the same event tracking infrastructure.

Suggested labels

🧹chore, requires approval

Suggested reviewers

• prateekshourya29
• sriramveeraghanta
• anmolsinghbhatia

Poem

In fields of code, a rabbit hops,
Old trackers gone, new helpers pop.
With clicks and views now neatly caught,
Payloads trimmed, confusion naught.
Constants bloom like springtime leaves,
Event logs dance on gentle breeze.
🐇✨ Hooray for tidy tracking, please!

---

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.

[prateekshourya29]

directly use data attribute for these use cases.

[prateekshourya29]

here as well