When opening an account from a chart of account, the move lines are not filtered

Bug #1045424 reported by Alexis de Lattre
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Committed
Undecided
OpenERP Publisher's Warranty Team

Bug Description

Here is the scenario to reproduce the problem on an up-to-date OpenERP 6.1 :
branch server/61 revno 4264
branch addons/61 revno 6973

1. Create a new DB with demo data and install the "account_accountant" module

2. Select the chart of account "France" (this bug is not specific to the French chart of account... but it's easier for to to describe the bug with it)

3. Activate extended view

4. Create a new customer invoice for Agrolait with 1 HDD1 product and validate it. It creates an account move in period 09/2012 with 3 account move lines with accounts 411100, 445711, 707100

5. Go to Accounting > Charts > Chart of Accounts
   Open a chart of accounts with :
   Fiscal year = 2012 (default)
   Target moves = All Posted entries (default)
   Start period = 10/2012
   End period = 12/2012

6. Open the hierarchy of accounts until you reach the account 707100. You see : Debit = 0, Credit = 0, Balance = 0 -> It's ok, because the only account move that we have is in the period 09/2012.

7. Double click on the account 707100 : you see the account move line corresponding to the product HDD1, which belongs to the period 09/2012
-> that's the bug : this view should only display the account move lines that belong to the period selected for the chart of accounts.

Tags: maintenance

Related branches

Changed in openobject-addons:
assignee: nobody → OpenERP Publisher's Warranty Team (openerp-opw)
tags: added: maintenance
Revision history for this message
Alexis de Lattre (alexis-via) wrote :

This bug is NOT present in OpenERP 6.0 nor 5.0. It is only present in OpenERP 6.1.

Revision history for this message
Alexis de Lattre (alexis-via) wrote :
Changed in openobject-addons:
status: New → Fix Committed
Revision history for this message
Richard Lewis (richard-lewis-r) wrote :

The above fix doesn't take into account the posted state. See attached patch.

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.