- Have a standard V13 with note - Connect as Admin A - Create User U1 and U2 with password and email on partner - As A, create a note N - Add U1 as a follower - Login as U1 - Open N and add U2 as a follower We have a custom record rule that provide access to notes if you are in the "message_partner_ids" of the Notes. An override to the field in notes to compute as sudo fix the issue opw-2223632 closes odoo/odoo#51082 X-original-commit: e1fbac466ff6c3abfd0de5760f43a3ff2e5cdb90 Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com>
Multi is the default api for methods, it is not necessary to explicitly decorate methods with it, adds clutter and most people use it because they see that the rest of the code uses it. Done with `find . -type f -name '*.py' | xargs sed -i '/@api.multi/d'`
UI improvement:
If there is no stage then there will be no button(no status bar) but there will be stages but task or note etc.. will not be in any stage then there will be 'undefined' so by click on that ('undefined') user can move to any stages. To avoid this behavior we add a default stage in note.
Also: - Don't display "Active -> True" when we create a note - Allow to create tags on the fly on a note form view When user create a new Note or click on 'Tick' option in kanban view, remove the message 'Active->True' & 'True->False' and Make the creation of 'Tags' inline mode. [IMP] note: 'Tags' should be created from note's form view.
note.note model now supports activities. Filters have been added to ease their management.
As this button leads to a void form view without context it is not really usefull. As creating new records is achieved using aliases there is no real need for a New Task/Issue/Note button. mail/new controller is kept for compatibility but should be removed before v11.
There is now a single method easier to inherit to add specific behavior for the display of access button as well as actions buttons. All addons using this mechanism are updated accordingly.
stage_id is comptued and based on stage_ids The default value should be put on stage_ids, not stage_id, it has the same effect but avoids an unecessary chain update.