[19.0][FIX] srm: default request_type to customer - #761
Open
Ricardoalso wants to merge 1 commit into
Open
Conversation
request_type was only ever set via a default_request_type context key on crm.crm_lead_action_pipeline's "New" button. Any lead created another way (website form, import, other integrations) got an empty request_type and was silently excluded from the Pipeline view, whose domain requires request_type = 'customer'. Default the field itself to 'customer'. Context-set defaults still take precedence over field defaults, so the supplier RFQ flows (which set default_request_type='supplier' explicitly) are unaffected.
|
Functional test on runboat 👍 Test:
|
ivantodorovich
approved these changes
Aug 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
request_type was only ever set via a default_request_type context key on crm.crm_lead_action_pipeline's "New" button. Any lead created another way (website form, import, other integrations) got an empty request_type and was silently excluded from the Pipeline view, whose domain requires request_type = 'customer'.
Default the field itself to 'customer'. Context-set defaults still take precedence over field defaults, so the supplier RFQ flows (which set default_request_type='supplier' explicitly) are unaffected.