diff options
| author | Quentin (OpenERP) <qdp-launchpad@openerp.com> | 2012-03-22 18:23:05 +0100 |
|---|---|---|
| committer | Quentin (OpenERP) <qdp-launchpad@openerp.com> | 2012-03-22 18:23:05 +0100 |
| commit | 343158f39fb5c80aaa8dd01e1409e27953e297b6 (patch) | |
| tree | 627fb91c1c153f714ea4a2711063733843a5a67e /addons/project_long_term/project_long_term_view.xml | |
| parent | 513b3c5108a47cb6268f765c9ae02b9f497f89aa (diff) | |
| parent | a4a2696fb32ee9f536bb95476a468e9207ffaa06 (diff) | |
[MERGE] merged the branch with menu modifications
bzr revid: qdp-launchpad@openerp.com-20120322172305-ko3l5j363lhdozkw
Diffstat (limited to 'addons/project_long_term/project_long_term_view.xml')
| -rw-r--r-- | addons/project_long_term/project_long_term_view.xml | 10 |
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" /> # ------------------------------------------------------ |