Merge lp:~sebastien.beau/openobject-addons/trunk-improve-project-issue into lp:openobject-addons

[Sébastien BEAU - http://www.akretion.com]

Hi
I just propose a little merge.
Indeed in the view project issue the field related assigned is visible even if the field task is empty (the field related read his result from the field "assigned to" of the task).
So without task you can not fill the field "assigned to" of the project_issue.

When a customer use this module, he try to fill this field before the task and think that openerp bug. So the field related should be invisible if the task is empty.

Moreover It will be cleaner to place this field after the field "task_id" as the customer have to fill the task_id before cmodifying the "assigned_to"

My 2 cents

[lp:~sebastien.beau/openobject-addons/trunk-improve-project-issue]

4954. By Sébastien BEAU - http://www.akretion.com on 2011-09-09

[IMP] project_issue : improve user inteface, field assigned is only visible if the field task is fill

[Fabien (Open ERP) (fp-tinyerp)]

hello, thank for the contrib.
I reject the proposal as project_issue changed since the proposal, we do not have assigned_to anymore.

Unmerged revisions

4954. By Sébastien BEAU - http://www.akretion.com on 2011-09-09

[IMP] project_issue : improve user inteface, field assigned is only visible if the field task is fill

=== modified file 'project_issue/project_issue_view.xml'
--- project_issue/project_issue_view.xml	2011-08-19 01:14:10 +0000
+++ project_issue/project_issue_view.xml	2011-09-09 11:23:56 +0000
@@ -56,7 +56,7 @@
                         <field name="project_id" required="True" on_change="on_change_project(project_id)"/>
                         <field name="categ_id" widget="selection" domain="[('object_id.model', '=', 'project.issue')]"/>
                         <field name="user_id" invisible="1" />
-                        <field name="assigned_to"/>
+                        <field name="assigned_to" attrs="{'invisible': [('task_id', '=', False)]}"/>
                         <field name="version_id" colspan="2" widget="selection"/>
                         <group colspan="2" col="4">
                             <field name="type_id" string="Resolution" />