openerp-india team mailing list archive

[Stéphane Bidoul <997148@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hello,

A very disturbing regression has been introduced in 6.0 regarding the
numbering of bank statements.

I traced the problem to commit
5120 revid:nel@xxxxxxxxxxx-20120308154540-d61jutyp9gbk14lq
which merges
5055.1.1 revid:rha@xxxxxxxxxxx-20120214073854-h7z687qdroju0qzk

To reproduce the problem, you need to create a bank statement and
populate it from open invoices and manually created statement lines.

Before that commit, the (correct) behaviour was as follow:
- the bank statement received a new number from the associated bank journal sequence (say BNK/2012/N)
- each line in the bank statement generated a move with a number constructed as BNK/2012/N/1, BNK/2012/N/2, ...

After that commit:
- the bank statement received a new number from the associated bank journal sequence (say BNK/2012/N)
- some lines increase generate moves and number them by increasing the journal sequence
- this is behaviour is wrong and result in gaps in bank statments numbering, not mentioning non-contiguous numbering of moves on the bank journal!

Reversing that commit fixes it. However that commit was meant to fix bug
lp:931748, so a better fix has to be created.

Best regards,

-sbi

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/997148

Title:
  [6.0] Important regression in bank statements numbering

Status in OpenERP Addons (modules):
  New

Bug description:
  Hello,

  A very disturbing regression has been introduced in 6.0 regarding the
  numbering of bank statements.

  I traced the problem to commit
  5120 revid:nel@xxxxxxxxxxx-20120308154540-d61jutyp9gbk14lq
  which merges
  5055.1.1 revid:rha@xxxxxxxxxxx-20120214073854-h7z687qdroju0qzk

  To reproduce the problem, you need to create a bank statement and
  populate it from open invoices and manually created statement lines.

  Before that commit, the (correct) behaviour was as follow:
  - the bank statement received a new number from the associated bank journal sequence (say BNK/2012/N)
  - each line in the bank statement generated a move with a number constructed as BNK/2012/N/1, BNK/2012/N/2, ...

  After that commit:
  - the bank statement received a new number from the associated bank journal sequence (say BNK/2012/N)
  - some lines increase generate moves and number them by increasing the journal sequence
  - this is behaviour is wrong and result in gaps in bank statments numbering, not mentioning non-contiguous numbering of moves on the bank journal!

  Reversing that commit fixes it. However that commit was meant to fix
  bug lp:931748, so a better fix has to be created.

  Best regards,

  -sbi

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/997148/+subscriptions