| Age | Commit message (Collapse) | Author |
|
Use crm.lead instead of a the crm.opportunity.report object for
reporting. This allows to show more fields (e.g. tags_ids). The only
field not accessible in the report is #activities, but there is a
deicated report dedicated to activities.
Improved the default search. Example: when reporting on leads, you want
leads+opps by creation date (and not only leads) as an opportunity has
been a lead created too.
|
|
First purpose of this commit is to limit access on activity types.
Employees can now only read activity types. Indeed defining or modifying
activity types should not be done by employees as it impacts daily work
of all other employees. Specific app-based rights are added for project
and sale managers. Those have a specific menu to configure activity
types, meaning they should also have the access rights to do so.
Also including :
* ease default computation for res_model_id of activity types: using
default_res_model in context it is possible to specify a default
res_model_id. It is useful for example to give a specific context
in configuration menus;
* add a domain on res_model_id field in order to limit it to models
inheriting from mail.thread and not being transient;
* various improvement in activity type form view to ease configuration
notably the # days renamed to planned in;
|
|
Thanks to ksa 87d531400f867a110167645e1208959723cfb6bc
|
|
Was part of PR #19820. Courtesy of Vauxoo
|
|
CRM module depends on base automation only to have some automated
actions as demo data. To avoid having unnecessary dependencies
automated action demo data have been removed. This allows to remove
the dependency between CRM and base automation.
|
|
First step towards cleaning and improving automated actions is to
correctly name things. base_action_rule module is therefore renamed
to base_automation. Model is also renamed to base.automation.
|
|
crm.lead model now supports activities. Filters have been added to ease
their management. Mail activities replace the old crm.activity model. All code
related to crm.activity is then removed, including views and custom widget.
Standard activities feature is now used widely in Odoo addons and replace
those custom activities.
A small update is required in website_crm_partner_assign. Now the portal user
can only update or create its own activities aka assigned to him. If he has
an activity assigned to him it is displayed in the opportunity website view.
If not editing the opportunity will create a new activity assigned to him.
|
|
Purpose:
Having the res_group defined in base and sales_team auto installed
with mail doens't make sense.
- Move the empty res_config class and the related view from
base_setup to sales_team (base_setup only contains the 'General Settings'
model and views
- Move the 'sale' related content from product to sale module (Access rights,
menuitems,...)
- Set sales_team at autoinstall False. The module is installed when needed by
crm or sale for example
- Set sales_team as a dependency of voip. (Access rights defined for configuration
purpose)
- Set sales_team ad a dependency of subscription (Access rights issue too)
[FIX] account: move some ir.model.access to sale module
[FIX] payment: Move some ir.rule to website_sale
[FIX] stock: move some ir.model.access rule to sale_stock
[FIX] project: Move some ir.model.access rules to crm_project_issue
[FIX] mrp: Move some ir.model.access rules to sale_mrp
[FIX] calendar: move some ir.model.access rules to crm
Rename xmlids accordingly. Example: 'base.group_sale_manager' becomes
sales_team.group_sale_manager.
[ADD] sales_team: See own documents => See only his sales team
Moved the "User: Own Leads Only", "User: All Leads" and "Manager" groups from sale and crm
into sales_team module. Add the record rules so that user can see only his Own Sales Team
if "See Own Leads" is sales right and can see all sales teams if he is having sales rights
of "See All Leads" or manager.
|
|
This branch need more testing instead of doing 10 fixes. A lot of issues are occuring
when installing modules in different orders.
This reverts commit fa6e415cdb23ce9494487ed672792186157b40e0.
|
|
Purpose:
Having the res_group defined in base and sales_team auto installed
with mail doens't make sense.
- Move the empty res_config class and the related view from
base_setup to sales_team (base_setup only contains the 'General Settings'
model and views
- Move the 'sale' related content from product to sale module (Access rights,
menuitems,...)
- Set sales_team at autoinstall False. The module is installed when needed by
crm or sale for example
- Set sales_team as a dependency of voip. (Access rights defined for configuration
purpose)
- Set sales_team ad a dependency of subscription (Access rights issue too)
Rename xmlids accordingly. Example: 'base.group_sale_manager' becomes
sales_team.group_sale_manager.
|
|
- now possible to archive lost reasons. Indeed some reasons may become
unrelevant after some time.
- updated access rights on lost reasons: manager can create / update them
salesmen can only use them
- add archived filter
|
|
usability + [IMP] account: bank journals are now the bank accounts of a company
|
|
[REM] crm: removed unused file crm_report_view.xml, containing
strange old views, probably some old reports. Those seems to be replaced by
the opportunities and activities analysis + the various dashboards and
graph views.
|
|
that should lie in a feature branch and be reviewed. We try not
to screw the history and the branches, let us continue like
this.
Reverted commits :
189c589d762c6abdcc4b68201f1b5da182bed3dd
11b1eb1ce534dc7c4b75ee906426a65978e25d7f
f618df931a07c78ea0ad15ca0aff1b5a2a8cf002
c0ee9de360abc2f5c415c81e236b1008db1332d0
a340f0cd2aa5e8c9842e91dedc7e95981d2041ed
c6235581ef1b630f5c37bca5bfe1eb8828e22395
51cc853c6190311c5e709dbe78a708215501d17d
7a541b0d070c0b0d3df7f514b5b0387455cf44c8
3f6b92e7b5746116f0ef3a01a5a2e12566c10dd0
ecd410a3eea964ed33c6b706b0a025dfdc99f166
b6418a116d5b1b9e6763bf1886ac94423ae02b68
|
|
won: probability=100 (on lead)
loss: probability=0 and not active
Won / Loss Replaced most complex domains (merge leads wizard...) by active=True
[IMP] Code cleaning / removing:
unused report.crm.*
merged crm.lead.report and crm.opportunity.report (one report with domains)
[IMP] Cleaned demo data:
Won / Loss, Put back "New" stage
Removed "Marketing" sales team
[IMP] Removed Multiple salesteam setting (always multiple salesteam
Always display the dashboard (multiple salesteam)
No more option in settings
[FIX] misc fixes (bad domains), type not required
|
|
to define custom light workflows on opportunities.
Activities are linked to mail.message.subtype through inheritance.
This means that the follow mechanism works for activities. When
an activity is done, a message with the matching subtype is posted
on the opportunity.
Activities are internal by default. They are only visible by
employees.
A shortcut in the 'log a note' chatter option allows to post a
note linked to an activity (subtype).
|
|
|
|
Before this commit, it was only visible by the admin user.
I used the crm.phonecall.report rules as an example, but I don't
think either of those or the opportunities ones are actually
used in the case of group_sale_salesman, because the submenu
Sales of the Reporting menu is only visible to the Sale Manager.
Fixes opw 615048.
|
|
Shadows lie)
|
|
This module tracks clicks in mass mailing mails and allow the generation of trackable links in a website interface.
Modules modifications
---------------------
Refractoring of the crm_tracking_* classes in a new module.
* Extract the crm_tracking_* from the crm module into a new module "utm"
* Remove the crm_mass_mailing bridge module
* New dependencies of mass_mailing and website_links to utm.
|
|
|
|
Models renamings:
- crm.case.stage becomes crm.stage
- crm.case.section becomes crm.team
Model split:
crm.case.categ has been splitted into:
- crm.phonecall.tag
- crm.lead tag
- crm.claim.tag
- crm.helpdesk.tag
Models removal:
- crm.payment.mode
- crm.segmentation
- report.crm.case
Removal of the crm_profiling module
(all these refactorings have been done in order to ease new API
migrations)
|
|
mass_mailing, crm_lead and sale_order
|
|
|
|
bzr revid: jke@openerp.com-20140430093613-3tdn2tfiwshcahbz
|
|
|
|
|
|
|
|
|
|
bzr revid: chs@openerp.com-20131124182419-nn1m2prno6fk0iez
|
|
bzr revid: chm@openerp.com-20130503140029-vv7u9gjmax73qyta
|
|
create and unlink
bzr revid: chm@openerp.com-20130503134356-9wxf9i9cifj3b7q6
|
|
Via this wizard, you will be able to merge a lot of partners via the email,
name, vat or other columns.
It is available in the "Sales/Tools" menu.
bzr revid: stw@openerp.com-20130502103044-ljnj5n7pvs1vsbed
|
|
was necessary only for the History tab on Customers in 6.1
The History tab does not contain PhoneCalls and Leads/Opportunities
anymore in 7.0 - they have been replaced by buttons on the top of
the form.
lp bug: https://launchpad.net/bugs/1066580 fixed
bzr revid: odo@openerp.com-20130325141943-r9q0ljz5x1pxeoqi
|
|
rules to use standard stuff
bzr revid: rco@openerp.com-20121221102151-fxepq652rkeba62z
|
|
bzr revid: mdi@tinyerp.com-20120801100016-2fnvaz9lnavkj4bz
|
|
widgets to work for stages
bzr revid: odo@openerp.com-20120724153405-8owoyo60bjgnq60r
|
|
bzr revid: tde@openerp.com-20120709081834-18pf4bol39s50uno
|
|
bzr revid: rco@openerp.com-20120705080616-k9rhleajvmdg0ieu
|
|
mail.message access rights will be defined as attachments.
bzr revid: tde@openerp.com-20120508135509-ujeqpgh83uui6nbz
|
|
bzr revid: jam@tinyerp.com-20120307054751-rtnddry36p7zhxf8
|
|
lp bug: https://launchpad.net/bugs/908797 fixed
bzr revid: kjo@tinyerp.com-20120106093609-y706tlnwsn21p7k0
|
|
bzr revid: rco@openerp.com-20111214151605-z3hd19ijqgqcweuj
|
|
bzr revid: fp@tinyerp.com-20111212181113-mhnnbps3ip8ls6pp
|
|
lp bug: https://launchpad.net/bugs/899916 fixed
bzr revid: mtr@tinyerp.com-20111205062638-vsg1n2zwyak399rd
|
|
bzr revid: al@openerp.com-20111108194043-u9a1sqokxl69r6i6
|
|
bzr revid: al@openerp.com-20110828025452-vkkj23005ct60wpb
|
|
bzr revid: al@openerp.com-20110827233130-end57de3i484r0kb
|
|
bzr revid: odo@openerp.com-20110722182337-5irz3g2qva0cf45e
|
|
bzr revid: rha@tinyerp.com-20110404094552-j2rdq2sbeqrbffgn
|