Skip to content

Conversation

@marcelsavegnago
Copy link
Member

This module extends the CRM functionality by allowing you to validate that specific fields are filled when moving a lead/opportunity to a certain stage.

Main Features

  • Field Validation per Stage: Configure which fields must be filled when a lead/opportunity reaches a specific stage
  • Flexible Configuration: Select any field from the CRM lead model to be validated
  • Clear Error Messages: Users receive detailed validation errors indicating which fields need to be filled
  • Multi-record Support: Validation works when moving multiple leads/opportunities at once

Benefits

  • Ensure data quality by requiring important fields at specific pipeline stages
  • Prevent leads from advancing without crucial information
  • Customize validation rules for each stage of your sales pipeline
  • Improve reporting accuracy by ensuring complete data at each stage

Dependencies

This module requires:

  • crm: Odoo's CRM module

@marcelsavegnago marcelsavegnago force-pushed the 16.0-add-crm_stage_validation branch from f152c22 to b6f75e5 Compare December 4, 2025 12:56
Copy link

@kaynnan kaynnan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kaynnan
Copy link

kaynnan commented Dec 22, 2025

Copy link

@rrebollo rrebollo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Code Review: LGTM

Thank you for your valuable contribution. The feature addresses a clear need within the validation workflow scope.

For several versions now, Odoo/OCA has maintained a robust framework for this type of requirement: tier_validation (from the OCA/server-ux repository). A module like crm_stage_tier_validation would likely be well-received by the community, as it would expand the feature beyond basic field validation into a more comprehensive approval system.

Please don't misunderstand — this is excellent work and represents a key functionality. It actually raises a broader question: why isn't this already part of the vanilla system?

If merged, this PR would certainly be a valuable addition. However, from a long-term and community-wide perspective, I believe enriching established tools like tier_validation is often more sustainable than creating new, separate solutions. This approach helps consolidate efforts and avoids fragmentation.

With that said, would you be open to reviewing my PR #661? It's also an addition, so please feel free to question or comment on any aspect of it. I welcome your perspective.

Thank you again for your work and collaboration.

Copy link

@WesleyOliveira98 WesleyOliveira98 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CODE REVIEW - OK

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@marcelsavegnago marcelsavegnago force-pushed the 16.0-add-crm_stage_validation branch from b6f75e5 to 9494944 Compare December 29, 2025 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants