c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #17499
[Bug 724489] Re: [trunk] translation inconsistency in module hr_holidays
Hello Serge,
I have checked your issue.
We have used a same object for "Allocation Request " and "Leave Request" but both have a different behaviors.
Allocation Request: Allocation request is the first step for the hr_holidays first we have to allocating a leave for the particular employee then he/she will put it's leave request.
Leave Request: After allocating a leave request according to a allocation of leave the particular employee will put it's leave request.
So for these reasons we have used a different string for the holiday
type field. In allocation request it's allocation type and in leave
request form it 's leave type.
Hope you will agree with this.
Thanks.
** Changed in: openobject-addons
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/openobject-addons/+question/146798
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/724489
Title:
[trunk] translation inconsistency in module hr_holidays
Status in OpenERP Modules (addons):
Invalid
Bug description:
2 different string for the same field in 2 view
<field name="holiday_type" on_change="onchange_type(holiday_type)"
attrs="{'readonly':[('state','!=','draft')]}" string="Allocation Type"
groups="base.group_hr_manager, base.group_extended"/>
<field name="holiday_type" on_change="onchange_type(holiday_type)"
attrs="{'readonly':[('state','!=','draft')]}" width="130"
groups="base.group_hr_manager, base.group_extended" string="Leave
Type"/>
string="Allocation Type" and string="Leave Type"
That confuse the end user, 2 form need to use the same string to kept
consistency.
References