lp:~openerp-dev/openobject-addons/trunk-bug-1158406-amitvora

Branch merges

Propose for merging

No branches dependent on this one.

Ready for review for merging into lp:openobject-addons

Nimesh Contractor(Open ERP) (community): Approve on 2013-03-25

OpenERP Core Team: Pending requested 2013-03-25

Diff: 10 lines (+1/-0)

1 file modified

crm/crm_lead.py (+1/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1158406: [7.0, trunk] Leads' on_change_partner() does not copy zip code

Low

Fix Committed

Link a bug report

Related blueprints

8645. By Amit Vora(OpenERP) on 2013-03-25

[MERGE] with trunk

8644. By Amit Vora(OpenERP) on 2013-03-25

[IMP] improve the code

8643. By Amit Vora(OpenERP) on 2013-03-22

[FIX] field name zip add when onchange function call

8642. By Launchpad Translations on behalf of openerp on 2013-03-22

Launchpad automatic translations update.

8641. By Thibault Delavallée (OpenERP) on 2013-03-21

[MERGE] [FORWARD] Forward port of addons 7.0 until revision 8906 (revid <email address hidden>).

8640. By Vo Minh Thu on 2013-03-21

[FIX] hr_timesheet: in hr.analytic.timesheet.unlink(), unlink the parent first (to ensure uninstall works correctly).

8639. By Raphael Collet (OpenERP) on 2013-03-21

[MERGE] cleanup of Yaml files: do not translate assert messages

8638. By Launchpad Translations on behalf of openerp on 2013-03-21

Launchpad automatic translations update.

8637. By Launchpad Translations on behalf of openerp on 2013-03-20

Launchpad automatic translations update.

8636. By Thibault Delavallée (OpenERP) on 2013-03-19

[MERGE] Mass Mailing branch. The purpose of this branch is to improve the mass mailing using the composer wizard, and a better support of email template values. Mass mailing basically posts a message on a document, without notifying the followers. Options are added that allow to send pure email mass mailing, or to notify followers. Specifying a reply to address is now supported. It by-passes the automatic thread fetching by directly looking for aliases instead of rebuilding threads when processing replies. Some templates have also been updated or added to support mass mailing in CRM.

mail_mail
- added recipient_ids field, that holds specific recipients in addition to email_to; this field replace the recipient_ids parameter of mail_mail.send(), allowing to re-send failed emails, or at least store the whole mail information about recipients,
- updated form view to add some missing fields in the view,
mail_message
- added 'reply_to' field, that holds specific reply_to value, before passing it to the created email notifications,
mail_compose_message
- added 'post' boolean field: whether the message will be posted on the document (using active_model_pool.message_post()), or if it should only be an email (using mail_mail.create()),
- added 'notify' boolean field: if the message is posted on the document, tells whether the followers should be notified of the message,
- added 'same_thread' boolean field: if not set, a custom reply_to will be used and the automatic thread routing in message_process will be py-passed,
email_template
- renamed 'email_recipients' field into 'partner_to' (more coherent: email_to is a list of emails, partner_to is a list of partner ids),
- added default template on res.partner, setting partner_to as obj.id,
- moving mass mailing action from mail to email_template, that now uses the previous template,
mail_compose_message in email_template
- added partner_to, email_to and email_cc to be able to use those fields, that exist on the template, in the wizard
crm
- updated basic lead/opportunity template, setting partner_to as obj.partner_id.id, or email_to as obj.email_from
- added mass mailing action for lead/opportunity that uses the previous template