[IMP] estate: add offer count stat button and default fillter for available property #1102
Conversation
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
models and security folder added Chapter 1: Architecture Overview Chapter 2: A New Application Chapter 3: Models And Basic Fields Chapter 4: Security - A Brief Introduction
models and security folder added Chapter 1: Architecture Overview Chapter 2: A New Application Chapter 3: Models And Basic Fields Chapter 4: Security - A Brief Introduction
models and security folder added Chapter 1: Architecture Overview Chapter 2: A New Application Chapter 3: Models And Basic Fields Chapter 4: Security - A Brief Introduction
models and security folder added Chapter 1: Architecture Overview Chapter 2: A New Application Chapter 3: Models And Basic Fields Chapter 4: Security - A Brief Introduction
models and security folder added Chapter 1: Architecture Overview Chapter 2: A New Application Chapter 3: Models And Basic Fields Chapter 4: Security - A Brief Introduction
modified manifest file. added action view in estate property. added more fields to model Chapter 5: Finally, Some UI To Play With
|
|
estate property list view. estate property form view. estate property search view.
bit-odoo
reviewed
Jan 2, 2026
Implemented relations between models (Many2one, One2many, Many2many). Added estate_property_offer model and views. Added estate_property_type model and views. Added estate_property_tags model and views. Chapter 7: Relations Between Models
Implemented new suggestions
Added computed fields for best offer and Total area. Added computed fields for validity and deadline. Added onchange method for garden Chapter 8
Button action to manage offers and property. SQL constraint for data validation. expected price and offer price must be strictly positive. selling price must be positive. property type and tag names must be unique. Python constraint for selling price Chapter 9,10
bit-odoo
reviewed
Jan 7, 2026
bit-odoo
left a comment
bit-odoo
left a comment
There was a problem hiding this comment.
Hello,
I have added some changes.
Please apply this suggestion. #1102 (review)
Please solve this traceback - https://runbot.odoo.com/runbot/batch/2307279/build/97348832
Thanks
Corrected the import order and method names. Declared the SQL constraint after all field declarations. Changed the order of files in the manifest file.
javek-odoo
changed the title
Author
|
I have implemented all the suggested changes. |
Added inline view of properties for the property type. Added widgets for the offer state. Added different list ordering at the model, view, and manual levels. Added color field for property tags.
implemented different types of list orders model, view, manual user can list their property type based on their need. rejected offers will be appear in red and accepted offers will be green color. user can edit their offers in list view. chapter 10
user can edit their property type and tags in list view. add default filter for the available property. after accepting an offer: the accept and refuse buttons are now hidden. all other pending offers are automatically rejected. date availability field will be list view optional and hidden by default. chapter-11
add white space after if. changed order of offer_view.xml
javek-odoo
changed the title
bit-odoo
reviewed
Jan 13, 2026
bit-odoo
left a comment
bit-odoo
left a comment
There was a problem hiding this comment.
Hello,
Can you please improve your PR title.
Thanks
javek-odoo
changed the title
Author
|
I have implemented all the suggested changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Users can list their properties and add offers for them.
Admins can manage offer statuses and property statuses.
Added multiple views, actions, computed fields, and onchange fields.
Implemented SQL and Python constraints for various fields.
Added Inline Views,Widgets for color picking and statusbar.
Added List Order by models,view,manual.
user can edit their property type and tags in the list view.
after accepting an offer accept/refuse buttons are hidden and all other offers will be refused.
date availability field is hidded in list view and hidden by default.