Skip to content
This repository was archived by the owner on Oct 27, 2025. It is now read-only.
This repository was archived by the owner on Oct 27, 2025. It is now read-only.

misc: phone features postponed for consistent API Integration #487

Description

@42atomys

Please exprime yourself

We are currently facing a technical challenge regarding the alignment of data between webhooks and the intra API. More specifically, there is a notable inconsistency in how the phone number is synchronized between these two interfaces.

In the interest of transparency and delivering a high-quality user experience, we have decided to take a proactive decision in this regard. We will temporarily remove the phone number from our data schema. This action means that all features related to the use of the phone number will be put on hold.

This is not a step back, but rather a cautious move to avoid potential complications. We want to prevent any misunderstanding or controversy by taking this measure. We will also delete all phone number data from our database to ensure the protection of our users' personal information.

In the future, instead of trying to synchronize this information between the webhooks and the intra API, we will request the phone number directly on our site. This will allow us to ensure that we have the most up-to-date and accurate information, while better controlling the process.

We appreciate your patience and understanding while we work on this transition. We are doing everything we can to minimize the impact on our users and we are committed to maintaining transparent communication throughout this process.

Best regards,

Action Items

  • Remove the 'phone' field from the data schema
  • Erase all phone data from the database and backups across all environments
  • Eliminate all code sections related to the phone number
  • Postpone all phone number-related features indefinitely

Code of Conduct

  • I agree to follow this project's Code of Conduct

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

aspect/backend 💻Concerns the backend code in the repositorydomain/complicated 🟨The relationship between cause and effect requires analysis or expertisepriority/critical 🟥Priority 1 - Must be fixed ASAPtype/chore 🛠Code changes that neither fix bugs nor add features (refactoring, dependency changes, ...)

Projects

  • Status
    Done 🎉

Relationships

None yet

Development

No branches or pull requests

Issue actions