V7.0 invoice duplication does not reset reference field

Bug #1092940 reported by Nicolas Bessi - Camptocamp
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Committed
Medium
OpenERP R&D Addons Team 3

Bug Description

Hello,

in V7.0 invoice duplication does not reset reference field that is widely use to reconcile data.

Regards

Nicolas

Related branches

Revision history for this message
Twinkle Christian(OpenERP) (tch-openerp) wrote :

Hello,

I have tested this issue, and I have seen that we have to override the def copy method and make this both field as a blank.

Thanks for reporting..!!

Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3)
importance: Undecided → Medium
status: New → Confirmed
Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Hiral Patel (OpenERP) (hip-openerp) wrote :

Hello,

           It has been Fixed in http://bazaar.launchpad.net/~openerp-dev/openobject-addons/trunk-bug-1092940-hip
           Revno: 8482
           Revision ID: <email address hidden>
Thanks,
hip

Changed in openobject-addons:
status: In Progress → Fix Committed
Revision history for this message
Houssine (houssine-bakkali) wrote :

one year passed and this fix hasn't been released?

what wrong with this fix?

Revision history for this message
Graeme Gellatly (gdgellatly) wrote : Re: [Bug 1092940] Re: V7.0 invoice duplication does not reset reference field

I don't know but I'm glad it hasn't been committed. It would be far
harder to disable when it is desired functionality. Whats wrong with
just putting it in a seperate module. Often when duplicating an
invoice you want the reference field duplicated, and if you don't then
delete it, and if you always don't then create a seperate module.
This is not so much a bug, just that someone doesn't like
functionality and in ensuring that they are satisfied it could impact
many users when it is far easier to have seperately.

IMO the only use case for not copying fields in a master module is
when it makes total nonsense - e.g. copying all the stock moves of a
journal when duplicating a journal, or copying the product id of a
duplicated product template, or the actual invoice number. In other
words, it must hold true for everyone all of the time. Anything that
comes down to personal preference, or is true for most people, most of
the time or for some people all of the time, or even most people all
of the time is best put in a seperate module so everyone can be
satisfied. Especially when it affects any of the standard ORM
functions because there is no way to really override the negative
behaviour as you always need to call upwards.

On Fri, Dec 20, 2013 at 5:09 AM, Houssine <email address hidden> wrote:
> one year passed and this fix hasn't been released?
>
> what wrong with this fix?
>
> --
> You received this bug notification because you are subscribed to OpenERP
> Addons.
> https://bugs.launchpad.net/bugs/1092940
>
> Title:
> V7.0 invoice duplication does not reset reference field
>
> Status in OpenERP Addons (modules):
> Fix Committed
>
> Bug description:
> Hello,
>
> in V7.0 invoice duplication does not reset reference field that is
> widely use to reconcile data.
>
>
> Regards
>
> Nicolas
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-addons/+bug/1092940/+subscriptions

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.