[ADD] estate: add module to sell property#1187
Open
prsan-odoo wants to merge 9 commits intoodoo:19.0from
Open
Conversation
506d60c to
42dea24
Compare
bit-odoo
reviewed
Mar 16, 2026
bit-odoo
left a comment
There was a problem hiding this comment.
Hello @prsan-odoo
Good Work!
I have added some comments.
Can you please follow the commit message guidelines?
https://www.odoo.com/documentation/19.0/contributing/development/git_guidelines.html
Thanks
2ccf395 to
0bb3d15
Compare
7f6eb45 to
94858ce
Compare
bit-odoo
reviewed
Mar 25, 2026
bit-odoo
left a comment
There was a problem hiding this comment.
Hello,
Good Work!
Can you please update your commit message according to the guidelines?
https://www.odoo.com/documentation/19.0/contributing/development/git_guidelines.html#commit-message-full-description
Also, can you please improve the PR title and PR description?
Thanks
de1ab64 to
b086120
Compare
-Created a new app called Estate. -Set up the estate addon with a proper manifest file. -Added estate property model with all required fields. -Access rights assigned to base groups. -CH2 , CH3 Completed.
40f40c8 to
379a448
Compare
The tutorial uses base groups, giving all rights to every user. Instead, Two dedicated groups are defined: - Agent: read and write access only - Manager: full CRUD access, implies Agent group - Admin user is automatically assigned the Manager group - CH4 Done
- Selling Price field is set as readonly so users cannot edit it manually; it is determined through the offer validation flow. - Selling Price and State fields are not duplicated when a property is copied, to avoid carrying over stale data. - Availability Date field is not duplicated so a fresh date is always required for new listings. - Bedrooms field defaults to 2 as a sensible starting point. - Active field defaults to True so properties are visible by default in list views. - State field is required and defaults to 'New' to track the property through its lifecycle. - CH5 done
379a448 to
61d8d94
Compare
Add basic UI views for the estate.property model to allow users to interact with property records. - Add list view to display properties in a tabular format. - Add form view to create, edit, and view individual properties. - Chapter 6 partially done (list and form views).
61d8d94 to
20b113c
Compare
Improve the estate.property views to make property browsing more efficient for users. - Add search view with filters for available properties and properties by current user. - Add group by postcode option in search view. - Apply domain filters on list and form views to refine displayed records. Chapter 6 completed.
20b113c to
458dcb2
Compare
The estate module needed relational fields to link properties to other records, demo data for easier development and testing, and an app logo for better identification in the app list. - Add Many2one fields for property type, buyer, and salesperson. - Add Many2many field for property tags. - Add One2many field for property offers. - Add demo data with 5 sample properties for testing. - Add app logo to identify the module in the app list. Chapter 7 completed.
458dcb2 to
d244688
Compare
…line Computed fields are needed to automatically calculate values that depend on other fields, avoiding manual input errors. - Add total area computed field combining living area and garden area. - Add best price computed field to show the highest offer received. - Add offer deadline computed field based on creation date and validity duration, with inverse to allow direct date editing. Chapter 8 partially done (computed fields only).
d244688 to
75dfa75
Compare
When a user enables the garden option, the garden area and orientation fields should be auto-filled with sensible defaults to reduce manual input. When disabled, both fields should be cleared to avoid stale data. - Add onchange method on garden field to set default garden area and orientation when garden is enabled. - Clear garden area and orientation when garden is disabled. Chapter 8 completed.
75dfa75 to
f1b3862
Compare
- Add optional hide on living area, seller, and buyer columns in list view to reduce visual clutter. - Add domain filters in search view to refine property results. - Set default search to show properties with offers received.
f1b3862 to
042e840
Compare
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
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.

-Created a new app called Estate.
-Set up the estate addon with a proper manifest file.
-Added estate property model with all required fields.
-Access rights assigned to base groups.
-CH2 , CH3 Completed.