Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Timebox] Remove "Probability" Field from Opportunities #5735

Open
Tracked by #5816
Bonapara opened this issue Jun 4, 2024 · 3 comments · May be fixed by #5877
Open
Tracked by #5816

[Timebox] Remove "Probability" Field from Opportunities #5735

Bonapara opened this issue Jun 4, 2024 · 3 comments · May be fixed by #5877
Assignees
Labels
scope: back+front Issues requiring full-stack knowledge size: hours

Comments

@Bonapara
Copy link
Member

Bonapara commented Jun 4, 2024

Current Behavior

We have a "Probability" field on Opportunities.

CleanShot 2024-06-04 at 15 44 34

Desired Behavior

Remove this field as it's not useful.

@Bonapara Bonapara added scope: back+front Issues requiring full-stack knowledge size: hours labels Jun 4, 2024
@Bonapara Bonapara mentioned this issue Jun 11, 2024
22 tasks
@siiddhantt siiddhantt linked a pull request Jun 15, 2024 that will close this issue
@siiddhantt
Copy link
Contributor

hi, created a PR for it

@charlesBochet
Copy link
Member

charlesBochet commented Jun 18, 2024

Do we want to change it to RATING type or deprecate it?

Anyway, would be great to have @deprecated annotation

  • sync metadata will read it set isCustom

@charlesBochet charlesBochet changed the title Remove "Probability" Field from Opportunities [Timebox] Remove "Probability" Field from Opportunities Jun 18, 2024
@Bonapara
Copy link
Member Author

Depreciate it! I think we don't need a standard rating field for now, as no specific behavior would be based on it yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: back+front Issues requiring full-stack knowledge size: hours
Projects
Status: 🔖 Planned
Development

Successfully merging a pull request may close this issue.

4 participants