| Age | Commit message (Collapse) | Author |
|---|
|
Closes #10835
|
|
model has been renamed to mail.channel to prepare the slack modeling.
In future commits the mail.group model will be merged with the channel
model from im_chat. The first move is to rename mail.group into
mail.channel to have a model that will unite both features.
|
|
|
|
- Several Modules have been splitted into several apps
Examples :
Human Resources : Splitted into Leaves, Recruitment, Expenses, Appraisals, Timesheets, Employees, Payroll
Marketing : Mass Mailing, Events, ...
Messaging : Chat, Agenda, Notes, Address Book, ...
- Generally, the related reports have been moved in the apps, as last menu
- Also, configuration menu (no_one group) have been moved into a config root menu
exception made for the warehouse and lunch modules
- Configuration for typical frontend modules have been moved into the website settings
Related modules : Ecommerce, blog, slides, forum
- When they are present, menus like 'product' or 'customers' have been moved
ex : Customers in Sales menu, Product in POS menu
- A lot of sequences and xmlids have been added or modified in this commit
- List of apps :
1 Chat : Inbox, Channels
2 Agenda : Calendar
3 Notes
4 Address Book : The view contact is still laying in the mail module (1 app => 2 icons)
5 eCommerce : Still to define : Config + Orders Analysis + Shipping + incoming Amazon module
6 Sales : Dashboard (Sales Team Kanban), CRM, Sales (note that they are splitted into 2 submenus)
Assignation, After-Sales (Invoicing and Services), Reports
7 Point of Sale : Dashboard (POS status), Orders, Reports
8 Project : Dashboard (Project Kanban), Search (all tasks, issues), Incoming Forecasts module, Reports
Project.issue.version feature has been removed completely
9 Members : Dashboard (Members Kanban), Report, Config
10 Timesheets : Time Tracking, Approvals, Reports
11 Purchase : Purchase, Control (Products and Bills)
12 Warehouse : Dashboard (Warehouse Kanban), Operations, Inventory Control, Schedulers, Configuration
13 Manufacturing : Same menu structure
14 Mass Mailing : Mailings, Campaigns, Reports
15 Events : Events, Reports
16 Lead Automation : Campaigns, Reports
17 Surveys : Surveys, Reports
18 Human Resources : Dashboard (Departments Kanban), Employees, Contracts, Engagement (Gamification)
19 Recruitment : Job Positions, Applications, Resumes & Letters, Reports
20 Expenses : Expenses, Approvals, Reports
21 Leaves : My Leaves, Approvals, Reports
22 Appraisals : Appraisals, Interview, Reports --> Will probably be modified by the incoming refactoring
23 Payroll : Current Menu
24 Lunch : My Lunch, Manager, Configuration
25 Accounting : Same menus currently, waiting the new accounting to be merged
26 Fleet : Current menu
27 Sign : Incoming docusign module
28 No root menuitem with this sequence
29 Attendance : Attendance, Reports
Sign in/out by project feature has been removed completely
30 Link Tracker (group_no_one) : Link Tracker, UTMs
New view added : URL Shortner, which is the frontend view embedded in backend
31 Versionning : Website domain, Versions, Experiments
32 Slides (group_no_one) : Channels, Categories, Slides, Tags
33 No root menu item with this sequence
34 Livechat : Channels, History, Reports
35 Dashboards : My Boards, Configuration
36 App Store : Local Modules, Apps, Updates
Last Settings : Incoming Dashboard Settings, Sales, ...., Website Settings
General Pattern for all modules' settings :
| Module_name
|-- Settings : General Config view (checkbox screen)
|-- Record setting 1
|-- ...
|-- Record setting n
Example for Sale module
| Sales
|-- Settings : Checkbox screen
|-- Quotations
|---- Quotation Templates
|---- Report Layout Categories
|---- Contract Template
|---- Invoice Type
|-- Contract
|---- Deduplicate Contacts
|-- Delivery
|---- Delivery Methods
|---- Delivery Pricelist
|
|
_track is now a method that returns the subtype to trigger in a given
tracking context. A tracking will now lead to only one subtype
being trigerred, instead of having multiple possible subtypes.
Now, one tracking leads to one message with one subtype, or without subtype
if there is none matching. This simplifies the model for future evolution of
chatter and mail.
[IMP] project, project_issue: cleaned task and issue subtypes, now having
opened for created / assigned.
|
|
next stage
|
|
kanban views
bzr revid: tde@openerp.com-20140508152536-s3my5onl33z3kxxx
|
|
bzr revid: mba@tinyerp.com-20140228131855-obhatiecnzv1bgqu
|
|
bzr revid: mba@tinyerp.com-20140224044547-pm0acqg1gr0hbi19
|
|
bzr revid: tde@openerp.com-20140221112704-lqd4o5bnljn84yxs
|
|
bug in project_mrp + re-added commentred tests in project_mrp
bzr revid: tde@openerp.com-20130710122526-tf87avul7huqgigg
|
|
bzr revid: tde@openerp.com-20130626155217-333zsa7hj8wjckcn
|
|
project.category aka 'tags')
bzr revid: qdp-launchpad@openerp.com-20130221145027-vgz83n2mchyhbmnu
|
|
avoid spamming contact partners.
bzr revid: tde@openerp.com-20130130090942-duiwfvtcj2d0ad6c
|
|
bzr revid: tde@openerp.com-20121219212330-xfx3lykstl1nsa8m
|
|
added in mail_thread. Updated track_visility parameter.
bzr revid: tde@openerp.com-20121219163923-8xmhb00sxvddcx4g
|
|
removed now unnecessary chatter messages.
bzr revid: tde@openerp.com-20121218153631-43h4hcd9nsgo1b3o
|
|
bzr revid: fka@tinyerp.com-20121204084819-ucg872vc6bxykjc0
|
|
bzr revid: fka@tinyerp.com-20121204073244-2m629bmhs394rpwb
|
|
Updated messages body to have shorter sentences.
bzr revid: tde@openerp.com-20121203113906-g0nhtn9j22d3lf0b
|
|
bzr revid: apa@tinyerp.com-20121122085833-7pb6s04q8jexklzt
|
|
bzr revid: rma@tinyerp.com-20121122061014-hzcoqkrdspk40jnb
|
|
bzr revid: rma@tinyerp.com-20121122052957-x6a1ei6t2ma8wujk
|
|
bzr revid: rma@tinyerp.com-20121121103820-ieoqpx0g0rghbav7
|
|
bzr revid: rma@tinyerp.com-20121120104556-hta7g7z27aa9jgl9
|
|
bzr revid: rma@tinyerp.com-20121120101306-nkk46y92qcs37n9c
|
|
bzr revid: rma@tinyerp.com-20121120094454-qoxpifbmt5pfiuyj
|
|
bzr revid: fp@tinyerp.com-20121115100740-3pbot8zfu64s4ods
|
|
meaning they are effectively pushed.
bzr revid: tde@openerp.com-20121114115504-tvh0j9ks0jde12ed
|
|
project automatically following issues. Updated subtype names.
bzr revid: tde@openerp.com-20121102154154-o8dpil045ub2spbd
|
|
bzr revid: tde@openerp.com-20120919120000-62v9f5e24fh3grzd
|
|
bzr revid: sgo@tinyerp.com-20120913053540-atfsrw8bkf16qo3t
|
|
bzr revid: rma@tinyerp.com-20120904130423-928mhaatxuxfbwi4
|
|
bzr revid: rma@tinyerp.com-20120904085626-klbtc8hrrksi4gy9
|
|
review misc wording
bzr revid: odo@openerp.com-20120830141852-ku8nql1sfkko8669
|
|
bzr revid: fp@tinyerp.com-20120817111936-2d33nlqlbvkjb374
|
|
bzr revid: fp@tinyerp.com-20120817102650-1sglq1y2dbb3xqju
|
|
bzr revid: fp@openerp.com-20120805201322-y8ghspcb69wmb3ut
|
|
bzr revid: rco@openerp.com-20120725113930-7ve3hz98i6ieuvmy
|
|
- give read access rights to group_portal_member on projet.task.type and project.task.work models
- hide action buttons and priority fields in form and list views
- a question remains: how to handle states and stages ? state seems more revelant and simple to understand for portal users (and therefore should be shown through the statusbar widget) while stage is more interesing for internal organization
bzr revid: abo@openerp.com-20120601150718-dk49583g1tko118y
|
|
bzr revid: fp@tinyerp.com-20101004235726-mvx5y41nx2bg4s9f
|
|
bzr revid: fp@tinyerp.com-20100928125008-wa6du4et5t43k2r9
|
|
bzr revid: rpa@tinyerp.com-20100923054709-720hvjixepc2v59g
|
|
bzr revid: hmo@tinyerp.com-20100922140024-usndmzb5u9hrkulm
|
|
bzr revid: jvo@tinyerp.com-20100922123756-vievvziib23ulzma
|
|
bzr revid: stephane@openerp.com-20100901094831-zar6xf0q1mgkv802
|
|
bzr revid: stephane@openerp.com-20100901094734-28a2p406slmfr7qy
|
|
bzr revid: mra@mra-laptop-20100702143706-k5zeko7e9n7ikvk1
|
|
bzr revid: stephane@openerp.com-20100429080154-kmn18r5kci0uq84u
|
|
bzr revid: mra@tinyerp.com-20100419083825-3qkk5o1kbvvudblq
|
