summaryrefslogtreecommitdiff
path: root/addons/project_long_term/project_long_term_view.xml
diff options
context:
space:
mode:
authorSbh (Openerp) <sbh@tinyerp.com>2012-03-23 10:55:30 +0530
committerSbh (Openerp) <sbh@tinyerp.com>2012-03-23 10:55:30 +0530
commite17dee3a5ee9ee0aeffb4bc28d2865eb9d1c2086 (patch)
treef36d5ffdb829c0bd7db81ee65853c05ff3ef599a /addons/project_long_term/project_long_term_view.xml
parentc3687e6f22d7e9824684ebb6004fc3c74f11ee6f (diff)
parentb917267f2d27688db7318f28faf96b97f952a67a (diff)
[MERGE] Merge with lp:openobject-addons
bzr revid: sbh@tinyerp.com-20120323052530-l9fsd06fbma1l3gz
Diffstat (limited to 'addons/project_long_term/project_long_term_view.xml')
-rw-r--r--addons/project_long_term/project_long_term_view.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/addons/project_long_term/project_long_term_view.xml b/addons/project_long_term/project_long_term_view.xml
index 23ae8139bea..9800c209dd5 100644
--- a/addons/project_long_term/project_long_term_view.xml
+++ b/addons/project_long_term/project_long_term_view.xml
@@ -2,7 +2,7 @@
<openerp>
<data>
- <menuitem id="base.menu_project_long_term" name="Planning" parent="base.menu_main_pm" sequence="1"/>
+ <menuitem id="base.menu_project_long_term" name="Long Term Planning" parent="base.menu_main_pm" sequence="3"/>
# ------------------------------------------------------
# Project User Allocation
@@ -124,7 +124,7 @@
</tree>
<form string="Project Users">
<field name="user_id"/>
- <field name="date_start" />
+ <field name="date_start" />
<field name="date_end"/>
</form>
</field>
@@ -252,7 +252,7 @@
<field name="res_model">project.phase</field>
<field name="view_type">form</field>
<field name="view_mode">gantt,tree,form,calendar</field>
- <field name="context">{"search_default_current": 1}</field>
+ <field name="context">{}</field>
<field name="search_view_id" ref="view_project_phase_search"/>
<field name="help">A project can be split into the different phases. For each phase, you can define your users allocation, describe different tasks and link your phase to previous and next phases, add date constraints for the automated scheduling. Use the long term planning in order to planify your available users, convert your phases into a series of tasks when you start working on the project.</field>
</record>
@@ -262,7 +262,7 @@
<field name="res_model">project.phase</field>
<field name="view_type">form</field>
<field name="view_mode">tree,form,calendar</field>
- <field name="context">{"search_default_current": 1}</field>
+ <field name="context">{}</field>
<field name="search_view_id" ref="view_project_phase_search"/>
</record>
@@ -334,7 +334,7 @@
res_model="project.phase"
src_model="project.project"
view_mode="tree,form"
- view_type="form"
+ view_type="form"
/>
# ------------------------------------------------------