summaryrefslogtreecommitdiff
path: root/addons/project_issue/project_issue_data.xml
diff options
context:
space:
mode:
authorFabien Pinckaers <fp@tinyerp.com>2012-08-17 13:19:36 +0200
committerFabien Pinckaers <fp@tinyerp.com>2012-08-17 13:19:36 +0200
commit6ac583c0f775475bcb9f62c9c10619970a3f6068 (patch)
tree735309714f1c946aac4787f1038fbec5de7561a7 /addons/project_issue/project_issue_data.xml
parent66ece041f0a423bc2526a894bae686dc1d8b41ce (diff)
[IMP] mail cleaning
bzr revid: fp@tinyerp.com-20120817111936-2d33nlqlbvkjb374
Diffstat (limited to 'addons/project_issue/project_issue_data.xml')
-rw-r--r--addons/project_issue/project_issue_data.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/addons/project_issue/project_issue_data.xml b/addons/project_issue/project_issue_data.xml
index beee0b0021d..5df09b683ca 100644
--- a/addons/project_issue/project_issue_data.xml
+++ b/addons/project_issue/project_issue_data.xml
@@ -32,7 +32,7 @@
</record>
<!-- notify all employees of module installation -->
- <function model="mail.group" name="message_append_note">
+ <function model="mail.group" name="message_post">
<!-- ids, subject, body, parent_id=False, type='notification', content_subtype='html' -->
<value eval="[ref('mail.group_all_employees')]"/>
<value>Manage the issues you might face in a project, like bugs in a system, client complaints or material breakdowns. You can record issues, assign them to some responsible person, and keep track of their status as they evolve over time.